commandmate 0.44.0 → 0.44.1

package/dist/lib/detection/status-reason.js

@@ -115,6 +115,23 @@ exports.STATUS_REASON = {
     OPENCODE_RESPONSE_COMPLETE: 'opencode_response_complete',
     INPUT_PROMPT: 'input_prompt',
     NO_RECENT_OUTPUT: 'no_recent_output',
+    /**
+     * Issue #3179: the agent's launch is still in progress.
+     *
+     * Published by `current-output-builder` and `worktree-status-helper` while
+     * `lib/session/session-starting-state` holds a record for the instance — from
+     * `beginAgentSession` until `startSession` returns or throws, bounded by the
+     * tool's readiness wait and released early by a dialog the launch does not
+     * answer. The frame underneath (a shell prompt and the launch line, or a trust
+     * dialog the launch is about to answer) is not read while it is up: the status
+     * is `running`, and `isUnclassifiedActive` / `isSelectionListActive` /
+     * `isPromptWaiting` are all false, so no pad, no answer sheet and no `wait`
+     * exit 10 is raised for a screen nobody has to drive.
+     *
+     * ADDITIVE in the sense {@link STATUS_REASON.EXITED} is: a reader that does not
+     * know the token sees a `running` session.
+     */
+    STARTING: 'starting',
     /**
      * Issue #2070: the tmux session is there, and the TOOL is not.
      *

package/dist/server/locales/en/worktree.json

@@ -410,7 +410,12 @@
             "stats": "Show usage statistics",
             "thinking": "Switch the model variant",
             "web": "Pair another device with this OpenCode",
-            "worktrees": "Manage workspaces"
+            "worktrees": "Manage workspaces",
+            "artifact-capabilities": "Load the reference for what a published artifact can use, such as connectors and file downloads",
+            "artifact-diagramming": "Load guidance for drawing diagrams in artifacts that stay legible in light and dark themes",
+            "claude-in-chrome": "Have Claude carry out a task in your browser through Claude in Chrome",
+            "plugin-authoring": "Load the reference Claude uses to write a mod",
+            "slides": "Make a new Claude Slides presentation from your brief"
         }
     },
     "session": {
@@ -556,6 +561,13 @@
         "dialogCardLabel": "Terminal screen",
         "unreadableHint": "Answer with the number shown on screen (1-9) or y/n. Enter confirms whatever the CLI has highlighted."
     },
+    "sessionStarting": {
+        "title": "Starting {agent}…",
+        "titleWithElapsed": "Starting {agent}… {elapsed}",
+        "hint": "The terminal will appear once the agent is ready.",
+        "showTerminal": "Show terminal",
+        "label": "Agent starting"
+    },
     "chatTranscript": {
         "regionLabel": "Chat transcript",
         "loading": "Loading messages",

package/dist/server/locales/ja/worktree.json

@@ -410,7 +410,12 @@
             "stats": "使用量の統計を表示",
             "thinking": "モデルのバリアントを切り替え",
             "web": "この OpenCode に別のデバイスをペアリング",
-            "worktrees": "ワークスペースを管理"
+            "worktrees": "ワークスペースを管理",
+            "artifact-capabilities": "公開アーティファクトで使える機能（コネクタ・ファイルのダウンロードなど）のリファレンスを読み込み",
+            "artifact-diagramming": "アーティファクトにライト・ダーク両方で読める図を描くためのガイダンスを読み込み",
+            "claude-in-chrome": "Claude in Chrome 経由でブラウザ上の作業を Claude に依頼",
+            "plugin-authoring": "mod を書くときに Claude が使うリファレンスを読み込み",
+            "slides": "指示から Claude Slides のプレゼンテーションを作成"
         }
     },
     "session": {
@@ -556,6 +561,13 @@
         "dialogCardLabel": "ターミナルの画面",
         "unreadableHint": "画面に出ている番号（1〜9）か y／n で答えてください。Enter は選択中の項目をそのまま確定します。"
     },
+    "sessionStarting": {
+        "title": "{agent} を起動中…",
+        "titleWithElapsed": "{agent} を起動中… {elapsed}",
+        "hint": "起動が終わるとターミナルを表示します。",
+        "showTerminal": "ターミナルを見る",
+        "label": "エージェントの起動中"
+    },
     "chatTranscript": {
         "regionLabel": "チャット履歴",
         "loading": "メッセージを読み込み中",

package/dist/server/src/config/session-starting-config.js

@@ -0,0 +1,75 @@
+"use strict";
+/**
+ * How long a session may be shown as "starting" (Issue #3179).
+ *
+ * `lib/session/session-starting-state` records when an agent's launch began and
+ * clears the record when `BaseCLITool.startSession` returns or throws. These
+ * bounds are the escape hatches for the launches that do neither in time:
+ * several tools (antigravity, codex, gemini, copilot, Command Code) only LOG
+ * when their readiness wait runs out and carry on, so a launch that never
+ * became ready would otherwise be shown as starting for as long as the request
+ * lingered. Past the bound the screen falls back to what it showed before
+ * #3179 — the raw pane — so a human notices the stuck start.
+ *
+ * @module config/session-starting-config
+ */
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.SESSION_STARTING_ELAPSED_THRESHOLD_MS = exports.SESSION_STARTING_PROMPT_GRACE_MS = exports.SESSION_STARTING_DEFAULT_WAIT_MS = exports.SESSION_STARTING_GRACE_MS = void 0;
+exports.getSessionStartingMaxMs = getSessionStartingMaxMs;
+exports.getSessionStartingMaxMsAcrossTools = getSessionStartingMaxMsAcrossTools;
+const types_1 = require("../lib/cli-tools/types");
+/**
+ * Slack added on top of a tool's own readiness wait, so the starting display
+ * outlives the wait it describes by a little rather than ending a beat before
+ * the launch reports.
+ */
+exports.SESSION_STARTING_GRACE_MS = 5_000;
+/**
+ * The default readiness wait a launch performs (antigravity / codex / gemini /
+ * copilot / opencode / Command Code are all measured at about 30 s, counting
+ * their initial settle delay and their prompt wait).
+ */
+exports.SESSION_STARTING_DEFAULT_WAIT_MS = 30_000;
+/**
+ * Per-tool readiness waits that differ from the default. Claude waits for its
+ * composer for up to `CLAUDE_INIT_TIMEOUT` (60 s); the literal is restated here
+ * rather than imported so this config module stays free of the session graph.
+ */
+const SESSION_STARTING_WAIT_MS = {
+    claude: 60_000,
+};
+/**
+ * The longest a launch of `cliToolId` is shown as starting, in ms.
+ *
+ * @param cliToolId - The tool being launched
+ * @returns Its readiness wait plus {@link SESSION_STARTING_GRACE_MS}
+ */
+function getSessionStartingMaxMs(cliToolId) {
+    return (SESSION_STARTING_WAIT_MS[cliToolId] ?? exports.SESSION_STARTING_DEFAULT_WAIT_MS)
+        + exports.SESSION_STARTING_GRACE_MS;
+}
+/**
+ * The longest {@link getSessionStartingMaxMs} over every tool, in ms.
+ *
+ * A send to a worktree with no session launches the agent inside the request,
+ * so the client must wait at least this long (Issue #3194).
+ */
+function getSessionStartingMaxMsAcrossTools() {
+    return Math.max(...types_1.CLI_TOOL_IDS.map(getSessionStartingMaxMs));
+}
+/**
+ * How long a dialog may stay on screen during a launch before it is treated as
+ * one the server will NOT answer (a login, an unknown dialog) and the starting
+ * display gives way to the raw pane.
+ *
+ * The dialogs the launch answers itself — the folder-trust screens of
+ * antigravity / codex / copilot / claude — are answered within one poll of the
+ * launch's readiness loop (≤ 1 s) plus the settle wait after the key, so they
+ * never reach this bound.
+ */
+exports.SESSION_STARTING_PROMPT_GRACE_MS = 5_000;
+/**
+ * After how long the client starts printing the elapsed time next to
+ * "<agent> を起動中…".
+ */
+exports.SESSION_STARTING_ELAPSED_THRESHOLD_MS = 5_000;

package/dist/server/src/lib/cli-tools/antigravity.js

@@ -26,6 +26,7 @@ const agent_session_lifecycle_1 = require("../../lib/session/agent-session-lifec
 const logger_1 = require("../../lib/logger");
 const cli_tool_timing_config_1 = require("../../config/cli-tool-timing-config");
 const install_hints_1 = require("./install-hints");
+const launch_screen_1 = require("../../lib/session/launch-screen");
 const logger = (0, logger_1.createLogger)('cli-tools/antigravity');
 /**
  * Extract error message from unknown error type (DRY).
@@ -254,7 +255,7 @@ class AntigravityTool extends base_1.BaseCLITool {
                 worktreePath,
             });
             const launchCommand = model ? `${base} --model ${shellSingleQuote(model)}` : base;
-            await (0, tmux_1.sendKeys)(sessionName, launchCommand, true);
+            await (0, tmux_1.sendKeys)(sessionName, (0, launch_screen_1.withLaunchScreenCleared)(launchCommand), true);
             // Wait for agy to initialize
             await new Promise((resolve) => setTimeout(resolve, ANTIGRAVITY_INIT_WAIT_MS));
             // Poll until the interactive prompt is ready (handles the trust dialog)

package/dist/server/src/lib/cli-tools/base.js

@@ -28,6 +28,7 @@ const logger_1 = require("../logger");
 const terminal_keys_1 = require("../../types/terminal-keys");
 const cli_tool_timing_config_1 = require("../../config/cli-tool-timing-config");
 const tmux_pane_config_1 = require("../../config/tmux-pane-config");
+const session_starting_state_1 = require("../session/session-starting-state");
 const execAsync = (0, util_1.promisify)(child_process_1.exec);
 const logger = (0, logger_1.createLogger)('cli-tools/base');
 /**
@@ -213,8 +214,12 @@ class BaseCLITool {
      * @throws Whatever {@link launchSession} threw — unchanged, after reporting
      */
     async startSession(worktreeId, worktreePath, instanceId, model) {
+        // Issue #3195: this launch's "starting" record is written under this token
+        // (see `session-starting-state`), so the `finally` below clears this
+        // launch's record and never a later launch's of the same instance.
+        const startingToken = (0, session_starting_state_1.issueSessionStartingToken)();
         try {
-            await this.launchSession(worktreeId, worktreePath, instanceId, model);
+            await (0, session_starting_state_1.runWithSessionStartingToken)(startingToken, () => this.launchSession(worktreeId, worktreePath, instanceId, model));
         }
         catch (error) {
             // Issue #2429: a launch that threw is reported as a failed start and as
@@ -229,6 +234,15 @@ class BaseCLITool {
             }, error);
             throw error;
         }
+        finally {
+            // Issue #3179: the launch is over, returned or thrown, so the screen
+            // stops showing it as starting. `beginAgentSession` wrote the record on
+            // the creation path; a reused pane never had one, and this is a no-op for
+            // it. `relaunchIfToolExited` comes through here too. Issue #3195: only
+            // under this launch's token — a launch killed and started again has a
+            // newer record under this key, and it is not this launch's to end.
+            (0, session_starting_state_1.clearSessionStarting)(worktreeId, this.id, instanceId, startingToken);
+        }
         const adopted = this.takeAdoptionMark(worktreeId, instanceId);
         if (adopted !== null)
             await this.warnIfHookUrlIsStale(worktreeId, adopted, instanceId);

package/dist/server/src/lib/cli-tools/codex.js

@@ -20,6 +20,7 @@ const hooks_config_1 = require("../../lib/hooks/sources/codex/hooks-config");
 const agent_session_lifecycle_1 = require("../../lib/session/agent-session-lifecycle");
 const cli_tool_timing_config_1 = require("../../config/cli-tool-timing-config");
 const install_hints_1 = require("./install-hints");
+const launch_screen_1 = require("../../lib/session/launch-screen");
 const logger = (0, logger_1.createLogger)('cli-tools/codex');
 /**
  * Extract error message from unknown error type (DRY)
@@ -268,11 +269,11 @@ class CodexTool extends base_1.BaseCLITool {
             // as the new one's.
             const relaunchIntoSamePane = async () => {
                 (0, agent_session_lifecycle_1.beginAgentSession)({ worktreeId, cliToolId: sources_1.CODEX_CLI_TOOL_ID, instanceId });
-                await (0, tmux_1.sendKeys)(sessionName, launchCommand, true);
+                await (0, tmux_1.sendKeys)(sessionName, (0, launch_screen_1.withLaunchScreenCleared)(launchCommand), true);
                 await new Promise((resolve) => setTimeout(resolve, CODEX_INIT_WAIT_MS));
             };
             // Start Codex CLI in interactive mode
-            await (0, tmux_1.sendKeys)(sessionName, launchCommand, true);
+            await (0, tmux_1.sendKeys)(sessionName, (0, launch_screen_1.withLaunchScreenCleared)(launchCommand), true);
             // Wait for Codex to initialize
             await new Promise((resolve) => setTimeout(resolve, CODEX_INIT_WAIT_MS));
             // Poll until Codex interactive prompt is ready

package/dist/server/src/lib/cli-tools/command-code.js

@@ -53,6 +53,7 @@ const cli_tool_timing_config_1 = require("../../config/cli-tool-timing-config");
 const install_hints_1 = require("./install-hints");
 const plan_review_state_1 = require("../detection/tools/command-code/plan-review-state");
 const session_start_error_1 = require("../../lib/session/session-start-error");
+const launch_screen_1 = require("../../lib/session/launch-screen");
 const logger = (0, logger_1.createLogger)('cli-tools/command-code');
 /** The executable CommandMate launches. See the module docblock for why not `cmd`. */
 exports.COMMAND_CODE_COMMAND = 'commandcode';
@@ -258,11 +259,11 @@ class CommandCodeTool extends base_1.BaseCLITool {
                 });
                 await new Promise((resolve) => setTimeout(resolve, cli_tool_timing_config_1.TUI_SESSION_CREATE_WAIT_MS));
             }
-            await (0, tmux_1.sendKeys)(sessionName, buildCommandCodeLaunchCommand({
+            await (0, tmux_1.sendKeys)(sessionName, (0, launch_screen_1.withLaunchScreenCleared)(buildCommandCodeLaunchCommand({
                 target: { worktreeId, cliToolId: tool_id_1.COMMAND_CODE_CLI_TOOL_ID, instanceId },
                 executablePath: this.command,
                 worktreePath,
-            }), true);
+            })), true);
             await new Promise((resolve) => setTimeout(resolve, cli_tool_timing_config_1.COMMAND_CODE_INIT_WAIT_MS));
             await this.waitForReady(sessionName);
             logger.info('started-command-code-session');

package/dist/server/src/lib/cli-tools/copilot.js

@@ -35,6 +35,7 @@ const tool_id_1 = require("../../lib/hooks/sources/copilot/tool-id");
 const errors_1 = require("../../lib/errors");
 const logger_1 = require("../../lib/logger");
 const install_hints_1 = require("./install-hints");
+const launch_screen_1 = require("../../lib/session/launch-screen");
 const logger = (0, logger_1.createLogger)('cli-tools/copilot');
 /** Interval for polling prompt detection */
 const COPILOT_POLL_INTERVAL_MS = 1000;
@@ -369,7 +370,7 @@ class CopilotTool extends base_1.BaseCLITool {
                 worktreePath,
             });
             // Start Copilot CLI in interactive mode
-            await (0, tmux_1.sendKeys)(sessionName, launchCommand, true);
+            await (0, tmux_1.sendKeys)(sessionName, (0, launch_screen_1.withLaunchScreenCleared)(launchCommand), true);
             // Issue #1907: no blind sleep before this. The 4-second one that used to
             // sit here was a guess at how long copilot takes to paint (measured on
             // 1.0.80: banner at ~1.3 s, folder-trust dialog at ~2.5 s), and it was

package/dist/server/src/lib/cli-tools/gemini.js

@@ -22,6 +22,7 @@ const agent_session_lifecycle_1 = require("../../lib/session/agent-session-lifec
 const logger_1 = require("../../lib/logger");
 const cli_tool_timing_config_1 = require("../../config/cli-tool-timing-config");
 const install_hints_1 = require("./install-hints");
+const launch_screen_1 = require("../../lib/session/launch-screen");
 const logger = (0, logger_1.createLogger)('cli-tools/gemini');
 /**
  * Extract error message from unknown error type (DRY)
@@ -128,7 +129,7 @@ class GeminiTool extends base_1.BaseCLITool {
                 executablePath: this.command,
                 worktreePath,
             });
-            await (0, tmux_1.sendKeys)(sessionName, launchCommand, true);
+            await (0, tmux_1.sendKeys)(sessionName, (0, launch_screen_1.withLaunchScreenCleared)(launchCommand), true);
             // Wait for Gemini to initialize (minimum wait for banner/auth)
             await new Promise((resolve) => setTimeout(resolve, GEMINI_INIT_WAIT_MS));
             // Poll until Gemini interactive prompt is ready

package/dist/server/src/lib/cli-tools/liveness-spec.js

@@ -90,22 +90,40 @@ const ADDED_TOOL_DEFAULTS = {
  */
 const LIVENESS_SPECS = {
     /**
-     * claude's is `isSessionHealthy`, unchanged, expressed as a declaration.
+     * claude's is `isSessionHealthy`, expressed as a declaration.
      *
-     * Three fields carry that history and are claude's alone: `aliveTailLines:
-     * null` (the check has always tested the whole frame), `shellPromptPatterns:
-     * []` (the length gate and the endings are the whole rule), and
+     * Two fields carry that history and are claude's alone: `aliveTailLines:
+     * null` (the check has always tested the whole frame) and
      * `unreadableIsExited: true` (an empty pane and a capture that threw have
-     * both meant "unhealthy" since it was written). Issue #2070's acceptance
-     * condition is that claude's verdicts do not move, so none of the three may be
-     * "improved" here — a change would have to be its own Issue, with its own
-     * measurements.
+     * both meant "unhealthy" since it was written). Neither is "improved" here.
+     *
+     * `shellPromptPatterns` is NOT claude's alone any more (Issue #3191). #2070
+     * left it `[]` so claude's verdicts would not move, which kept claude on the
+     * length-gated endings rule — and that rule cannot see a prompt of 40
+     * characters or more. Measured 2026-10-04: after `/exit` the pane fell back
+     * to `maenokota@MAENOnoMac-Studio uat-repo-wt2 %` (42 characters) and the
+     * session stayed `running`, so the next send sat in `waitForPrompt` until
+     * `Prompt detection timeout (10000ms)`; the author's everyday prompt
+     * (`… MyCodeBranchDesk %`, 46) is past the gate too.
+     *
+     * The positive `user@host …` forms are therefore claude's as well. What made
+     * that safe to adopt unnarrowed: every row of every claude screen fixture in
+     * the repository (`tests/fixtures/claude-*`, `tests/unit/detection/tools/
+     * claude/fixtures/`, the #2070 frames — composer, transcript, dialogs,
+     * pickers, banners) was swept against both patterns and NONE matched, not
+     * just none on the bottom row; `tool-liveness-3191.test.ts` keeps that
+     * sweep. The whole-frame `CLAUDE_PROMPT_PATTERN` check still runs first, so
+     * a pane with claude's composer anywhere on it stays alive regardless. Below
+     * the 40-character gate the verdicts are unchanged — a pattern match there
+     * already ended in `$` / `%` / `#` — only the reason reads `shell prompt
+     * detected` instead of `shell prompt ending detected` for a `user@host:…`
+     * row.
      */
     claude: {
         ...SHARED,
         alivePatterns: [cli_patterns_1.CLAUDE_PROMPT_PATTERN],
         aliveTailLines: null,
-        shellPromptPatterns: [],
+        shellPromptPatterns: tool_liveness_1.SHELL_PROMPT_LINE_PATTERNS,
         unreadableIsExited: true,
         fatalPatterns: cli_patterns_1.CLAUDE_SESSION_ERROR_PATTERNS,
         fatalRegexPatterns: cli_patterns_1.CLAUDE_SESSION_ERROR_REGEX_PATTERNS,

package/dist/server/src/lib/cli-tools/opencode-v2.js

@@ -57,6 +57,7 @@ const graceful_exit_1 = require("./graceful-exit");
 const cli_tool_timing_config_1 = require("../../config/cli-tool-timing-config");
 const install_hints_1 = require("./install-hints");
 const opencode_executable_1 = require("./opencode-executable");
+const launch_screen_1 = require("../../lib/session/launch-screen");
 const logger = (0, logger_1.createLogger)('cli-tools/opencode-v2');
 const execFileAsync = (0, util_1.promisify)(child_process_1.execFile);
 /** Interval between composer polls (launch and send). */
@@ -232,7 +233,7 @@ class OpenCodeV2Tool extends base_1.BaseCLITool {
             if (port === null) {
                 logger.warn('opencode-v2-launch-without-server', { worktreeId, instanceId });
             }
-            await (0, tmux_1.sendKeys)(sessionName, (0, agent_session_lifecycle_1.buildAgentLaunchCommandLine)({ target, executablePath: executable.path, worktreePath }), true);
+            await (0, tmux_1.sendKeys)(sessionName, (0, launch_screen_1.withLaunchScreenCleared)((0, agent_session_lifecycle_1.buildAgentLaunchCommandLine)({ target, executablePath: executable.path, worktreePath })), true);
             await this.waitForReady(sessionName);
             await (0, runtime_1.attachOpencodeV2EventStream)(target);
             logger.info('started-opencode-v2-session');

package/dist/server/src/lib/cli-tools/opencode.js

@@ -75,6 +75,7 @@ const cli_tool_timing_config_1 = require("../../config/cli-tool-timing-config");
 const install_hints_1 = require("./install-hints");
 const opencode_executable_1 = require("./opencode-executable");
 const log_diagnosis_1 = require("../../lib/hooks/sources/opencode/log-diagnosis");
+const launch_screen_1 = require("../../lib/session/launch-screen");
 const logger = (0, logger_1.createLogger)('cli-tools/opencode');
 const execFileAsync = (0, util_1.promisify)(child_process_1.execFile);
 /**
@@ -393,7 +394,7 @@ class OpenCodeTool extends base_1.BaseCLITool {
                 });
             }
             const launchedAt = Date.now();
-            await (0, tmux_1.sendKeys)(sessionName, launchCommand, true);
+            await (0, tmux_1.sendKeys)(sessionName, (0, launch_screen_1.withLaunchScreenCleared)(launchCommand), true);
             // Issue #1908: poll for opencode's own composer instead of sleeping 15 s.
             await this.waitForReady(sessionName);
             // Issue #1763: subscribe once the server is up. Health-checked first, so

package/dist/server/src/lib/cli-tools/vibe-local.js

@@ -21,6 +21,7 @@ const logger_1 = require("../../lib/logger");
 const cli_tool_timing_config_1 = require("../../config/cli-tool-timing-config");
 const install_hints_1 = require("./install-hints");
 const agent_session_lifecycle_1 = require("../../lib/session/agent-session-lifecycle");
+const launch_screen_1 = require("../../lib/session/launch-screen");
 const logger = (0, logger_1.createLogger)('cli-tools/vibe-local');
 /**
  * Extract error message from unknown error type (DRY)
@@ -123,7 +124,7 @@ class VibeLocalTool extends base_1.BaseCLITool {
             }
             // Start vibe-local in interactive mode with auto-approve (-y)
             // -y flag skips the permission confirmation prompt
-            await (0, tmux_1.sendKeys)(sessionName, vibeLocalCommand, true);
+            await (0, tmux_1.sendKeys)(sessionName, (0, launch_screen_1.withLaunchScreenCleared)(vibeLocalCommand), true);
             // Wait for vibe-local to initialize (banner + model loading)
             await new Promise((resolve) => setTimeout(resolve, VIBE_LOCAL_INIT_WAIT_MS));
             logger.info('started-vibe-local-session:sessionname');

package/dist/server/src/lib/detection/status-reason.js

@@ -115,6 +115,23 @@ exports.STATUS_REASON = {
     OPENCODE_RESPONSE_COMPLETE: 'opencode_response_complete',
     INPUT_PROMPT: 'input_prompt',
     NO_RECENT_OUTPUT: 'no_recent_output',
+    /**
+     * Issue #3179: the agent's launch is still in progress.
+     *
+     * Published by `current-output-builder` and `worktree-status-helper` while
+     * `lib/session/session-starting-state` holds a record for the instance — from
+     * `beginAgentSession` until `startSession` returns or throws, bounded by the
+     * tool's readiness wait and released early by a dialog the launch does not
+     * answer. The frame underneath (a shell prompt and the launch line, or a trust
+     * dialog the launch is about to answer) is not read while it is up: the status
+     * is `running`, and `isUnclassifiedActive` / `isSelectionListActive` /
+     * `isPromptWaiting` are all false, so no pad, no answer sheet and no `wait`
+     * exit 10 is raised for a screen nobody has to drive.
+     *
+     * ADDITIVE in the sense {@link STATUS_REASON.EXITED} is: a reader that does not
+     * know the token sees a `running` session.
+     */
+    STARTING: 'starting',
     /**
      * Issue #2070: the tmux session is there, and the TOOL is not.
      *

package/dist/server/src/lib/detection/tool-liveness.js

@@ -49,7 +49,9 @@ exports.SHELL_PROMPT_ENDINGS = ['$', '%', '#'];
  * reproduced on renders as `maenokota@MAENOnoMac-Studio work-codex %` — forty
  * characters exactly, i.e. one past this gate — so a codex session that had
  * genuinely fallen back to the shell read as alive. See
- * {@link SHELL_PROMPT_LINE_PATTERNS}.
+ * {@link SHELL_PROMPT_LINE_PATTERNS}. Issue #3191 found the same gap for claude
+ * (`… uat-repo-wt2 %`, 42 characters, after `/exit`), and claude now takes the
+ * line patterns too.
  */
 exports.MAX_SHELL_PROMPT_LENGTH = 40;
 /**

package/dist/server/src/lib/realtime/terminal-broadcast.js

@@ -75,6 +75,9 @@ function snapshotFingerprint(payload) {
         // client, or the Esc card outlives the panel it dismisses.
         payload.isDismissablePanelActive ?? false,
         payload.isUnclassifiedActive ?? false,
+        // Issue #3179: the launch ending is a change the client has to see even
+        // when the frame and every flag above are unchanged.
+        payload.startingSince ?? null,
     ]);
 }
 async function captureFreshPayload(worktreeId, cliToolId, instanceId) {
@@ -111,6 +114,8 @@ function emitTerminalSnapshot(worktreeId, cliToolId, payload, instanceId) {
         isPagerActive: payload.isPagerActive ?? false,
         isDismissablePanelActive: payload.isDismissablePanelActive ?? false,
         isUnclassifiedActive: payload.isUnclassifiedActive ?? false,
+        // Issue #3179: so the push and the poll agree on "still starting".
+        startingSince: payload.startingSince ?? null,
         version: nextVersion(key),
     });
 }

package/dist/server/src/lib/session/agent-session-lifecycle.js

@@ -43,6 +43,7 @@ exports.buildAgentLaunchCommandLine = buildAgentLaunchCommandLine;
 const sources_1 = require("../../lib/hooks/sources");
 const agent_event_state_1 = require("../../lib/session/agent-event-state");
 const session_generation_archive_1 = require("../../lib/session/session-generation-archive");
+const session_starting_state_1 = require("../../lib/session/session-starting-state");
 const logger_1 = require("../../lib/logger");
 const logger = (0, logger_1.createLogger)('lib/session/agent-session-lifecycle');
 /**
@@ -66,6 +67,16 @@ const logger = (0, logger_1.createLogger)('lib/session/agent-session-lifecycle')
  * @param at - Epoch ms; defaults to now
  */
 function beginAgentSession(target, at = Date.now()) {
+    // Issue #3179: the launch is in progress from here until
+    // `BaseCLITool.startSession` returns or throws (it clears the record in a
+    // `finally`). First, so the screen stops reading the about-to-be-created pane
+    // as a running agent before anything else here can fail.
+    // Issue #3195: the record is written under the token `startSession` is
+    // running the launch with (an `AsyncLocalStorage`, read inside
+    // `markSessionStarting`), which is how that `finally` knows the record is
+    // its own. A second call from the same launch (codex's
+    // `relaunchIntoSamePane`) rewrites the same launch's record.
+    (0, session_starting_state_1.markSessionStarting)(target.worktreeId, target.cliToolId, target.instanceId, at);
     const before = (0, agent_event_state_1.getAgentEventDropCounts)(target.worktreeId, target.cliToolId, target.instanceId).decisionEvicted;
     (0, agent_event_state_1.beginAgentEventGeneration)(target.worktreeId, target.cliToolId, target.instanceId, at);
     const after = (0, agent_event_state_1.getAgentEventDropCounts)(target.worktreeId, target.cliToolId, target.instanceId).decisionEvicted;

package/dist/server/src/lib/session/claude-session.js

@@ -36,6 +36,7 @@ const cmate_cli_tool_parser_1 = require("../../lib/cmate-cli-tool-parser");
 const agent_session_lifecycle_1 = require("../../lib/session/agent-session-lifecycle");
 const agent_event_state_1 = require("../../lib/session/agent-event-state");
 const session_start_error_1 = require("../../lib/session/session-start-error");
+const launch_screen_1 = require("../../lib/session/launch-screen");
 const logger = (0, logger_1.createLogger)('claude-session');
 const execAsync = (0, util_1.promisify)(child_process_1.exec);
 // ----- Helper Functions -----
@@ -429,6 +430,11 @@ function findSessionErrorPattern(cleanOutput) {
  * reading as a zsh prompt. What changed is that six other tools can now be
  * asked the same question; see `lib/cli-tools/liveness-spec`.
  *
+ * Issue #3191: a `user@host …` prompt of 40 characters or more is now read as
+ * the shell too (claude's spec takes `SHELL_PROMPT_LINE_PATTERNS`), so a claude
+ * that was `/exit`ed into a long zsh / bash prompt is reported unhealthy and
+ * relaunched instead of timing out the next send.
+ *
  * @param sessionName - tmux session name
  * @returns HealthCheckResult with healthy status and optional reason
  */
@@ -674,7 +680,7 @@ async function startClaudeSession(options) {
         // and the operator's `~/.claude/settings.json` (measured on 2.1.278).
         const launchCommand = model === undefined ? baseLaunchCommand : `${baseLaunchCommand} --model ${(0, hook_settings_generator_1.shellQuote)(model)}`;
         // Start Claude CLI in interactive mode using dynamically resolved path
-        await (0, tmux_1.sendKeys)(sessionName, launchCommand, true);
+        await (0, tmux_1.sendKeys)(sessionName, (0, launch_screen_1.withLaunchScreenCleared)(launchCommand), true);
         // Wait for Claude to initialize with dynamic detection (OCP-001)
         // Use constants instead of hardcoded values
         const maxWaitTime = exports.CLAUDE_INIT_TIMEOUT;