teddy-cli 0.1.17.dev1307__tar.gz → 0.1.17.dev1309__tar.gz

{teddy_cli-0.1.17.dev1307 → teddy_cli-0.1.17.dev1309}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: teddy-cli
-Version: 0.1.17.dev1307
+Version: 0.1.17.dev1309
 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,28 @@ 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.
 
+### Environment Variables
+
+TeDDy checks the following process environment variables at startup and during a session.
+
+| Variable            | Purpose                                                                                                                                                     |
+| :------------------ | :---------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `TEDDY_LLM_API_KEY` | The LLM API key. The bundled `config.yaml` default references it as `llm.api_key: "${TEDDY_LLM_API_KEY}"`. A shell value wins over the `.teddy/.env` value. |
+| `EDITOR`            | Fallback editor command when `editor` is unset in `.teddy/config.yaml`.                                                                                     |
+| `TEDDY_DIFF_TOOL`   | Overrides the auto-detected diff viewer.                                                                                                                    |
+
+TeDDy also interpolates any `${VAR}` or `${VAR:-default}` token in `.teddy/config.yaml` against `.teddy/.env` layered under the process environment, so you can reference your own secrets from config values.
+
+### Using TeDDy in CI
+
+TeDDy is safe to run in non-interactive environments. When stdin is not a terminal, TeDDy skips the API-key and editor setup prompts automatically, so no command blocks waiting for input.
+
+To run TeDDy in a pipeline, set `TEDDY_LLM_API_KEY` in the environment and pass `--pipeline` (`-p`), which auto-approves actions, requires `-m`, exits after the first message turn, and defaults to the `assistant` agent.
+
+```bash
+TEDDY_LLM_API_KEY="$OPENROUTER_API_KEY" teddy start --pipeline -m "do the thing"
+```
+
 ---
 
 ## Usage
@@ -274,7 +296,7 @@ TeDDy packages your workspace context into a single clipboard payload, and the a
 | Command                       | Description                                                                  |
 | :---------------------------- | :--------------------------------------------------------------------------- |
 | `init`                        | Initialize `.teddy` workspace with defaults and pre-warm dependencies.       |
-| <nobr>`init prompts`</nobr>   | Overwrite bundled prompt Markdown files in `.teddy/prompts/` with defaults. |
+| <nobr>`init prompts`</nobr>   | Overwrite bundled prompt Markdown files in `.teddy/prompts/` with defaults.  |
 | <nobr>`init config`</nobr>    | Overwrite `config.yaml`, `.gitignore`, and `init.context` with defaults.     |
 | <nobr>`init templates`</nobr> | Overwrite bundled Markdown templates in `docs/templates/` with defaults.     |
 | `start`                       | Start an interactive agent session.                                          |

{teddy_cli-0.1.17.dev1307 → teddy_cli-0.1.17.dev1309}/README.md

@@ -176,6 +176,28 @@ 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.
 
+### Environment Variables
+
+TeDDy checks the following process environment variables at startup and during a session.
+
+| Variable            | Purpose                                                                                                                                                     |
+| :------------------ | :---------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `TEDDY_LLM_API_KEY` | The LLM API key. The bundled `config.yaml` default references it as `llm.api_key: "${TEDDY_LLM_API_KEY}"`. A shell value wins over the `.teddy/.env` value. |
+| `EDITOR`            | Fallback editor command when `editor` is unset in `.teddy/config.yaml`.                                                                                     |
+| `TEDDY_DIFF_TOOL`   | Overrides the auto-detected diff viewer.                                                                                                                    |
+
+TeDDy also interpolates any `${VAR}` or `${VAR:-default}` token in `.teddy/config.yaml` against `.teddy/.env` layered under the process environment, so you can reference your own secrets from config values.
+
+### Using TeDDy in CI
+
+TeDDy is safe to run in non-interactive environments. When stdin is not a terminal, TeDDy skips the API-key and editor setup prompts automatically, so no command blocks waiting for input.
+
+To run TeDDy in a pipeline, set `TEDDY_LLM_API_KEY` in the environment and pass `--pipeline` (`-p`), which auto-approves actions, requires `-m`, exits after the first message turn, and defaults to the `assistant` agent.
+
+```bash
+TEDDY_LLM_API_KEY="$OPENROUTER_API_KEY" teddy start --pipeline -m "do the thing"
+```
+
 ---
 
 ## Usage
@@ -240,7 +262,7 @@ TeDDy packages your workspace context into a single clipboard payload, and the a
 | Command                       | Description                                                                  |
 | :---------------------------- | :--------------------------------------------------------------------------- |
 | `init`                        | Initialize `.teddy` workspace with defaults and pre-warm dependencies.       |
-| <nobr>`init prompts`</nobr>   | Overwrite bundled prompt Markdown files in `.teddy/prompts/` with defaults. |
+| <nobr>`init prompts`</nobr>   | Overwrite bundled prompt Markdown files in `.teddy/prompts/` with defaults.  |
 | <nobr>`init config`</nobr>    | Overwrite `config.yaml`, `.gitignore`, and `init.context` with defaults.     |
 | <nobr>`init templates`</nobr> | Overwrite bundled Markdown templates in `docs/templates/` with defaults.     |
 | `start`                       | Start an interactive agent session.                                          |

{teddy_cli-0.1.17.dev1307 → teddy_cli-0.1.17.dev1309}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "teddy-cli"
-version = "0.1.17.dev1307"
+version = "0.1.17.dev1309"
 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.dev1307 → teddy_cli-0.1.17.dev1309}/src/teddy_executor/__main__.py

@@ -137,6 +137,24 @@ def _run_init_setup_gates(container) -> None:
     _validate_editor_config(container)
 
 
+def _display_init_drift(container) -> None:
+    """Print the prompt/template drift advice after bare ``teddy init``.
+
+    Bare ``teddy init`` reuses the SAME advice ``teddy start`` prints, so its
+    "unchanged" summary cannot mislead: it flags drifted prompts and missing
+    templates and names the actionable ``teddy init prompts`` /
+    ``teddy init templates`` commands. The two shared helpers are imported
+    lazily, mirroring ``_run_init_setup_gates``, and they are advisory only --
+    they never block the command.
+    """
+    from teddy_executor.adapters.inbound.session_cli_handlers import (
+        _display_checks_footer,
+        _display_drift_notification,
+    )
+
+    _display_checks_footer(_display_drift_notification(container))
+
+
 def _ensure_project_initialized(container, root_dir: str | None = None) -> None:
     """Lazily performs project anchoring and initialization.
 
@@ -300,6 +318,7 @@ def init_callback(ctx: typer.Context):
     init_use_case = container.resolve(IInitUseCase)
     summary = init_use_case.ensure_initialized()
     typer.echo(f"TeDDy initialized in .teddy folder. {summary}")
+    _display_init_drift(container)
     _run_init_setup_gates(container)