commandmate 0.27.1 → 0.29.0

package/dist/cli/docs/agent-operations.d.ts

@@ -5,6 +5,6 @@
  * This content is embedded as a string constant so that it's available
  * even when installed via `npm install -g commandmate` (where docs/ is not included).
  */
-export declare const AGENT_OPERATIONS_GUIDE = "# CLI Agent Operations Guide\n\nOperate agent sessions from the CommandMate CLI.\nThese commands enable coding agents (Claude Code, Codex, etc.) to orchestrate other agents in parallel.\n\n## Prerequisites\n\n- CommandMate server must be running: commandmate start --daemon\n- Target worktrees must be registered (visible in browser UI sidebar)\n- Connection target is resolved as: exported CM_PORT > ~/.commandmate/.env CM_PORT > 3000\n  (CM_BIND and the CM_HTTPS_CERT + CM_HTTPS_KEY pair are honoured the same way)\n- Use CM_AUTH_TOKEN env var for authenticated servers\n\n## Commands\n\n### commandmate ls\n  List worktrees with status.\n\n  commandmate ls                          # Table format (ID, NAME, STATUS, DEFAULT)\n  commandmate ls --json                   # JSON output (for agent consumption)\n  commandmate ls --quiet                  # IDs only, one per line (for piping)\n  commandmate ls --branch <prefix>        # Filter by branch name prefix\n  commandmate ls --id <prefix>            # Filter by worktree id prefix\n\n  Worktree ids are <repo>-<branch> slugs (e.g. anvil-develop). --id / --branch\n  front-match is case-sensitive and does NOT guarantee uniqueness (e.g.\n  --id anvil-develop also matches anvil-develop-2). --branch and --id combine\n  as AND. Use --id to disambiguate the same branch across repositories.\n\n  STATUS values:\n    idle     - Session not started\n    ready    - Session running, waiting for input (task completed)\n    running  - Agent executing a task\n    waiting  - Confirmation prompt active (Yes/No, etc.)\n\n### commandmate sync\n  Ask the server to re-scan repositories and sync worktrees to its database\n  (same endpoint as the GUI sync button). Run it after 'git worktree add' so the\n  new worktree appears in 'commandmate ls' without opening the GUI (Issue #1680).\n\n  commandmate sync                        # Prints the server's summary message\n  commandmate sync --json                 # Full API response (worktreeCount,\n                                          # repositoryCount, repositories,\n                                          # deletedCount, cleanupWarnings)\n\n### commandmate send <worktree-id> \"<message>\"\n  Send a message to an agent (async). Starts session automatically if not running.\n\n  Options:\n    --instance <id>        Agent instance ID: <agent> or <agent>-<n> (e.g. claude-2, or codex\n                           for the codex primary instance). The recommended way to name a\n                           target: send / wait / respond / capture / auto-yes all take it.\n    --agent <id>           Ad-hoc CLI tool for an instance the roster does not know:\n                           claude (default), codex, gemini, vibe-local, opencode, copilot, antigravity\n    --register             Register the --instance session into the agent-instance roster\n    --auto-yes             Enable auto-yes before sending (session-wide, no policy\n                           guard -- for unattended runs prefer --contract with an\n                           autoYes policy: mode / denyPatterns)\n    --duration <d>         Auto-yes duration: 1h, 3h, 8h (default: 1h)\n    --stop-pattern <p>     Auto-yes stop condition (regex; matches terminal output,\n                           cannot block commands -- see auto-yes below)\n    --ignore-structured-prompt\n                           Send even if only the agent's hooks report an open dialog.\n                           For a session whose pane looks idle but keeps refusing;\n                           a dialog visible in the terminal is still refused.\n\n  Refused while the agent is waiting on a prompt (exit 2). Keystrokes sent to\n  an open dialog never reach the agent -- they pile up in the dialog's own\n  input line, and the next respond then carries that text along as a message\n  instead of an answer. Nudging a stalled worker is how this gets worse.\n  Answer first: commandmate respond <id> <answer>. respond, special keys and\n  prompt-response are never refused -- they are the way out. Timer-fired sends\n  ARE refused (same service layer) and record [prompt_waiting] as their reason.\n  It fails open if the pane cannot be read, so treat it as a narrowing, not a\n  guarantee.\n\n  Two layers can report the dialog: the terminal scraper, and the agent's own\n  hooks. Either one is enough to refuse -- the dialog the scraper cannot read is\n  exactly the one that caused this. A frame neither layer classifies is still\n  wait's \"unclassified\" case instead.\n\n  A hook-reported dialog is released by the agent's next event, and hooks are\n  fail-open, so the record can outlive its dialog. It therefore stops blocking\n  sends 5 minutes after it was reported -- and immediately with\n  --ignore-structured-prompt, or CM_STRUCTURED_SEND_GUARD=off for the server.\n  A session nobody can send to is worse than a missed guard. Both bypasses are\n  narrow: a prompt on screen is still refused, and the payload still reports it\n  (wait and the UI do not go quiet).\n\n  Finding worktree IDs:\n    WT=$(commandmate ls --branch feature/101 --quiet)\n    WT=$(commandmate ls --id anvil- --quiet)   # disambiguate by repo (id prefix)\n    commandmate send \"$WT\" \"Implement this\"\n\n  Targeting a non-default agent (Issue #1638): pass --instance, not --agent. Only\n  --instance is accepted by every command -- 'wait --agent' does not exist -- so a\n  workflow that names the agent on 'send' and nothing on 'wait' waits on the wrong\n  session in silence.\n    commandmate send \"$WT\" \"Implement this\" --instance codex\n    commandmate wait \"$WT\" --instance codex\n\n### commandmate wait <worktree-id...>\n  Block until agent completes or prompt is detected.\n\n  Options:\n    --timeout <seconds>        Maximum wait time\n    --on-prompt <mode>         agent (default) or human\n    --stall-timeout <seconds>  Max time without output change\n    --instance <id>            Agent instance to wait on. There is no --agent here.\n    --verify                   After completion, run every verification gate\n    --require-work             After completion, run only the work-evidence gate\n\n  Exit codes:\n    0   - Completed (agent idle/ready), and verified when --verify was given\n    10  - Prompt detected (--on-prompt agent mode)\n    20  - A verification gate failed (--verify)\n    21  - Nothing to verify: no commits, no uncommitted changes\n    124 - Timeout exceeded\n\n  --on-prompt modes:\n    agent  - Returns exit 10 immediately with prompt JSON on stdout\n    human  - Keeps blocking until human responds via browser UI\n\n  Prompt JSON output (exit 10):\n    {\"worktreeId\":\"...\",\"cliToolId\":\"claude\",\"type\":\"yes_no\",\"question\":\"...\",\"options\":[\"yes\",\"no\"],\"status\":\"pending\"}\n    The payload IS the prompt -- read it from stdout before falling back to\n    capture. For type \"selection_list\", options is empty by design and the\n    question field carries the reason.\n\n    Three \"type\" values share exit 10; only the first is answerable with\n    respond:\n      yes_no / multiple_choice  a parsed prompt        -> commandmate respond\n      selection_list            arrow-key menu         -> special keys\n      unclassified              the frame is interactive but detection could\n                                not parse it, and it has stayed that way for\n                                60s -> look at the pane: capture <id> --pane\n    \"unclassified\" exists because a frame that slips past detection disables\n    auto-yes, the contract's autoYes policy and this exit 10 all at once. It\n    needs the dwell: a capture taken mid-repaint can raise the flag once.\n    --on-prompt human keeps waiting for it, same as the other two.\n\n  --verify turns \"the agent stopped\" into \"the work passes the repository's own\n  checks\". Verification only runs when completion was detected: a prompt (10) or\n  a timeout (124) is reported as-is and never verified. With several worktrees,\n  gates run one worktree at a time because the server caps concurrent runs.\n\n### commandmate verify <worktree-id>\n  Run the gates declared in .commandmate/verify.yaml against a worktree.\n\n  Options:\n    --gates <id1,id2>     Gate ids to run (default: work-evidence + all declared)\n    --instance <id>       Attribute the run to an agent instance\n    --timeout <seconds>   Stop polling after N seconds (exit 124)\n    --json                Print the run and its gate results as JSON on stdout\n\n  Exit codes:\n    0   - Every gate passed\n    20  - A gate failed, timed out, or errored\n    21  - work-evidence found nothing to verify (no commits, no changes)\n    99  - The run produced no verdict (bad verify.yaml, gates skipped, cancelled)\n    124 - --timeout elapsed while the run was still going\n\n  Output (progress on stderr, verdict on stdout):\n    GATE work-evidence PASS (commits=3, uncommitted=2)\n    GATE lint PASS (exit=0, 12.3s)\n    GATE unit FAIL (exit=1, 45.0s)\n    RESULT failed\n\n  Gates run in the worktree's own directory. Gates are skipped (run status 99,\n  never 0) in the checkout the server itself runs from when verify.yaml sets\n  options.skipInPrimaryCheckout, so a 'build' gate cannot replace the assets the\n  live app is serving.\n\n### commandmate verify history / commandmate verify show <run-id>\n  Read past verification runs. Both are read-only and never start a run, so\n  neither returns 20 or 21 \u2014 those mean \"this tree failed verification\", and a\n  question about history is not a verdict on the current tree.\n\n  commandmate verify history                          # every worktree, newest 50\n  commandmate verify history --worktree <id>          # one worktree\n  commandmate verify history --days 14 --limit 100    # window and page size\n  commandmate verify history --json                   # JSON array on stdout\n  commandmate verify show 42                          # gates + log tails\n  commandmate verify show 42 --json\n\n  history options:\n    --worktree <id>       Restrict to one worktree (default: all)\n    --days <n>            Look back n days, 1..90 (default: no lower bound)\n    --limit <n>           Maximum runs, 1..500 (default: 50)\n\n  One run per line. The leading #<run-id> is what \"verify show\" takes:\n    #42  2026-07-31T04:12:00.000Z  myrepo-feature-101  manual  failed  failed: unit,build\n\n  The listing carries gate verdicts but NOT gate log bodies \u2014 logTail is absent\n  from the JSON, not null. Use \"verify show <run-id>\" when you need the log.\n\n  Exit codes:\n    0   - Read succeeded (also when nothing matched: stderr note, or [] in JSON)\n    2   - Bad argument (--days/--limit out of range, bad worktree or run id)\n    99  - No such run (404), or an unexpected failure\n\n### commandmate respond <worktree-id> \"<answer>\"\n  Respond to an agent's prompt.\n\n  commandmate respond <id> \"yes\"          # Yes/No\n  commandmate respond <id> \"2\"            # Multiple choice (number)\n  commandmate respond <id> \"custom text\"  # Free text\n  commandmate respond <id> \"yes\" --instance codex-2   # Specific instance\n\n  Exit codes:\n    0  - Response sent\n    99 - Prompt already dismissed (prompt_no_longer_active)\n\n### commandmate capture <worktree-id>\n  Get current terminal output.\n\n  commandmate capture <id>                   # Plain text\n  commandmate capture <id> --json            # JSON with status info\n  commandmate capture <id> --instance codex  # Specific instance\n\n### commandmate auto-yes <worktree-id>\n  Control auto-yes (automatic prompt response).\n\n  commandmate auto-yes <id> --enable                    # Enable (default 1h)\n  commandmate auto-yes <id> --enable --duration 3h      # With duration\n  commandmate auto-yes <id> --enable --stop-pattern \"error\"\n  commandmate auto-yes <id> --disable                   # Disable\n  commandmate auto-yes <id> --enable --instance codex-2 # Scoped to one instance\n\n  --stop-pattern matches new terminal output, not the commands an agent runs.\n  It cannot block a command; a build log that merely prints the pattern\n  (e.g. \"rm -rf\" in an npm script) also triggers it and stops auto-yes.\n  To suppress auto-responses for risky prompts, use the task contract's\n  autoYes.denyPatterns instead (docs/design/task-contract.md).\n\n### commandmate instances <worktree-id> [action] [args]\n  Discover and manage a worktree's agent-instance roster (1 agent, multiple sessions).\n\n  commandmate instances <id>                            # List roster + running/auto-yes status\n  commandmate instances <id> --json                     # JSON output\n  commandmate instances <id> add --agent codex          # Add an instance (auto-generates ID, e.g. codex-2)\n  commandmate instances <id> add --agent codex --alias \"Review\" --id codex-3\n  commandmate instances <id> remove <instance-id>       # Remove from roster\n  commandmate instances <id> remove <instance-id> --kill  # Remove and kill its session\n  commandmate instances <id> alias <instance-id> \"New Name\"\n  commandmate instances <id> kill <instance-id>         # Kill only that instance's session\n\n  See \"Multi-Session\" below for the ID convention and roster semantics.\n\n### commandmate skill <subcommand>\n  Manage official Agent Skills. Every subcommand is a thin client over the same\n  APIs the browser UI uses: the CLI never downloads, extracts, writes or deletes\n  anything itself, and never sends a filesystem path, artifact URL, file list or\n  checksum (the API rejects those outright).\n\n  commandmate skill list [--json] [--prerelease]\n  commandmate skill info <skill-id> [--version <v>] [--json]\n  commandmate skill plan <skill-id> --worktree <id> [--version <v>] [--json]\n  commandmate skill install <skill-id> --worktree <id> --version <exact> [--dry-run] [--yes] [--ack-risk <id>@<version>] [--json]\n  commandmate skill uninstall <skill-id> --worktree <id> [--dry-run] [--yes] [--json]\n  commandmate skill status <skill-id> --worktree <id> [--json]\n\n  Confirmation contract (writes = install / uninstall):\n    - A plan is always built and shown first. --dry-run stops there.\n    - Without a TTY, a write REQUIRES --yes. A missing --yes is refused, never\n      assumed: an environment that cannot prompt must not install silently.\n    - A high-risk Skill additionally requires --ack-risk <skill-id>@<version>\n      with the exact id and version. --yes alone never carries a high-risk\n      install, in a TTY or out of one.\n\n  Exit codes:\n    0   success\n    1   the server or the Catalog could not be reached (retryable)\n    2   invalid arguments, unknown Skill or unknown version\n    11  the worktree refused it (local change, conflict, lock, plan drift)\n    12  the write was never confirmed (no --yes, declined, or missing --ack-risk)\n    13  files changed but the operation needs reconciliation\n\n  --json prints the API response body verbatim on stdout; diagnostics, prompts\n  and errors always go to stderr, so a failed --json run leaves stdout empty.\n\n  'skill status' reports one Skill in one worktree, read from the install\n  receipt on disk. There is no per-worktree listing endpoint yet, so <skill-id>\n  is required.\n\n## Multi-Session (1 agent, multiple sessions)\n\n  A worktree can run several sessions of the same CLI tool concurrently. Each\n  session is an \"instance\" identified by an instance ID:\n    <agent>        - the agent's primary instance (e.g. \"claude\")\n    <agent>-<n>    - an additional instance, n >= 2 (e.g. \"claude-2\", \"claude-3\")\n\n  --instance is accepted by send / wait / respond / capture / auto-yes.\n  send --instance auto-starts the session if it is not already running.\n\n  --instance alone is the recommended way to name a target (Issue #1638). It is\n  the only flag all five commands share: --agent is rejected by 'wait'. A\n  rostered instance already carries its CLI tool (Issue #1629), and an instance\n  id that is itself a tool id resolves to that tool's primary instance even\n  without a roster entry, so '--instance codex' needs no --agent.\n\n  --agent remains accepted by send / respond / capture / auto-yes as the\n  supplement for ad-hoc instances the roster does not know -- notably\n  '--register', which cannot infer the tool from an id like codex-3. Passing an\n  --agent that contradicts the roster is an error (exit 2), not an override.\n\n  The roster (visible in the browser UI's Agent panel) is the list of known\n  instances with aliases and display order. Ad-hoc sessions started via\n  'send --instance' do NOT appear in the roster unless registered:\n    commandmate send <id> \"...\" --instance claude-2 --register\n  Without --register, the session still runs and responds to CLI commands,\n  but it will not show up in the UI sidebar/roster until added there or via\n  'commandmate instances <id> add'.\n\n  Per-instance auto-yes: --instance scopes --auto-yes/--duration/--stop-pattern\n  to that specific session, independent of other instances of the same agent.\n\n  commandmate instances <id>                        # discover valid --instance values\n  commandmate send <id> \"task\" --instance codex-2 --auto-yes\n  commandmate wait <id> --instance codex-2 --timeout 600\n  commandmate capture <id> --instance codex-2\n\n## All Exit Codes\n\n  0   SUCCESS          - Completed successfully\n  1   DEPENDENCY_ERROR - Server not running\n  2   CONFIG_ERROR     - Validation error (invalid agent, duration, etc.)\n  10  PROMPT_DETECTED  - Prompt detected during wait\n  20  VERIFY_FAILED    - A verification gate failed (verify, wait --verify)\n  21  NOT_STARTED      - Nothing to verify: no commits, no uncommitted changes\n  99  UNEXPECTED_ERROR - Unexpected error / resource not found / no verdict\n  124 TIMEOUT          - Wait or verification timeout exceeded\n\n  When one 'wait' covers several worktrees, the reported code is the highest\n  priority one observed: 10 > 20 > 21 > 124.\n\n## Troubleshooting\n\n  Server not running:\n    commandmate start --daemon\n    CM_PORT=3011 commandmate ls        # Different port\n\n  Worktree not found:\n    commandmate ls --quiet             # Check registered IDs\n    commandmate sync                   # Sync new worktrees (e.g. after git worktree add)\n    commandmate status                 # Confirm 'ls' and 'status' report the same Port\n                                       # (with several servers running, an exported CM_PORT\n                                       #  points 'ls' at a different one)\n\n  Authentication:\n    CM_AUTH_TOKEN=your-token commandmate ls\n";
+export declare const AGENT_OPERATIONS_GUIDE = "# CLI Agent Operations Guide\n\nOperate agent sessions from the CommandMate CLI.\nThese commands enable coding agents (Claude Code, Codex, etc.) to orchestrate other agents in parallel.\n\n## Prerequisites\n\n- CommandMate server must be running: commandmate start --daemon\n- Target worktrees must be registered (visible in browser UI sidebar)\n- Connection target is resolved as: exported CM_PORT > ~/.commandmate/.env CM_PORT > 3000\n  (CM_BIND and the CM_HTTPS_CERT + CM_HTTPS_KEY pair are honoured the same way)\n- Use CM_AUTH_TOKEN env var for authenticated servers\n\n## Commands\n\n### commandmate ls\n  List worktrees with status.\n\n  commandmate ls                          # Table format (ID, NAME, STATUS, DEFAULT)\n  commandmate ls --json                   # JSON output (for agent consumption)\n  commandmate ls --quiet                  # IDs only, one per line (for piping)\n  commandmate ls --branch <prefix>        # Filter by branch name prefix\n  commandmate ls --id <prefix>            # Filter by worktree id prefix\n\n  Worktree ids are <repo>-<branch> slugs (e.g. anvil-develop). --id / --branch\n  front-match is case-sensitive and does NOT guarantee uniqueness (e.g.\n  --id anvil-develop also matches anvil-develop-2). --branch and --id combine\n  as AND. Use --id to disambiguate the same branch across repositories.\n\n  STATUS values:\n    idle     - Session not started\n    ready    - Session running, waiting for input (task completed)\n    running  - Agent executing a task\n    waiting  - Confirmation prompt active (Yes/No, etc.)\n\n### commandmate sync\n  Ask the server to re-scan repositories and sync worktrees to its database\n  (same endpoint as the GUI sync button). Run it after 'git worktree add' so the\n  new worktree appears in 'commandmate ls' without opening the GUI (Issue #1680).\n\n  commandmate sync                        # Prints the server's summary message\n  commandmate sync --json                 # Full API response (worktreeCount,\n                                          # repositoryCount, repositories,\n                                          # deletedCount, cleanupWarnings)\n\n### commandmate send <worktree-id> \"<message>\"\n  Send a message to an agent (async). Starts session automatically if not running.\n\n  Options:\n    --instance <id>        Agent instance ID: <agent> or <agent>-<n> (e.g. claude-2, or codex\n                           for the codex primary instance). The recommended way to name a\n                           target: send / wait / respond / capture / auto-yes all take it.\n    --agent <id>           Ad-hoc CLI tool for an instance the roster does not know:\n                           claude (default), codex, gemini, vibe-local, opencode, copilot, antigravity\n    --register             Register the --instance session into the agent-instance roster\n    --auto-yes             Enable auto-yes before sending (session-wide, no policy\n                           guard -- for unattended runs prefer --contract with an\n                           autoYes policy: mode / denyPatterns)\n    --duration <d>         Auto-yes duration: 1h, 3h, 8h (default: 1h)\n    --stop-pattern <p>     Auto-yes stop condition (regex; matches terminal output,\n                           cannot block commands -- see auto-yes below)\n    --ignore-structured-prompt\n                           Send even if only the agent's hooks report an open dialog.\n                           For a session whose pane looks idle but keeps refusing;\n                           a dialog visible in the terminal is still refused.\n\n  Refused while the agent is waiting on a prompt (exit 2). Keystrokes sent to\n  an open dialog never reach the agent -- they pile up in the dialog's own\n  input line, and the next respond then carries that text along as a message\n  instead of an answer. Nudging a stalled worker is how this gets worse.\n  Answer first: commandmate respond <id> <answer>. respond, special keys and\n  prompt-response are never refused -- they are the way out. Timer-fired sends\n  ARE refused (same service layer) and record [prompt_waiting] as their reason.\n  It fails open if the pane cannot be read, so treat it as a narrowing, not a\n  guarantee.\n\n  Two layers can report the dialog: the terminal scraper, and the agent's own\n  hooks. Either one is enough to refuse -- the dialog the scraper cannot read is\n  exactly the one that caused this. A frame neither layer classifies is still\n  wait's \"unclassified\" case instead.\n\n  A hook-reported dialog is released by the agent's next event, and hooks are\n  fail-open, so the record can outlive its dialog. It therefore stops blocking\n  sends 5 minutes after it was reported -- and immediately with\n  --ignore-structured-prompt, or CM_STRUCTURED_SEND_GUARD=off for the server.\n  A session nobody can send to is worse than a missed guard. Both bypasses are\n  narrow: a prompt on screen is still refused, and the payload still reports it\n  (wait and the UI do not go quiet).\n\n  Finding worktree IDs:\n    WT=$(commandmate ls --branch feature/101 --quiet)\n    WT=$(commandmate ls --id anvil- --quiet)   # disambiguate by repo (id prefix)\n    commandmate send \"$WT\" \"Implement this\"\n\n  Targeting a non-default agent (Issue #1638): pass --instance, not --agent. Only\n  --instance is accepted by every command -- 'wait --agent' does not exist -- so a\n  workflow that names the agent on 'send' and nothing on 'wait' waits on the wrong\n  session in silence.\n    commandmate send \"$WT\" \"Implement this\" --instance codex\n    commandmate wait \"$WT\" --instance codex\n\n### commandmate wait <worktree-id...>\n  Block until agent completes or prompt is detected.\n\n  Options:\n    --timeout <seconds>        Maximum wait time\n    --on-prompt <mode>         agent (default) or human\n    --stall-timeout <seconds>  Max time without output change\n    --instance <id>            Agent instance to wait on. There is no --agent here.\n    --verify                   After completion, run every verification gate\n    --require-work             After completion, run only the work-evidence gate\n\n  Exit codes:\n    0   - Completed (agent idle/ready), and verified when --verify was given\n    10  - Prompt detected (--on-prompt agent mode)\n    20  - A verification gate failed (--verify)\n    21  - Nothing to verify: no commits, no uncommitted changes\n    124 - Timeout exceeded\n\n  --on-prompt modes:\n    agent  - Returns exit 10 immediately with prompt JSON on stdout\n    human  - Keeps blocking until human responds via browser UI\n\n  Prompt JSON output (exit 10):\n    {\"worktreeId\":\"...\",\"cliToolId\":\"claude\",\"type\":\"yes_no\",\"question\":\"...\",\"options\":[\"yes\",\"no\"],\"status\":\"pending\"}\n    The payload IS the prompt -- read it from stdout before falling back to\n    capture. For type \"selection_list\", options is empty by design and the\n    question field carries the reason.\n\n    Three \"type\" values share exit 10; only the first is answerable with\n    respond:\n      yes_no / multiple_choice  a parsed prompt        -> commandmate respond\n      selection_list            arrow-key menu         -> special keys\n      unclassified              the frame is interactive but detection could\n                                not parse it, and it has stayed that way for\n                                60s -> look at the pane: capture <id> --pane\n    \"unclassified\" exists because a frame that slips past detection disables\n    auto-yes, the contract's autoYes policy and this exit 10 all at once. It\n    needs the dwell: a capture taken mid-repaint can raise the flag once.\n    --on-prompt human keeps waiting for it, same as the other two.\n\n    On opencode the commonest cause has a name and a one-key fix. If its\n    sidebar is on -- ctrl+x b, or \"Show sidebar\" in its ctrl+p palette -- it\n    shares screen rows with the transcript, covers the marker that ends a\n    turn, and every frame after that reads running/unknown_frame. wait says\n    so on stderr (paneObstruction=opencode_sidebar) and capture --json\n    publishes the same field. Press ctrl+x b in the pane to close it; Escape\n    does not.\n\n    An opencode DIALOG is the other one, and it exits 10 as selection_list\n    rather than waiting out the dwell. Its session list (ctrl+x l), agent list\n    (ctrl+x a), timeline (ctrl+x g), command palette (ctrl+p) and pickers are\n    painted over the transcript, so the marker of the previous turn is still\n    on the pane behind them -- which is what used to make wait report a\n    blocked pane as Completed. sessionStatusReason is opencode_modal_overlay\n    and Escape closes all of them.\n\n  --verify turns \"the agent stopped\" into \"the work passes the repository's own\n  checks\". Verification only runs when completion was detected: a prompt (10) or\n  a timeout (124) is reported as-is and never verified. With several worktrees,\n  gates run one worktree at a time because the server caps concurrent runs.\n\n### commandmate verify <worktree-id>\n  Run the gates declared in .commandmate/verify.yaml against a worktree.\n\n  Options:\n    --gates <id1,id2>     Gate ids to run (default: work-evidence + all declared)\n    --instance <id>       Attribute the run to an agent instance\n    --timeout <seconds>   Stop polling after N seconds (exit 124)\n    --json                Print the run and its gate results as JSON on stdout\n\n  Exit codes:\n    0   - Every gate passed\n    20  - A gate failed, timed out, or errored\n    21  - work-evidence found nothing to verify (no commits, no changes)\n    99  - The run produced no verdict (bad verify.yaml, gates skipped, cancelled)\n    124 - --timeout elapsed while the run was still going\n\n  Output (progress on stderr, verdict on stdout):\n    GATE work-evidence PASS (commits=3, uncommitted=2)\n    GATE lint PASS (exit=0, 12.3s)\n    GATE unit FAIL (exit=1, 45.0s)\n    RESULT failed\n\n  Gates run in the worktree's own directory. Gates are skipped (run status 99,\n  never 0) in the checkout the server itself runs from when verify.yaml sets\n  options.skipInPrimaryCheckout, so a 'build' gate cannot replace the assets the\n  live app is serving.\n\n### commandmate verify history / commandmate verify show <run-id>\n  Read past verification runs. Both are read-only and never start a run, so\n  neither returns 20 or 21 \u2014 those mean \"this tree failed verification\", and a\n  question about history is not a verdict on the current tree.\n\n  commandmate verify history                          # every worktree, newest 50\n  commandmate verify history --worktree <id>          # one worktree\n  commandmate verify history --days 14 --limit 100    # window and page size\n  commandmate verify history --json                   # JSON array on stdout\n  commandmate verify show 42                          # gates + log tails\n  commandmate verify show 42 --json\n\n  history options:\n    --worktree <id>       Restrict to one worktree (default: all)\n    --days <n>            Look back n days, 1..90 (default: no lower bound)\n    --limit <n>           Maximum runs, 1..500 (default: 50)\n\n  One run per line. The leading #<run-id> is what \"verify show\" takes:\n    #42  2026-07-31T04:12:00.000Z  myrepo-feature-101  manual  failed  failed: unit,build\n\n  The listing carries gate verdicts but NOT gate log bodies \u2014 logTail is absent\n  from the JSON, not null. Use \"verify show <run-id>\" when you need the log.\n\n  Exit codes:\n    0   - Read succeeded (also when nothing matched: stderr note, or [] in JSON)\n    2   - Bad argument (--days/--limit out of range, bad worktree or run id)\n    99  - No such run (404), or an unexpected failure\n\n### commandmate respond <worktree-id> \"<answer>\"\n  Respond to an agent's prompt.\n\n  commandmate respond <id> \"yes\"          # Yes/No\n  commandmate respond <id> \"2\"            # Multiple choice (number)\n  commandmate respond <id> \"custom text\"  # Free text\n  commandmate respond <id> \"yes\" --instance codex-2   # Specific instance\n\n  Exit codes:\n    0  - Response sent\n    99 - Prompt already dismissed (prompt_no_longer_active)\n\n### commandmate interrupt <worktree-id>\n  Interrupt the turn an agent is generating (the GUI's interrupt button).\n  Not 'stop' -- that stops the CommandMate server.\n\n  commandmate interrupt <id>                    # Every running session of the worktree\n  commandmate interrupt <id> --instance codex-2 # Only that instance\n  commandmate interrupt <id> --json             # { success, message, interrupted[] }\n\n  Omitting --instance is a broadcast, not \"the primary instance\": the route\n  interrupts every session that is running. There is no --agent (wait's rule:\n  a tool name does not say which session).\n\n  Exit codes:\n    0  - At least one session was interrupted\n    30 - The worktree exists but nothing was running (nothing was interrupted)\n    99 - No such worktree\n\n### commandmate capture <worktree-id>\n  Get current terminal output.\n\n  commandmate capture <id>                   # Plain text\n  commandmate capture <id> --json            # JSON with status info\n  commandmate capture <id> --instance codex  # Specific instance\n\n### commandmate auto-yes <worktree-id>\n  Control auto-yes (automatic prompt response).\n\n  commandmate auto-yes <id> --enable                    # Enable (default 1h)\n  commandmate auto-yes <id> --enable --duration 3h      # With duration\n  commandmate auto-yes <id> --enable --stop-pattern \"error\"\n  commandmate auto-yes <id> --disable                   # Disable\n  commandmate auto-yes <id> --enable --instance codex-2 # Scoped to one instance\n\n  --stop-pattern matches new terminal output, not the commands an agent runs.\n  It cannot block a command; a build log that merely prints the pattern\n  (e.g. \"rm -rf\" in an npm script) also triggers it and stops auto-yes.\n  To suppress auto-responses for risky prompts, use the task contract's\n  autoYes.denyPatterns instead (docs/design/task-contract.md).\n\n### commandmate instances <worktree-id> [action] [args]\n  Discover and manage a worktree's agent-instance roster (1 agent, multiple sessions).\n\n  commandmate instances <id>                            # List roster + running/auto-yes status\n  commandmate instances <id> --json                     # JSON output\n  commandmate instances <id> add --agent codex          # Add an instance (auto-generates ID, e.g. codex-2)\n  commandmate instances <id> add --agent codex --alias \"Review\" --id codex-3\n  commandmate instances <id> remove <instance-id>       # Remove from roster\n  commandmate instances <id> remove <instance-id> --kill  # Remove and kill its session\n  commandmate instances <id> alias <instance-id> \"New Name\"\n  commandmate instances <id> kill <instance-id>         # Kill only that instance's session\n\n  See \"Multi-Session\" below for the ID convention and roster semantics.\n\n### commandmate skill <subcommand>\n  Manage official Agent Skills. Every subcommand is a thin client over the same\n  APIs the browser UI uses: the CLI never downloads, extracts, writes or deletes\n  anything itself, and never sends a filesystem path, artifact URL, file list or\n  checksum (the API rejects those outright).\n\n  commandmate skill list [--json] [--prerelease]\n  commandmate skill info <skill-id> [--version <v>] [--json]\n  commandmate skill plan <skill-id> --worktree <id> [--version <v>] [--json]\n  commandmate skill install <skill-id> --worktree <id> --version <exact> [--dry-run] [--yes] [--ack-risk <id>@<version>] [--json]\n  commandmate skill uninstall <skill-id> --worktree <id> [--dry-run] [--yes] [--json]\n  commandmate skill status <skill-id> --worktree <id> [--json]\n\n  Confirmation contract (writes = install / uninstall):\n    - A plan is always built and shown first. --dry-run stops there.\n    - Without a TTY, a write REQUIRES --yes. A missing --yes is refused, never\n      assumed: an environment that cannot prompt must not install silently.\n    - A high-risk Skill additionally requires --ack-risk <skill-id>@<version>\n      with the exact id and version. --yes alone never carries a high-risk\n      install, in a TTY or out of one.\n\n  Exit codes:\n    0   success\n    1   the server or the Catalog could not be reached (retryable)\n    2   invalid arguments, unknown Skill or unknown version\n    11  the worktree refused it (local change, conflict, lock, plan drift)\n    12  the write was never confirmed (no --yes, declined, or missing --ack-risk)\n    13  files changed but the operation needs reconciliation\n\n  --json prints the API response body verbatim on stdout; diagnostics, prompts\n  and errors always go to stderr, so a failed --json run leaves stdout empty.\n\n  'skill status' reports one Skill in one worktree, read from the install\n  receipt on disk. There is no per-worktree listing endpoint yet, so <skill-id>\n  is required.\n\n## Multi-Session (1 agent, multiple sessions)\n\n  A worktree can run several sessions of the same CLI tool concurrently. Each\n  session is an \"instance\" identified by an instance ID:\n    <agent>        - the agent's primary instance (e.g. \"claude\")\n    <agent>-<n>    - an additional instance, n >= 2 (e.g. \"claude-2\", \"claude-3\")\n\n  --instance is accepted by send / wait / respond / capture / auto-yes.\n  send --instance auto-starts the session if it is not already running.\n\n  --instance alone is the recommended way to name a target (Issue #1638). It is\n  the only flag all five commands share: --agent is rejected by 'wait'. A\n  rostered instance already carries its CLI tool (Issue #1629), and an instance\n  id that is itself a tool id resolves to that tool's primary instance even\n  without a roster entry, so '--instance codex' needs no --agent.\n\n  --agent remains accepted by send / respond / capture / auto-yes as the\n  supplement for ad-hoc instances the roster does not know -- notably\n  '--register', which cannot infer the tool from an id like codex-3. Passing an\n  --agent that contradicts the roster is an error (exit 2), not an override.\n\n  The roster (visible in the browser UI's Agent panel) is the list of known\n  instances with aliases and display order. Ad-hoc sessions started via\n  'send --instance' do NOT appear in the roster unless registered:\n    commandmate send <id> \"...\" --instance claude-2 --register\n  Without --register, the session still runs and responds to CLI commands,\n  but it will not show up in the UI sidebar/roster until added there or via\n  'commandmate instances <id> add'.\n\n  Per-instance auto-yes: --instance scopes --auto-yes/--duration/--stop-pattern\n  to that specific session, independent of other instances of the same agent.\n\n  commandmate instances <id>                        # discover valid --instance values\n  commandmate send <id> \"task\" --instance codex-2 --auto-yes\n  commandmate wait <id> --instance codex-2 --timeout 600\n  commandmate capture <id> --instance codex-2\n\n## All Exit Codes\n\n  0   SUCCESS          - Completed successfully\n  1   DEPENDENCY_ERROR - Server not running\n  2   CONFIG_ERROR     - Validation error (invalid agent, duration, etc.)\n  10  PROMPT_DETECTED  - Prompt detected during wait\n  20  VERIFY_FAILED    - A verification gate failed (verify, wait --verify)\n  21  NOT_STARTED      - Nothing to verify: no commits, no uncommitted changes\n  30  NO_ACTIVE_SESSIONS - interrupt found no running session to interrupt\n  99  UNEXPECTED_ERROR - Unexpected error / resource not found / no verdict\n  124 TIMEOUT          - Wait or verification timeout exceeded\n\n  When one 'wait' covers several worktrees, the reported code is the highest\n  priority one observed: 10 > 20 > 21 > 124.\n\n## Troubleshooting\n\n  Server not running:\n    commandmate start --daemon\n    CM_PORT=3011 commandmate ls        # Different port\n\n  Worktree not found:\n    commandmate ls --quiet             # Check registered IDs\n    commandmate sync                   # Sync new worktrees (e.g. after git worktree add)\n    commandmate status                 # Confirm 'ls' and 'status' report the same Port\n                                       # (with several servers running, an exported CM_PORT\n                                       #  points 'ls' at a different one)\n\n  Authentication:\n    CM_AUTH_TOKEN=your-token commandmate ls\n";
 export declare const AGENT_OPERATIONS_SAMPLES = "# CLI Agent Operations - Workflow Samples\n\nCopy and adapt these patterns for your use case.\n\n## 1. Basic: send, wait, capture\n\n  WT=$(commandmate ls --branch feature/101 --quiet)\n  commandmate send \"$WT\" \"Implement Issue #101 with TDD\"\n  commandmate wait \"$WT\" --timeout 600\n  commandmate capture \"$WT\"\n\n## 2. With Auto-Yes (unattended execution)\n\n  WT=$(commandmate ls --branch feature/101 --quiet)\n  commandmate send \"$WT\" \"Implement Issue #101\" --auto-yes --duration 3h\n  commandmate wait \"$WT\" --timeout 1800\n  commandmate auto-yes \"$WT\" --disable    # Disable for safety\n  commandmate capture \"$WT\" --json\n\n## 3. Prompt Response Loop\n\n  WT=$(commandmate ls --branch feature/101 --quiet)\n  commandmate send \"$WT\" \"Refactor this module\"\n\n  while true; do\n    commandmate wait \"$WT\" --timeout 600 --on-prompt agent\n    EXIT_CODE=$?\n\n    if [ $EXIT_CODE -eq 0 ]; then\n      echo \"Done\"\n      break\n    elif [ $EXIT_CODE -eq 10 ]; then\n      commandmate respond \"$WT\" \"yes\"\n    elif [ $EXIT_CODE -eq 124 ]; then\n      echo \"Timeout\"\n      break\n    fi\n  done\n\n  commandmate capture \"$WT\"\n\n## 4. Parallel Worktrees\n\n  WT1=$(commandmate ls --branch feature/101 --quiet)\n  WT2=$(commandmate ls --branch feature/102 --quiet)\n\n  commandmate send \"$WT1\" \"Implement #101\" --auto-yes\n  commandmate send \"$WT2\" \"Implement #102\" --auto-yes --instance codex\n\n  # One --instance covers every worktree id in the call, so worktrees on\n  # different instances need one wait each. Both agents keep running while the\n  # first wait blocks, so this costs no wall clock over a combined wait.\n  # A bare 'wait \"$WT2\"' would watch WT2's DEFAULT agent, not the codex session:\n  # 'wait' has no --agent to correct that with.\n  commandmate wait \"$WT1\" --timeout 1800\n  commandmate wait \"$WT2\" --instance codex --timeout 1800\n\n  commandmate capture \"$WT1\" --json\n  commandmate capture \"$WT2\" --instance codex --json\n\n## 5. Check status before sending\n\n  # Find worktrees and check status\n  commandmate ls --json | python3 -c \"\n  import sys, json\n  for wt in json.load(sys.stdin):\n      if wt['name'].startswith('feature/'):\n          print(f\\\"{wt['id']}  {wt['name']}\\\")\n  \"\n\n## 6. Error handling pattern\n\n  WT=$(commandmate ls --branch feature/101 --quiet)\n\n  if [ -z \"$WT\" ]; then\n    echo \"Error: worktree not found\"\n    exit 1\n  fi\n\n  commandmate send \"$WT\" \"Fix the bug\" --auto-yes\n  commandmate wait \"$WT\" --timeout 600\n  EXIT_CODE=$?\n\n  case $EXIT_CODE in\n    0)   echo \"Success\"; commandmate capture \"$WT\" ;;\n    10)  echo \"Prompt detected\"; commandmate respond \"$WT\" \"yes\" ;;\n    124) echo \"Timeout\"; commandmate capture \"$WT\" --json ;;\n    *)   echo \"Error: exit $EXIT_CODE\" ;;\n  esac\n\n## 7. Multi-Session: run a second Codex session alongside the primary agent\n\n  WT=$(commandmate ls --branch feature/101 --quiet)\n\n  # Discover the roster before picking an --instance value\n  commandmate instances \"$WT\"\n\n  # Register a second Codex instance, then send/wait/capture scoped to it.\n  # Once it is in the roster, --instance alone carries the CLI tool.\n  commandmate instances \"$WT\" add --agent codex --alias \"Review\"\n  commandmate send \"$WT\" \"Review the diff\" --instance codex-2 --auto-yes\n  commandmate wait \"$WT\" --instance codex-2 --timeout 600\n  commandmate capture \"$WT\" --instance codex-2 --json\n\n  # Ad-hoc instance without pre-registering (still runs; register to show in UI).\n  # --agent is required here: codex-3 is not in the roster yet, so nothing else\n  # says which CLI tool to start.\n  commandmate send \"$WT\" \"Quick check\" --agent codex --instance codex-3 --register\n\n  # Clean up when done\n  commandmate instances \"$WT\" remove codex-2 --kill\n\n## 8. Verify the work instead of trusting \"the agent stopped\"\n\n  WT=$(commandmate ls --branch feature/101 --quiet)\n  commandmate send \"$WT\" \"Implement Issue #101 with TDD\" --auto-yes\n\n  # One call: wait for completion, then run every gate in .commandmate/verify.yaml\n  commandmate wait \"$WT\" --timeout 1800 --verify\n  case $? in\n    0)  echo \"Verified\" ;;\n    10) commandmate respond \"$WT\" \"yes\" ;;\n    20) echo \"A gate failed\"; commandmate verify \"$WT\" --json ;;\n    21) echo \"The agent produced nothing\" ;;\n  esac\n\n  # Cheap pre-check: is there any work at all, before paying for the full suite?\n  commandmate wait \"$WT\" --require-work || echo \"no commits and no changes\"\n\n  # Re-run a subset after a fix, without waiting on the agent\n  commandmate verify \"$WT\" --gates lint,unit\n";
 //# sourceMappingURL=agent-operations.d.ts.map

package/dist/cli/docs/agent-operations.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"agent-operations.d.ts","sourceRoot":"","sources":["../../../src/cli/docs/agent-operations.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH,eAAO,MAAM,sBAAsB,stkBA+VlC,CAAC;AAEF,eAAO,MAAM,wBAAwB,klJAmIpC,CAAC"}
+{"version":3,"file":"agent-operations.d.ts","sourceRoot":"","sources":["../../../src/cli/docs/agent-operations.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH,eAAO,MAAM,sBAAsB,0goBAiYlC,CAAC;AAEF,eAAO,MAAM,wBAAwB,klJAmIpC,CAAC"}

package/dist/cli/docs/agent-operations.js

@@ -149,6 +149,22 @@ These commands enable coding agents (Claude Code, Codex, etc.) to orchestrate ot
     needs the dwell: a capture taken mid-repaint can raise the flag once.
     --on-prompt human keeps waiting for it, same as the other two.
 
+    On opencode the commonest cause has a name and a one-key fix. If its
+    sidebar is on -- ctrl+x b, or "Show sidebar" in its ctrl+p palette -- it
+    shares screen rows with the transcript, covers the marker that ends a
+    turn, and every frame after that reads running/unknown_frame. wait says
+    so on stderr (paneObstruction=opencode_sidebar) and capture --json
+    publishes the same field. Press ctrl+x b in the pane to close it; Escape
+    does not.
+
+    An opencode DIALOG is the other one, and it exits 10 as selection_list
+    rather than waiting out the dwell. Its session list (ctrl+x l), agent list
+    (ctrl+x a), timeline (ctrl+x g), command palette (ctrl+p) and pickers are
+    painted over the transcript, so the marker of the previous turn is still
+    on the pane behind them -- which is what used to make wait report a
+    blocked pane as Completed. sessionStatusReason is opencode_modal_overlay
+    and Escape closes all of them.
+
   --verify turns "the agent stopped" into "the work passes the repository's own
   checks". Verification only runs when completion was detected: a prompt (10) or
   a timeout (124) is reported as-is and never verified. With several worktrees,
@@ -221,6 +237,23 @@ These commands enable coding agents (Claude Code, Codex, etc.) to orchestrate ot
     0  - Response sent
     99 - Prompt already dismissed (prompt_no_longer_active)
 
+### commandmate interrupt <worktree-id>
+  Interrupt the turn an agent is generating (the GUI's interrupt button).
+  Not 'stop' -- that stops the CommandMate server.
+
+  commandmate interrupt <id>                    # Every running session of the worktree
+  commandmate interrupt <id> --instance codex-2 # Only that instance
+  commandmate interrupt <id> --json             # { success, message, interrupted[] }
+
+  Omitting --instance is a broadcast, not "the primary instance": the route
+  interrupts every session that is running. There is no --agent (wait's rule:
+  a tool name does not say which session).
+
+  Exit codes:
+    0  - At least one session was interrupted
+    30 - The worktree exists but nothing was running (nothing was interrupted)
+    99 - No such worktree
+
 ### commandmate capture <worktree-id>
   Get current terminal output.
 
@@ -338,6 +371,7 @@ These commands enable coding agents (Claude Code, Codex, etc.) to orchestrate ot
   10  PROMPT_DETECTED  - Prompt detected during wait
   20  VERIFY_FAILED    - A verification gate failed (verify, wait --verify)
   21  NOT_STARTED      - Nothing to verify: no commits, no uncommitted changes
+  30  NO_ACTIVE_SESSIONS - interrupt found no running session to interrupt
   99  UNEXPECTED_ERROR - Unexpected error / resource not found / no verdict
   124 TIMEOUT          - Wait or verification timeout exceeded
 

package/dist/cli/program.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"program.d.ts","sourceRoot":"","sources":["../../src/cli/program.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH,OAAO,EAAE,OAAO,EAAU,MAAM,WAAW,CAAC;AAgE5C;;;;;;;GAOG;AACH,wBAAgB,YAAY,IAAI,OAAO,CAmLtC"}
+{"version":3,"file":"program.d.ts","sourceRoot":"","sources":["../../src/cli/program.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH,OAAO,EAAE,OAAO,EAAU,MAAM,WAAW,CAAC;AAoE5C;;;;;;;GAOG;AACH,wBAAgB,YAAY,IAAI,OAAO,CA4LtC"}

package/dist/cli/program.js

@@ -22,6 +22,8 @@ const sync_1 = require("./commands/sync");
 const send_1 = require("./commands/send");
 const wait_1 = require("./commands/wait");
 const respond_1 = require("./commands/respond");
+// Issue #2101: CLI face of POST /api/worktrees/:id/interrupt
+const interrupt_1 = require("./commands/interrupt");
 const capture_1 = require("./commands/capture");
 const auto_yes_1 = require("./commands/auto-yes");
 const verify_1 = require("./commands/verify");
@@ -32,6 +34,8 @@ const report_1 = require("./commands/report");
 const instances_1 = require("./commands/instances");
 // Issue #1237: Skill management as a thin client over the Skill APIs
 const skill_1 = require("./commands/skill");
+// Issue #1937 (R9): expose the server to a phone and pair it with a QR code
+const remote_1 = require("./commands/remote");
 // Issue #1195: Guided quickstart for bare `npx commandmate`
 const quickstart_1 = require("./commands/quickstart");
 const prompt_1 = require("./utils/prompt");
@@ -207,6 +211,10 @@ function buildProgram() {
     program.addCommand((0, send_1.createSendCommand)());
     program.addCommand((0, wait_1.createWaitCommand)());
     program.addCommand((0, respond_1.createRespondCommand)());
+    // Issue #2101: stop the turn an agent is generating. Registered next to
+    // `respond` because the two are the pair that act on a LIVE turn; `stop`
+    // above stops the CommandMate server and is not related.
+    program.addCommand((0, interrupt_1.createInterruptCommand)());
     program.addCommand((0, capture_1.createCaptureCommand)());
     program.addCommand((0, auto_yes_1.createAutoYesCommand)());
     // Issue #1544: verification gates (.commandmate/verify.yaml)
@@ -219,6 +227,10 @@ function buildProgram() {
     program.addCommand((0, instances_1.createInstancesCommand)());
     // Issue #1237: Skill management (catalog / plan / install / uninstall / status)
     program.addCommand((0, skill_1.createSkillCommand)());
+    // Issue #1937 (R9): `remote` composes start + a Provider tunnel + pairing.
+    // Registered next to the server lifecycle commands it builds on rather than
+    // with the agent-orchestration group, which it has nothing to do with.
+    program.addCommand((0, remote_1.createRemoteCommand)());
     // Issue #264: AI Tool Integration help section
     program.addHelpText('after', `
 AI Tool Integration:

package/dist/cli/types/api-responses.d.ts

@@ -90,6 +90,31 @@ export interface AgentInstance {
     alias: string;
     order: number;
 }
+/**
+ * Mirrors: src/app/api/worktrees/[id]/opencode/session/route.ts GET response
+ * (Issue #2038).
+ *
+ * opencode-only. Every field is nullable because the interesting case is a
+ * **stopped** instance: the session id there is what the next launch will pass
+ * to `opencode -s <id>`, and nothing is running to describe it.
+ */
+export interface OpencodeInstanceSession {
+    instanceId: string;
+    /** opencode's `Session.id`, or null when nothing has been recorded yet. */
+    sessionId: string | null;
+    /** opencode's `Session.title`, or null. Display only. */
+    title: string | null;
+    /** The directory opencode reported the session belongs to, or null. */
+    worktreePath: string | null;
+    /** Epoch ms the memory was written, or null. */
+    updatedAt: number | null;
+    /** Whether an opencode server is currently attached to this instance. */
+    live: boolean;
+}
+/** Mirrors: the same route's GET body (Issue #2038). */
+export interface OpencodeSessionsResponse {
+    instances: OpencodeInstanceSession[];
+}
 export interface WorktreeDetailResponse extends WorktreeItem {
     agentInstances: AgentInstance[];
 }
@@ -333,6 +358,36 @@ export interface CurrentOutputResponse {
              * what has expired is the server's ability to answer it automatically.
              */
             deliveryExpired: boolean;
+            /**
+             * Whether a human is being asked to approve or to choose (Issue #2040).
+             *
+             * `permission` / `question`. The two block a worker identically and are
+             * answered completely differently — three fixed verdicts against the
+             * agent's own published choices — so a reader deciding whether to answer
+             * at all has to see this first.
+             *
+             * String-typed and optional for this file's two usual reasons: a newer
+             * server may name a third kind, and a server from before #2040 sends no
+             * such key. Absent means "this daemon predates the field", never
+             * "unknown".
+             */
+            kind?: string;
+            /**
+             * The choices a pending question offers, or null (Issue #2040).
+             *
+             * Null on every approval — an approval's three verdicts belong to the
+             * SOURCE and are published as `promptData.decisionOptions` — and null on a
+             * question whose payload is no longer held, because the numbers are the
+             * payload's own order and quoting them from anything else would number a
+             * list the agent never sent.
+             *
+             * These are the numbers `commandmate respond <worktree> <n>` resolves
+             * against on an agent that publishes decision ids.
+             */
+            questionOptions?: Array<{
+                number: number;
+                label: string;
+            }> | null;
         }>;
         /**
          * What this instance has had dropped by the structured layer's own bounds,
@@ -477,10 +532,171 @@ export interface CurrentOutputResponse {
                 permissionHookPredictsDialog: boolean;
                 sessionStartMayArriveLate: boolean;
                 permissionReplyReleasesPrompt: boolean;
+                /**
+                 * Where a frame-unique id for this source comes from, or null.
+                 *
+                 * Non-null is what makes an option number a VERDICT the server can POST
+                 * rather than a key it has to type, which is the gate `commandmate
+                 * respond` reads before choosing an endpoint (Issue #2040).
+                 */
                 eventIdentity: string | null;
                 resync: string;
             };
+            /**
+             * Which machinery is speaking for this pane right now (Issue #2054).
+             *
+             * `sse` / `hooks` / `scraper` — **string-typed, and optional, for the two
+             * reasons the block above already gives.** A server newer than this CLI
+             * can name a transport this build has never heard of, and a server older
+             * than #2054 sends no `kind` at all; narrowing to the union would turn
+             * both into a parse failure on a payload the reader could otherwise print.
+             */
+            kind?: string;
+            /**
+             * Why this pane is not on the machinery its tool declares (Issue #2054).
+             *
+             * A token — `port_identity_changed`, `heartbeat_stale`, `not_subscribed`,
+             * or whatever the transport recorded. Absent when nothing is degraded, and
+             * absent on every push tool.
+             */
+            degradedReason?: string;
+            /** `live` / `stale`, or absent. Issue #2054, string-typed as above. */
+            liveness?: string;
+            /**
+             * What the source said about this instance's activity when its stream was
+             * last attached, or null (Issue #2054).
+             *
+             * A record of one instant — `at` is when it was asked — and not a live
+             * reading: `capture --json | jq '.structuredEvents.source.probedActivity'`
+             * answers "was the pane mid-turn when CommandMate connected?", which is a
+             * question the stream itself cannot answer until the turn ends. Null for
+             * every tool that is not a subscription source.
+             */
+            probedActivity?: {
+                activity: string | null;
+                at: number;
+            } | null;
         };
+        /**
+         * What the agent says about the conversation this instance is in, or null
+         * (Issue #2040).
+         *
+         * Mirrors: src/lib/hooks/agent-session-telemetry.ts AgentSessionRecord.
+         *
+         * The half of a worker's state a terminal frame cannot show — which
+         * session, which persona, which model, what it has cost. Read off frames
+         * the server was already receiving, so it costs no request; null on every
+         * tool that publishes none (all but opencode today), on an opencode pane
+         * whose stream has not reported a session yet, and on one that has been
+         * killed since it did.
+         *
+         * Every value is the agent's own, unrounded and unformatted: a reader
+         * compares them against what the agent reports about itself, and tidying on
+         * the way out breaks that comparison exactly when it matters.
+         */
+        session?: {
+            /** The agent's own session id, or null. */
+            id: string | null;
+            /** The agent's own title for it, or null. Display only, bounded. */
+            title: string | null;
+            /** Which persona is driving (opencode's `build` / `plan` / …), or null. */
+            agent: string | null;
+            /** The model id, verbatim, or null. */
+            model: string | null;
+            /** The provider that model belongs to, verbatim, or null. */
+            provider: string | null;
+            /** What the session has cost so far, in the agent's own unit, or null. */
+            cost: number | null;
+            /**
+             * The tokens spent, as the agent counts them.
+             *
+             * Null members mean "the agent did not say", never zero. `cacheRead` /
+             * `cacheWrite` are opencode's `tokens.cache.read` / `.write`, flattened;
+             * `total` is declared on an assistant message rather than on a session, so
+             * it is null today and is NOT this server's own sum of the other five.
+             */
+            tokens: {
+                input: number | null;
+                output: number | null;
+                reasoning: number | null;
+                cacheRead: number | null;
+                cacheWrite: number | null;
+                total: number | null;
+            };
+            /** Epoch ms this record was written, so a reader can judge its age. */
+            at: number;
+        } | null;
+        /**
+         * How full this instance's context window is, or null (Issue #2042).
+         *
+         * Mirrors: src/lib/hooks/agent-session-telemetry.ts
+         * AgentSessionContextUsage.
+         *
+         * **Not derivable from `session.tokens`, which is why it is its own block.**
+         * Those counts are the session's *cumulative* spend — the figure `opencode
+         * stats` prints — while "how much of the window is in use" is the last
+         * finished assistant turn's footprint. Measured over two turns the session
+         * summed to 16,999 (`2%`) where opencode's own footer read 8,508 (`1%`), and
+         * the gap widens with every turn.
+         *
+         * Every member here is computed by the server from two reads of the agent's
+         * own API, so unlike `session` this block is *derived*: `percent` is
+         * opencode's own `round(tokens / limit.context * 100)`, transcribed from
+         * 1.18.22 rather than guessed.
+         *
+         * Optional, and null until the first measurement lands — it is refreshed off
+         * the poll path, so the poll that notices a turn ended publishes the
+         * previous numbers and the next one publishes the new. Null forever on every
+         * tool but opencode.
+         */
+        sessionContext?: {
+            /** The last finished assistant turn's token footprint, or null. */
+            tokens: number | null;
+            /** The model's declared context window (`limit.context`), or null. */
+            limit: number | null;
+            /** `round(tokens / limit * 100)`, or null when either input is null. */
+            percent: number | null;
+            /** The `session.at` these numbers were measured against. */
+            sessionAt: number;
+            /** Epoch ms this record was written. */
+            at: number;
+        } | null;
+        /**
+         * What the last opencode turn changed on disk (Issue #2043), or null.
+         *
+         * Mirrors: src/lib/hooks/sources/opencode/diff.ts
+         * OpencodeSessionDiffRecord.
+         *
+         * **`files` and `revertedFiles` are different questions.** `files` is what
+         * the turn named by `turnMessageId` changed, read from
+         * `GET /session/:id/diff?messageID=...` — the only call measured to answer
+         * it on 1.18.22. `revertedFiles` is what a revert is holding back right now,
+         * off the `session.diff` frame, and is empty whenever nothing is reverted.
+         *
+         * Issue #2043 assumed `session.diff` carried the first of these. It does
+         * not: every `session.diff` frame of two file-editing turns carried
+         * `diff: []`, including the one emitted alongside `session.idle`. See
+         * `docs/design/opencode-server-live-verification.md` §16.
+         *
+         * Optional and null for every tool but opencode, and for an opencode pane
+         * whose stream has not reported a turn yet.
+         */
+        sessionDiff?: {
+            /** The session these files belong to, or null. */
+            sessionId: string | null;
+            /** The user message whose turn `files` describes, or null. */
+            turnMessageId: string | null;
+            /** What that turn changed. Empty until the read has answered. */
+            files: AgentSessionDiffFile[];
+            /** Epoch ms `files` was read at, or null when it never was. */
+            filesAt: number | null;
+            /** What a revert is holding back. Empty when nothing is. */
+            revertedFiles: AgentSessionDiffFile[];
+            /** The message a revert is holding back to, or null. */
+            revertedMessageId: string | null;
+            /** Epoch ms the newest frame that touched this record arrived. */
+            at: number;
+        } | null;
     };
     /**
      * Issue #1839: the upstream (model API) fault visible on the live frame, or
@@ -507,6 +723,36 @@ export interface CurrentOutputResponse {
         /** Epoch ms the frame was captured. */
         at: number;
     } | null;
+    /**
+     * Issue #2095: a second column sharing rows with the agent's transcript, or
+     * null when the frame's layout could not be read as two columns.
+     *
+     * Mirrors: src/lib/session/current-output-builder.ts
+     * CurrentOutputPayload.paneObstruction
+     *
+     * **null is not an all-clear**, for the same reason {@link upstreamFault}'s is
+     * not: an opencode permission dialog removes the border row the geometry is
+     * measured from, and no tool other than opencode is examined at all.
+     *
+     * The one value shipped is `opencode_sidebar` — opencode's own sidebar, turned
+     * on by `ctrl+x b` or by its `ctrl+p` palette, painted across the same rows as
+     * the transcript and the input box. It hides the marker that ends a turn, so
+     * the pane reads `running` / `unknown_frame` until it is closed. `wait` does
+     * not branch on this field; it names it in the message it already prints for
+     * an unclassified frame.
+     *
+     * Optional here for the same reason as every other field on this mirror: an
+     * older daemon sends nothing, and the CLI is routinely newer than the server
+     * it dials.
+     */
+    paneObstruction?: {
+        /** `opencode_sidebar`. */
+        id: string;
+        /** The second column's own text, trimmed and bounded to 200 UTF-8 bytes. */
+        matchedText: string;
+        /** Epoch ms the frame was captured. */
+        at: number;
+    } | null;
     /**
      * Issue #1785: the model the session is running, or null when nothing knows.
      *
@@ -651,6 +897,39 @@ export interface PromptData {
         label: string;
         reply: string;
     }>;
+    /**
+     * The agent's own id for the decision this dialog is (Issue #1932 / #2100).
+     *
+     * Mirrors: src/lib/session/structured-prompt.ts
+     * StructuredPromptWaitingData.decisionId.
+     *
+     * `null` is a real answer — "this server looked and there is no addressable
+     * decision" — and is distinct from the field being absent, which means a
+     * daemon from before #2031 sent no such key at all. Present for BOTH kinds of
+     * addressable decision since #2100: an approval, whose replies are
+     * {@link decisionOptions}, and a question, whose replies are the numbered
+     * choices published on `structuredEvents.pendingDecisions[].questionOptions`.
+     * The two are never published together — see the note on
+     * `readPromptQuestionChoices`.
+     */
+    decisionId?: string | null;
+    /**
+     * What the agent asked, when this dialog is an `AskUserQuestion`-style call
+     * (Issue #1726).
+     *
+     * Mirrors: src/lib/session/structured-prompt.ts
+     * StructuredAskUserQuestionSummary.
+     *
+     * Whether the numbers here may be ANSWERED is not a property of this field:
+     * it is `decisionId` plus `questionCount === 1` plus the absence of
+     * {@link decisionOptions}. Claude publishes this summary for a picker only
+     * its pane can see, with no id to deliver an answer to.
+     */
+    askUserQuestion?: {
+        question: string;
+        labels: string[];
+        questionCount: number;
+    };
     [key: string]: unknown;
 }
 export interface PromptMessageResponse {
@@ -696,6 +975,50 @@ export interface PromptResponseResult {
         decisionId?: string;
     };
 }
+/**
+ * Mirrors: src/app/api/worktrees/[id]/respond/structured-decision.ts, the body
+ * of `POST /api/worktrees/[id]/respond` for the two id-less shapes
+ * (Issue #2040).
+ *
+ * A different route from {@link PromptResponseResult} and therefore a different
+ * mirror, even though `respond` reports both through the same lines. The
+ * difference that matters is `resolved.via`: this route answers a QUESTION as
+ * well as an approval, and a question's answer is a list of labels rather than
+ * one verdict — so `optionNumber` / `optionLabel` are absent on that branch and
+ * `answers` / `optionNumbers` / `optionLabels` / `freeText` take their place.
+ *
+ * Every field is optional for this file's usual reason: the CLI is routinely
+ * newer than the daemon it dials, and a server from before #2040 answers this
+ * body's shape only for the `{ decisionId, answer }` request.
+ */
+export interface StructuredDecisionResult {
+    /** False when the verdict was resolved but the POST to the agent did not land. */
+    success: boolean;
+    /** The option number for an approval; the chosen numbers, or the text, for a question. */
+    answer: string;
+    /** `decision_not_delivered` — the only reason this shape carries on a 200. */
+    reason?: string;
+    /** Detail accompanying a reason, when the server sent one. */
+    message?: string;
+    resolved?: {
+        /** `structured-decision` for an approval, `structured-question` for a question. */
+        via: 'structured-decision' | 'structured-question';
+        /** Approval only: 1 = Allow once, 2 = Allow always, 3 = Reject. */
+        optionNumber?: number;
+        /** Approval only: the verdict's label. */
+        optionLabel?: string;
+        /** The decision that was answered. */
+        decisionId?: string;
+        /** Question only: exactly what went on the wire — one array of labels per question. */
+        answers?: string[][];
+        /** Question only: the numbers the answer named, empty for free text. */
+        optionNumbers?: number[];
+        /** Question only: the labels those numbers named. */
+        optionLabels?: string[];
+        /** Question only: whether this was prose the agent never offered as a choice. */
+        freeText?: boolean;
+    };
+}
 /**
  * Mirrors: src/app/api/worktrees/[id]/auto-yes/route.ts AutoYesResponse
  * [Issue #1898, extended by Issue #1909].
@@ -1491,4 +1814,56 @@ export interface TaskDetailResponse {
     task: TaskView;
     lastVerificationRun: VerificationRunView | null;
 }
+/**
+ * One file in `structuredEvents.sessionDiff` (Issue #2043).
+ *
+ * Mirrors: src/lib/hooks/sources/opencode/client.ts OpencodeFileDiff.
+ *
+ * `file`, `patch` and `status` are nullable because opencode's own OpenAPI
+ * marks only `additions` and `deletions` required on `SnapshotFileDiff`
+ * (1.18.22, `GET /doc`).
+ */
+export interface AgentSessionDiffFile {
+    /** Repository-relative path, or null when the agent did not name one. */
+    file: string | null;
+    /** Unified diff for this file, or null. */
+    patch: string | null;
+    additions: number;
+    deletions: number;
+    /** `added` | `deleted` | `modified`, or null. */
+    status: 'added' | 'deleted' | 'modified' | null;
+}
+/**
+ * One session an interrupt actually reached (Issue #2101).
+ *
+ * Mirrors: src/app/api/worktrees/[id]/interrupt/route.ts InterruptResult.
+ *
+ * `cliToolId` is `string` rather than a union for the same reason
+ * {@link WorktreeItem.cliToolId} is: the CLI bundle keeps its own copy of the
+ * API shapes, and a newer daemon naming a tool this build has never heard of
+ * must print through rather than fail to parse.
+ */
+export interface InterruptedSession {
+    cliToolId: string;
+    /** Primary instances carry `instanceId === cliToolId` (Issue #868). */
+    instanceId: string;
+    /** tmux session name, e.g. `mcbd-opencode-<worktree-id>`. */
+    sessionName: string;
+}
+/**
+ * Mirrors: src/app/api/worktrees/[id]/interrupt/route.ts POST 200 response
+ * (Issue #2101).
+ *
+ * The route answers 404 `{ error: 'No active sessions found' }` instead of a
+ * 200 with an empty list, so `interrupted` is never empty on this shape — see
+ * `src/cli/commands/interrupt.ts` for how that 404 becomes
+ * {@link InterruptExitCode.NO_ACTIVE_SESSIONS} rather than a generic
+ * "resource not found".
+ */
+export interface InterruptResponse {
+    success: boolean;
+    /** e.g. `Interrupt sent to 1 session(s)`. */
+    message: string;
+    interrupted: InterruptedSession[];
+}
 //# sourceMappingURL=api-responses.d.ts.map