teddy-cli 0.1.17.dev1402__tar.gz → 0.1.17.dev1404__tar.gz

{teddy_cli-0.1.17.dev1402 → teddy_cli-0.1.17.dev1404}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: teddy-cli
-Version: 0.1.17.dev1402
+Version: 0.1.17.dev1404
 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
@@ -270,17 +270,29 @@ teddy resume -m "your next instruction"
 
 ### Optional Flags
 
-| Flag               | Description                                                                                                                                   |
-| :----------------- | :-------------------------------------------------------------------------------------------------------------------------------------------- |
-| `--agent`, `-a`    | Select agent persona (`pathfinder`, `architect`, `developer`, `debugger`, `assistant`). Default: `pathfinder` (`assistant` in pipeline mode). |
-| `--context`, `-c`  | Supply additional context files or directories. Repeatable (`-c a.py -c b.md`) or comma-separated (`-c "a.py,b.md"`).                         |
-| `--model`          | Override the default configured model.                                                                                                        |
-| `--yolo`, `-y`     | Auto-approve all actions. To make this default, set `yolo_default: true` in `.teddy/config.yaml`.                                             |
-| `--no-yolo`, `-n`  | Force interactive mode for a single run.                                                                                                      |
-| `--message`, `-m`  | Initial instruction to pass directly to the agent.                                                                                            |
-| `--pipeline`, `-p` | Pipeline mode. Auto-approves actions, requires `-m`, exits immediately after the first message turn, and defaults to the `assistant` agent.   |
-| `--max-turns`      | Maximum turns for a non-interactive run. Overrides `guardrails.max_turns` in `.teddy/config.yaml`.                                            |
-| `--max-cost`       | Maximum session cost in dollars for a non-interactive run. Overrides `guardrails.max_session_cost` in `.teddy/config.yaml`.                   |
+| Flag | Description |
+| :--- | :--- |
+| <nobr>`--agent`, `-a`</nobr> | Select agent persona (`pathfinder`, `architect`, `developer`, `debugger`, `assistant`). Default: `pathfinder` (`assistant` in pipeline mode). |
+| <nobr>`--context`, `-c`</nobr> | Supply additional context files or directories. Repeatable (`-c a.py -c b.md`) or comma-separated (`-c "a.py,b.md"`). |
+| <nobr>`--model`</nobr> | Override the default configured model. |
+| <nobr>`--yolo`, `-y`</nobr> | Auto-approve all actions. To make this default, set `yolo_default: true` in `.teddy/config.yaml`. |
+| <nobr>`--no-yolo`, `-n`</nobr> | Force interactive mode for a single run. |
+| <nobr>`--message`, `-m`</nobr> | Initial instruction to pass directly to the agent. |
+| <nobr>`--pipeline`, `-p`</nobr> | Pipeline mode. Auto-approves actions, requires `-m`, exits immediately after the first message turn, and defaults to the `assistant` agent. |
+| <nobr>`--max-turns`</nobr> | Maximum turns for a non-interactive run. Overrides `guardrails.max_turns` in `.teddy/config.yaml`. |
+| <nobr>`--max-cost`</nobr> | Maximum session cost in dollars for a non-interactive run. Overrides `guardrails.max_session_cost` in `.teddy/config.yaml`. |
+
+### Chat-Oriented Workflow (CHOP)
+
+You do not need API keys or per-token billing to use TeDDy. If you already have an active subscription (ChatGPT, Claude, Gemini, etc.), you can also use TeDDy to practice **[Chat-Oriented Programming (CHOP)](https://arxiv.org/html/2510.10819v1#S2.2)** from your web browser.
+
+TeDDy packages your workspace context into a single clipboard payload, and the agent prompts instruct the model to automatically format its response as an executable, self-contained Markdown plan.
+
+1. **Set the system instructions:** Copy your chosen agent persona's prompt with `teddy get-prompt <agent_name>` and paste it into your web interface's system prompt or custom instructions field.
+2. **Bundle project context:** Export your workspace context to the clipboard with `teddy context` (see [Exporting Context](#exporting-context)). This bundles system information, current git status, project structure, and the full verbatim contents of all files listed in `.teddy/init.context` into a single Markdown payload.
+3. **Prompt the AI:** Paste the context payload into the chat alongside your task request. Guided by the system instructions, the model will automatically structure its response as an executable Markdown plan.
+4. **Apply changes:** Copy the full Markdown plan to your clipboard and run `teddy execute` to validate, review diffs, and apply approved changes automatically, or copy and run individual snippets manually as you would in standard CHOP.
+5. **Report back:** When `teddy execute` finishes, it automatically copies a concise execution report back to your clipboard to paste into the chat.
 
 ### Exporting Context
 
@@ -307,18 +319,6 @@ teddy context -c review.context
 
 `--only` requires at least one `-c` value. Without one the command exits with a usage error, because an empty explicit set would export no files.
 
-### Chat-Oriented Workflow (CHOP)
-
-You do not need API keys or per-token billing to use TeDDy. If you already have an active subscription (ChatGPT, Claude, Gemini, etc.), you can also use TeDDy to practice **[Chat-Oriented Programming (CHOP)](https://sourcegraph.com/blog/chat-oriented-programming-in-action)** from your web browser.
-
-TeDDy packages your workspace context into a single clipboard payload, and the agent prompts instruct the model to automatically format its response as an executable, self-contained Markdown plan.
-
-1. **Set the system instructions:** Copy your chosen agent persona's prompt with `teddy get-prompt <agent_name>` and paste it into your web interface's system prompt or custom instructions field.
-2. **Bundle project context:** Export your workspace context to the clipboard with `teddy context`. This bundles system information, current git status, project structure, and the full verbatim contents of all files listed in `.teddy/init.context` into a single Markdown payload.
-3. **Prompt the AI:** Paste the context payload into the chat alongside your task request. Guided by the system instructions, the model will automatically structure its response as an executable Markdown plan.
-4. **Apply changes:** Copy the full Markdown plan to your clipboard and run `teddy execute` to validate, review diffs, and apply approved changes automatically, or copy and run individual snippets manually as you would in standard CHOP.
-5. **Report back:** When `teddy execute` finishes, it automatically copies a concise execution report back to your clipboard to paste into the chat.
-
 ---
 
 ## Command Reference

{teddy_cli-0.1.17.dev1402 → teddy_cli-0.1.17.dev1404}/README.md

@@ -236,17 +236,29 @@ teddy resume -m "your next instruction"
 
 ### Optional Flags
 
-| Flag               | Description                                                                                                                                   |
-| :----------------- | :-------------------------------------------------------------------------------------------------------------------------------------------- |
-| `--agent`, `-a`    | Select agent persona (`pathfinder`, `architect`, `developer`, `debugger`, `assistant`). Default: `pathfinder` (`assistant` in pipeline mode). |
-| `--context`, `-c`  | Supply additional context files or directories. Repeatable (`-c a.py -c b.md`) or comma-separated (`-c "a.py,b.md"`).                         |
-| `--model`          | Override the default configured model.                                                                                                        |
-| `--yolo`, `-y`     | Auto-approve all actions. To make this default, set `yolo_default: true` in `.teddy/config.yaml`.                                             |
-| `--no-yolo`, `-n`  | Force interactive mode for a single run.                                                                                                      |
-| `--message`, `-m`  | Initial instruction to pass directly to the agent.                                                                                            |
-| `--pipeline`, `-p` | Pipeline mode. Auto-approves actions, requires `-m`, exits immediately after the first message turn, and defaults to the `assistant` agent.   |
-| `--max-turns`      | Maximum turns for a non-interactive run. Overrides `guardrails.max_turns` in `.teddy/config.yaml`.                                            |
-| `--max-cost`       | Maximum session cost in dollars for a non-interactive run. Overrides `guardrails.max_session_cost` in `.teddy/config.yaml`.                   |
+| Flag | Description |
+| :--- | :--- |
+| <nobr>`--agent`, `-a`</nobr> | Select agent persona (`pathfinder`, `architect`, `developer`, `debugger`, `assistant`). Default: `pathfinder` (`assistant` in pipeline mode). |
+| <nobr>`--context`, `-c`</nobr> | Supply additional context files or directories. Repeatable (`-c a.py -c b.md`) or comma-separated (`-c "a.py,b.md"`). |
+| <nobr>`--model`</nobr> | Override the default configured model. |
+| <nobr>`--yolo`, `-y`</nobr> | Auto-approve all actions. To make this default, set `yolo_default: true` in `.teddy/config.yaml`. |
+| <nobr>`--no-yolo`, `-n`</nobr> | Force interactive mode for a single run. |
+| <nobr>`--message`, `-m`</nobr> | Initial instruction to pass directly to the agent. |
+| <nobr>`--pipeline`, `-p`</nobr> | Pipeline mode. Auto-approves actions, requires `-m`, exits immediately after the first message turn, and defaults to the `assistant` agent. |
+| <nobr>`--max-turns`</nobr> | Maximum turns for a non-interactive run. Overrides `guardrails.max_turns` in `.teddy/config.yaml`. |
+| <nobr>`--max-cost`</nobr> | Maximum session cost in dollars for a non-interactive run. Overrides `guardrails.max_session_cost` in `.teddy/config.yaml`. |
+
+### Chat-Oriented Workflow (CHOP)
+
+You do not need API keys or per-token billing to use TeDDy. If you already have an active subscription (ChatGPT, Claude, Gemini, etc.), you can also use TeDDy to practice **[Chat-Oriented Programming (CHOP)](https://arxiv.org/html/2510.10819v1#S2.2)** from your web browser.
+
+TeDDy packages your workspace context into a single clipboard payload, and the agent prompts instruct the model to automatically format its response as an executable, self-contained Markdown plan.
+
+1. **Set the system instructions:** Copy your chosen agent persona's prompt with `teddy get-prompt <agent_name>` and paste it into your web interface's system prompt or custom instructions field.
+2. **Bundle project context:** Export your workspace context to the clipboard with `teddy context` (see [Exporting Context](#exporting-context)). This bundles system information, current git status, project structure, and the full verbatim contents of all files listed in `.teddy/init.context` into a single Markdown payload.
+3. **Prompt the AI:** Paste the context payload into the chat alongside your task request. Guided by the system instructions, the model will automatically structure its response as an executable Markdown plan.
+4. **Apply changes:** Copy the full Markdown plan to your clipboard and run `teddy execute` to validate, review diffs, and apply approved changes automatically, or copy and run individual snippets manually as you would in standard CHOP.
+5. **Report back:** When `teddy execute` finishes, it automatically copies a concise execution report back to your clipboard to paste into the chat.
 
 ### Exporting Context
 
@@ -273,18 +285,6 @@ teddy context -c review.context
 
 `--only` requires at least one `-c` value. Without one the command exits with a usage error, because an empty explicit set would export no files.
 
-### Chat-Oriented Workflow (CHOP)
-
-You do not need API keys or per-token billing to use TeDDy. If you already have an active subscription (ChatGPT, Claude, Gemini, etc.), you can also use TeDDy to practice **[Chat-Oriented Programming (CHOP)](https://sourcegraph.com/blog/chat-oriented-programming-in-action)** from your web browser.
-
-TeDDy packages your workspace context into a single clipboard payload, and the agent prompts instruct the model to automatically format its response as an executable, self-contained Markdown plan.
-
-1. **Set the system instructions:** Copy your chosen agent persona's prompt with `teddy get-prompt <agent_name>` and paste it into your web interface's system prompt or custom instructions field.
-2. **Bundle project context:** Export your workspace context to the clipboard with `teddy context`. This bundles system information, current git status, project structure, and the full verbatim contents of all files listed in `.teddy/init.context` into a single Markdown payload.
-3. **Prompt the AI:** Paste the context payload into the chat alongside your task request. Guided by the system instructions, the model will automatically structure its response as an executable Markdown plan.
-4. **Apply changes:** Copy the full Markdown plan to your clipboard and run `teddy execute` to validate, review diffs, and apply approved changes automatically, or copy and run individual snippets manually as you would in standard CHOP.
-5. **Report back:** When `teddy execute` finishes, it automatically copies a concise execution report back to your clipboard to paste into the chat.
-
 ---
 
 ## Command Reference

{teddy_cli-0.1.17.dev1402 → teddy_cli-0.1.17.dev1404}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "teddy-cli"
-version = "0.1.17.dev1402"
+version = "0.1.17.dev1404"
 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.dev1402 → teddy_cli-0.1.17.dev1404}/src/teddy_executor/adapters/inbound/session_cli_handlers.py

@@ -285,6 +285,7 @@ def _run_health_checks(config_service: IConfigService) -> None:
 _GIT_PULL_TIMEOUT_SECONDS = 15
 _PULL_SKIPPED_WARNING = "⚠ Workspace pull skipped; continuing with the current branch."
 _PULL_TIMEOUT_WARNING = "⚠ Workspace pull timed out; continuing without it."
+_PULL_GIT_UNAVAILABLE_WARNING = "⚠ Workspace pull skipped; git is unavailable."
 _IN_PROGRESS_GIT_MARKERS = (
     "rebase-merge",
     "rebase-apply",
@@ -293,6 +294,16 @@ _IN_PROGRESS_GIT_MARKERS = (
 )
 
 
+def _warn_pull(message: str) -> None:
+    """Print one yellow pull warning followed by a blank line.
+
+    The trailing blank line keeps every pull block, success or warning, the
+    same height before the ``Checking configurations...`` line.
+    """
+    typer.secho(message, fg=typer.colors.YELLOW, err=True)
+    typer.echo("", err=True)
+
+
 def _pull_workspace_on_start(
     config_service: IConfigService,
     run_func: Optional[Callable[..., Any]] = None,
@@ -303,8 +314,9 @@ def _pull_workspace_on_start(
     a Git repository, so a disabled toggle or a non-repository directory stays
     silent. A detached HEAD, a missing upstream, or an in-progress operation
     also stays silent, because there is nothing safe to fast-forward. A dirty
-    worktree or a failed pull reports one warning and leaves the workspace
-    unchanged. A successful fast-forward names the number of commits it moved.
+    worktree, a failed pull, a timeout, or an unavailable git binary reports
+    one warning and leaves the workspace unchanged. A successful fast-forward
+    names the number of commits it moved.
 
     The Git process is injected through ``run_func`` so every decision is
     testable without spawning a real repository.
@@ -317,7 +329,9 @@ def _pull_workspace_on_start(
     try:
         _fast_forward_workspace(git_run)
     except subprocess.TimeoutExpired:
-        typer.secho(_PULL_TIMEOUT_WARNING, fg=typer.colors.YELLOW, err=True)
+        _warn_pull(_PULL_TIMEOUT_WARNING)
+    except OSError:
+        _warn_pull(_PULL_GIT_UNAVAILABLE_WARNING)
 
 
 def _fast_forward_workspace(git_run: Callable[..., Any]) -> None:
@@ -330,7 +344,7 @@ def _fast_forward_workspace(git_run: Callable[..., Any]) -> None:
     skip_reason = _pull_skip_reason(git_run)
     if skip_reason is not None:
         if skip_reason:
-            typer.secho(skip_reason, fg=typer.colors.YELLOW, err=True)
+            _warn_pull(skip_reason)
         return
     before = _read_head(git_run)
     result = git_run(
@@ -341,7 +355,7 @@ def _fast_forward_workspace(git_run: Callable[..., Any]) -> None:
         timeout=_GIT_PULL_TIMEOUT_SECONDS,
     )
     if result.returncode != 0:
-        typer.secho(_PULL_SKIPPED_WARNING, fg=typer.colors.YELLOW, err=True)
+        _warn_pull(_PULL_SKIPPED_WARNING)
         return
     _report_fast_forward(git_run, before, _read_head(git_run))
 
@@ -414,10 +428,13 @@ def _report_fast_forward(git_run: Callable[..., Any], before: str, after: str) -
         return
     noun = "commit" if commits == 1 else "commits"
     typer.secho(
-        f"Workspace fast-forwarded ({commits} {noun})",
+        f"✓ Workspace fast-forwarded ({commits} {noun})",
         fg=typer.colors.GREEN,
         err=True,
     )
+    # A trailing blank line separates the fast-forward block from the
+    # ``Checking configurations...`` line that follows it.
+    typer.echo("", err=True)
 
 
 def _start_background_update_check(container: Container) -> list[str]:
@@ -440,22 +457,27 @@ def _start_background_update_check(container: Container) -> list[str]:
     return _display_update_notification(container, cache_path)
 
 
-def _run_startup_preamble(
+def _run_startup_preamble(  # noqa: PLR0913  # Each parameter is an explicit startup gate.
     container: Container,
     fired: list[str],
     agent: Optional[str] = None,
     setup_editor: Optional[bool] = None,
     setup_api_key: Optional[bool] = None,
+    pull_workspace: bool = False,
 ) -> None:
     """Run the shared startup preamble for both session entry points.
 
     The order is fixed so the banner layout cannot drift: health checks, the
-    ``Checking configurations...`` line, the preflight check (whose returned
-    keys extend ``fired``), then the shared disable-footer. ``start`` forwards
-    its ``agent`` so the preflight validates the agent prompt; ``resume``
-    leaves it ``None`` and validates no agent.
+    start-only workspace fast-forward line, the ``Checking configurations...``
+    line, the preflight check (whose returned keys extend ``fired``), then the
+    shared disable-footer. ``start`` forwards its ``agent`` so the preflight
+    validates the agent prompt and enables ``pull_workspace``; ``resume``
+    leaves the agent ``None`` and keeps the pull off.
     """
-    _run_health_checks(container.resolve(IConfigService))
+    config_service = container.resolve(IConfigService)
+    _run_health_checks(config_service)
+    if pull_workspace:
+        _pull_workspace_on_start(config_service)
     typer.echo("Checking configurations...", err=True)
     fired.extend(
         _run_cli_preflight_check(
@@ -861,8 +883,8 @@ def handle_new_session(  # noqa: PLR0913
             agent=agent,
             setup_editor=setup_editor,
             setup_api_key=setup_api_key,
+            pull_workspace=True,
         )
-        _pull_workspace_on_start(container.resolve(IConfigService))
         _echo_config_success(container, agent, model=model)
 
         session_manager: ISessionManager = container.resolve(ISessionManager)

{teddy_cli-0.1.17.dev1402 → teddy_cli-0.1.17.dev1404}/src/teddy_executor/resources/MRP.md

@@ -126,7 +126,7 @@ Prefer config-level bypasses (pyproject `per-file-ignores`, pre-commit `exclude`
 
 ### Code and Naming Hygiene
 
-Write semantic, self-documenting code where naming and structure make what the code does immediately obvious. Reserve comments exclusively for why (business rationale, non-obvious invariants, constraints, or algorithmic trade-offs); never repeat what code already states. Write comments as full, natural sentences without artificial line-breaking or column wrapping. When editing existing code, update or improve confusing comments rather than leaving stale text. Never cite internal documentation filenames, section headers, rule numbers, or workflow steps in code comments, action descriptions, or turn titles. Name files, functions, and tests after the domain concept, scenario, or behavior under test. Never embed incident, ticket, or bug numbers in file, function, class, or test names.
+Write semantic, self-documenting code where naming and structure make what the code does immediately obvious. Reserve comments exclusively for why (business rationale, non-obvious invariants, constraints, or algorithmic trade-offs); never repeat what code already states. Write comments as full, natural sentences without artificial line-breaking or column wrapping. When editing existing code, update or improve confusing comments rather than leaving stale text. Never cite internal documentation filenames, section headers, rule numbers, or workflow steps in code comments, action descriptions, or turn titles. Name files, functions, and tests after the domain concept, scenario, or behavior under test. Consistently apply domain terms and Ubiquitous Language across all code, tests, and documentation. Never embed incident, ticket, or bug numbers in file, function, class, or test names.
 
 ## Response Format