teddy-cli 0.1.17.dev1351__tar.gz → 0.1.17.dev1352__tar.gz

{teddy_cli-0.1.17.dev1351 → teddy_cli-0.1.17.dev1352}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: teddy-cli
-Version: 0.1.17.dev1351
+Version: 0.1.17.dev1352
 Summary: The local-first, test-driven agentic engineering harness. Because you should own the means of development.
 Author: Raphael Atteritano
 License: AGPL-3.0-only
@@ -210,6 +210,10 @@ Use subcommands to overwrite specific defaults:
 
 The first execution of `teddy start` runs an interactive setup to configure your API key and preferred editor. For deeper customization, edit `.teddy/config.yaml`. All `llm.*` settings pass directly through to [LiteLLM](https://docs.litellm.ai/docs/completion/input), allowing you to route to cloud providers or local endpoints (Ollama, llama.cpp, or any OpenAI-compatible server via `api_base`). The config file also lets you adjust your external editor, command execution timeouts, diff similarity thresholds, and automated context pruning budgets.
 
+#### OpenRouter App Attribution
+
+The bundled config attributes OpenRouter usage to TeDDy through the documented `HTTP-Referer` and `X-OpenRouter-Title` headers, so the usage appears on [TeDDy's app page](https://openrouter.ai/apps?url=https://github.com/atte500/teddy). Attribution is provider-side visibility only: the headers travel to the endpoint you already configured and the TeDDy project receives nothing. Delete the `llm.extra_headers` block from `.teddy/config.yaml` to opt out, and note that other providers ignore these headers.
+
 ### Environment Variables
 
 TeDDy checks the following process environment variables at startup and during a session.
@@ -322,7 +326,7 @@ TeDDy packages your workspace context into a single clipboard payload, and the a
 
 <br />
 
-No. TeDDy collects zero telemetry, zero analytics, and runs no background tracking. All requests go directly to whichever LLM provider or local endpoint you configure in your local config file.
+No. TeDDy collects zero telemetry, zero analytics, and runs no background tracking. All requests go directly to whichever LLM provider or local endpoint you configure in your local config file. The bundled config sends OpenRouter's published app-attribution headers, so OpenRouter credits your usage to TeDDy on its public leaderboard, and that visibility reaches only the provider you chose. Remove the `llm.extra_headers` block from `.teddy/config.yaml` to opt out.
 
 </details>
 

{teddy_cli-0.1.17.dev1351 → teddy_cli-0.1.17.dev1352}/README.md

@@ -176,6 +176,10 @@ Use subcommands to overwrite specific defaults:
 
 The first execution of `teddy start` runs an interactive setup to configure your API key and preferred editor. For deeper customization, edit `.teddy/config.yaml`. All `llm.*` settings pass directly through to [LiteLLM](https://docs.litellm.ai/docs/completion/input), allowing you to route to cloud providers or local endpoints (Ollama, llama.cpp, or any OpenAI-compatible server via `api_base`). The config file also lets you adjust your external editor, command execution timeouts, diff similarity thresholds, and automated context pruning budgets.
 
+#### OpenRouter App Attribution
+
+The bundled config attributes OpenRouter usage to TeDDy through the documented `HTTP-Referer` and `X-OpenRouter-Title` headers, so the usage appears on [TeDDy's app page](https://openrouter.ai/apps?url=https://github.com/atte500/teddy). Attribution is provider-side visibility only: the headers travel to the endpoint you already configured and the TeDDy project receives nothing. Delete the `llm.extra_headers` block from `.teddy/config.yaml` to opt out, and note that other providers ignore these headers.
+
 ### Environment Variables
 
 TeDDy checks the following process environment variables at startup and during a session.
@@ -288,7 +292,7 @@ TeDDy packages your workspace context into a single clipboard payload, and the a
 
 <br />
 
-No. TeDDy collects zero telemetry, zero analytics, and runs no background tracking. All requests go directly to whichever LLM provider or local endpoint you configure in your local config file.
+No. TeDDy collects zero telemetry, zero analytics, and runs no background tracking. All requests go directly to whichever LLM provider or local endpoint you configure in your local config file. The bundled config sends OpenRouter's published app-attribution headers, so OpenRouter credits your usage to TeDDy on its public leaderboard, and that visibility reaches only the provider you chose. Remove the `llm.extra_headers` block from `.teddy/config.yaml` to opt out.
 
 </details>
 

{teddy_cli-0.1.17.dev1351 → teddy_cli-0.1.17.dev1352}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "teddy-cli"
-version = "0.1.17.dev1351"
+version = "0.1.17.dev1352"
 description = "The local-first, test-driven agentic engineering harness. Because you should own the means of development."
 readme = "README.md"
 keywords = [

{teddy_cli-0.1.17.dev1351 → teddy_cli-0.1.17.dev1352}/src/teddy_executor/resources/config/config.yaml

@@ -63,6 +63,15 @@ llm:
   api_key: "${TEDDY_LLM_API_KEY}"  # Paste your key into .teddy/.env, or replace this with a literal value to override.
   max_retries: 3
   timeout: 300
+  # OpenRouter app attribution (https://openrouter.ai/docs/app-attribution).
+  # Usage from this app appears at https://openrouter.ai/apps?url=https://github.com/atte500/teddy.
+  # LiteLLM also sends a legacy X-Title default, so both title headers are pinned here.
+  # Remove this block to opt out. Non-OpenRouter providers ignore these headers.
+  extra_headers:
+    HTTP-Referer: "https://github.com/atte500/teddy"
+    X-Title: "TeDDy"
+    X-OpenRouter-Title: "TeDDy"
+    X-OpenRouter-Categories: "cli-agent,programming-app"
 
 # Local models (no API key needed — LiteLLM supplies a keyless default):
 #   model: "ollama/llama3.2"      # Ollama (default endpoint http://localhost:11434)