aiterm-mcp 0.24.0 → 0.24.2

package/README.ja.md

@@ -96,6 +96,10 @@ host統合は、kitepon.devの製品開発を支える内部基盤
 
 14 ツール: 6 つの **PTY ツール**（`pty_open` / `pty_send` / `pty_read` / `pty_key` / `pty_close` / `pty_list`）で 1 本の永続端末を開き・操作し・読む。加えて 4 つの **エージェント起動ツール**（`claude_agent` / `codex_agent` / `grok_agent` / `composer_agent`）が別のコーディングエージェントの TUI を新しい端末の中に起動し、`agent_configure`が起動中のCodex／Claudeのmodel・effortを再起動なしで変更し、`claude_turn`がdurable caller向けの構造化issue／recoveryを、`claude_approval`が相関済みClaude承認UI中継を、`diagnostics`が安全なfactory readinessを返す。バックエンドは **tmux** なので、MCP サーバや AI クライアントが再起動してもセッションは生き残る。
 
+**v0.24.2では長寿命Codexでも設定変更を維持。** 起動時headerがcapture範囲外へ流れた後は、
+常駐するmodel／effort footerと入力欄でCodexを識別する。idle sessionをそのまま変更でき、
+caller側の画面再描画、再試行、agent再起動は不要。
+
 **v0.24.0では起動中agentの設定変更を追加。** `agent_configure`はvendor標準操作を使って、
 起動中のCodex／Claudeのmodelとreasoning effortを変更する。PTY、vendor session、会話contextは維持する。
 
@@ -377,7 +381,7 @@ aiterm は同じ核心の洞察——端末を出会いの場にする——を
 
 `aiterm-runtime-errors snapshot` は dotagents factory adapter 向けに、製品所有のローカル snapshot を機械可読 JSON で返す。canonical dotagents factory-reporter config が schema-exact、host profile が実行 OS と一致し、`collection.enabled` が JSON boolean `true` の時だけ収集する。reporting field は schema 検証するが endpoint/credential file へ接続・読取せず network I/O も行わない。観測 API は core owner layer の固定3 code（PTY dependency・persistence・任意 vendor launcher）だけを受け、保存するのも固定 template と aggregate metadata（SHA-256 fingerprint、count、first/last、status、monotonic sequence）だけ。exception、stderr/stdout、stack、prompt、PTY/transcript/event body、path、任意 context は受け付けない。保存済み JSON も top/record exact・固定定義一致・fingerprint 再計算を通し、明示 DTO だけを返す。
 
-consumer は `aiterm-runtime-errors snapshot` を読み、durable ingestion 後に `aiterm-runtime-errors ack --cursor N` を呼ぶ。運用上の明示操作は `resolve|reopen --fingerprint SHA256`。MCP からの収集・diagnostic read は timeout 付き child process に隔離し、FIFOや停止 filesystem が端末本体を止めない。store mutation は期限付き bakery ticket queue で直列化する。各waiterは PID＋process start identity＋owner token を持つ再利用されない固有ticketを所有するため、死んだownerだけを固有名で除去でき、固定path回収のABAを作らない。POSIX state は `$XDG_STATE_HOME/aiterm-mcp/`（既定 `~/.local/state/aiterm-mcp/`）へ atomic replacement で置き、every read で owner/mode を再検証する。Windows native は `%LOCALAPPDATA%\aiterm-mcp\` で current SID の非継承 FullControl ACE 1件だけへ DACL を再構築し readback する。今回 Windows は path/DACL/timeout の純粋テストだけであり、新しい実機統合成功は主張しない。
+consumer は `aiterm-runtime-errors snapshot` を読み、durable ingestion 後に `aiterm-runtime-errors ack --cursor N` を呼ぶ。運用上の明示操作は `resolve|reopen --fingerprint SHA256`。MCP からの収集・diagnostic read は timeout 付き child process に隔離し、FIFOや停止 filesystem が端末本体を止めない。store mutation は期限付き bakery ticket queue で直列化する。各waiterは PID＋process start identity＋owner token を持つ再利用されない固有ticketを所有するため、死んだownerだけを固有名で除去でき、固定path回収のABAを作らない。queueの期限は正常な前任者を含む総待ち時間ではなく、同じ先頭ownerが進まない時間を測る。通常pollはprocessの生存確認だけを行い、process start identityはblockerがstallした時に照合する。POSIX state は `$XDG_STATE_HOME/aiterm-mcp/`（既定 `~/.local/state/aiterm-mcp/`）へ atomic replacement で置き、every read で owner/mode を再検証する。Windows native は `%LOCALAPPDATA%\aiterm-mcp\` で current SID の非継承 FullControl ACE 1件だけへ DACL を再構築し readback する。今回 Windows は path/DACL/timeout の純粋テストだけであり、新しい実機統合成功は主張しない。
 
 ### 対話エージェント起動ツール
 

package/README.md

@@ -96,6 +96,11 @@ toolchain behind kitepon.dev's products.
 
 Fourteen tools: six **PTY tools** — `pty_open` / `pty_send` / `pty_read` / `pty_key` / `pty_close` / `pty_list` — to open, drive, and read one persistent terminal, four **agent launchers** — `claude_agent` / `codex_agent` / `grok_agent` / `composer_agent` — that each start another coding agent's TUI inside a fresh one, `agent_configure` to change a running Codex/Claude session's model and effort without restarting it, `claude_turn` for durable structured issue/recovery, `claude_approval` for correlated Claude approval prompts, and `diagnostics` for safe factory readiness. The backend is **tmux**, so sessions survive even if the MCP server or the AI client restarts.
 
+**v0.24.2 keeps in-place configuration working in long-lived Codex sessions.** Once the
+startup header has scrolled out of the captured pane, aiterm recognizes Codex by its persistent
+model/effort footer together with the input prompt. An idle session is therefore configured
+directly; callers do not need to redraw the TUI, retry, or restart the agent.
+
 **v0.24.0 adds in-place agent configuration.** `agent_configure` uses each vendor's
 native controls to change the model and/or reasoning effort of a running Codex or Claude
 session while preserving its PTY, vendor session, and conversation context.
@@ -402,7 +407,7 @@ On top of that sits a productized layer a raw tmux bridge doesn't have: **token-
 
 `aiterm-runtime-errors snapshot` exposes a machine-readable, product-owned local snapshot for the dotagents factory adapter. Collection is fail-closed unless the canonical dotagents factory-reporter config is schema-exact, its host profile matches the executing OS, and it contains the JSON boolean `collection.enabled: true`; reporting fields are schema-validated but endpoints and credential files are never contacted, and the store performs no network I/O. The only accepted observations are three fixed codes owned by the core boundary (PTY dependency, persistence, and optional vendor launcher). Stored data is limited to fixed templates and aggregate metadata (SHA-256 fingerprint, count, first/last seen, status, and monotonic sequence); exceptions, stderr/stdout, stacks, prompts, terminal/transcript/event bodies, paths, and arbitrary context cannot enter the API. Persisted JSON is revalidated with exact top/record fields and a recomputed fingerprint before explicit DTO projection.
 
-Consumer flow is `aiterm-runtime-errors snapshot`, then `aiterm-runtime-errors ack --cursor N` after durable ingestion. Operators can use `resolve|reopen --fingerprint SHA256`. MCP collection and diagnostic reads run in timeout-bounded child processes, so a FIFO or stalled filesystem cannot block terminal work; child failure emits only the fixed store diagnostic. Store mutation uses a bounded bakery ticket queue: every waiter owns a never-reused ticket containing PID, process-start identity, and an owner token, so dead owners are removed by unique filename without fixed-path reclaim ABA. Worker deadlines use forced termination so a SIGTERM-ignoring child cannot mutate state after timeout. POSIX state is atomically replaced under `$XDG_STATE_HOME/aiterm-mcp/` (default `~/.local/state/aiterm-mcp/`) with owner/mode rechecked on every read. Windows native uses `%LOCALAPPDATA%\aiterm-mcp\`; each DACL is rebuilt and read back as one non-inherited FullControl ACE for the current SID. Windows path/DACL/timeout behavior is covered by pure tests in this change; no new Windows integration success is claimed.
+Consumer flow is `aiterm-runtime-errors snapshot`, then `aiterm-runtime-errors ack --cursor N` after durable ingestion. Operators can use `resolve|reopen --fingerprint SHA256`. MCP collection and diagnostic reads run in timeout-bounded child processes, so a FIFO or stalled filesystem cannot block terminal work; child failure emits only the fixed store diagnostic. Store mutation uses a bounded bakery ticket queue: every waiter owns a never-reused ticket containing PID, process-start identity, and an owner token, so dead owners are removed by unique filename without fixed-path reclaim ABA. The queue deadline measures lack of progress by the same head owner, not total wait behind healthy predecessors; normal polling uses the native process-liveness check and validates process-start identity only when a blocker stalls. Worker deadlines use forced termination so a SIGTERM-ignoring child cannot mutate state after timeout. POSIX state is atomically replaced under `$XDG_STATE_HOME/aiterm-mcp/` (default `~/.local/state/aiterm-mcp/`) with owner/mode rechecked on every read. Windows native uses `%LOCALAPPDATA%\aiterm-mcp\`; each DACL is rebuilt and read back as one non-inherited FullControl ACE for the current SID. Windows path/DACL/timeout behavior is covered by pure tests in this change; no new Windows integration success is claimed.
 
 ### Interactive agent launchers
 

package/dist/core.js

@@ -3323,7 +3323,11 @@ function isAgentTuiReady(kind, screen) {
         return screen.includes("Claude Code") && /(^|\n)\s*❯/.test(screen);
     }
     if (kind === "codex") {
-        return screen.includes("OpenAI Codex") && /(^|\n)\s*[›>]/.test(screen);
+        // 起動直後は製品header、長寿命sessionでは常駐footerがCodex TUIの識別子になる。
+        // capture-paneは直近45行だけなので、会話が進むとheaderは正常に画面外へ流れる。
+        const codexFrontend = screen.includes("OpenAI Codex")
+            || /(^|\n)\s*\S+\s+(?:low|medium|high|xhigh|max|ultra)\s+·\s+\S.*$/m.test(screen);
+        return codexFrontend && /(^|\n)\s*[›>]/.test(screen);
     }
     // Grok Build 0.2.117 は起動完了後に製品名を消し、model footerだけを残す。
     // Composerも同じfrontendでmodel名だけが異なるため、両方をvendor UIの根拠にする。

package/dist/runtime-error-store.js

@@ -532,10 +532,15 @@ export class RuntimeErrorStore {
             ticket = path.join(queue, ticketName);
             this.publishOwnerFile(ticket, owner);
             fs.unlinkSync(choosing);
-            const deadline = Date.now() + 1_500;
+            // 期限はqueue全体の総待ち時間ではなく、同じ先頭ownerが進まない時間を測る。
+            // 正常な前任者がticketを順に解放するたびに予算を更新し、長いqueueをbusyと誤認しない。
+            let deadline = Date.now() + 1_500;
+            let blockingTicket = null;
+            let choosingBlockers = new Set();
             for (;;) {
                 const names = fs.readdirSync(queue).sort();
                 let hasLiveChoosing = false;
+                const liveChoosing = new Set();
                 for (const name of names.filter((candidate) => choosingPattern.test(candidate))) {
                     const currentPath = path.join(queue, name);
                     let current;
@@ -549,10 +554,17 @@ export class RuntimeErrorStore {
                     }
                     if (name !== `choosing-${current.token}.json`)
                         throw new Error("runtime error choosing entry が不正です");
-                    const identity = processStartIdentity(current.pid, this.platform, identityTimeoutMs);
-                    const live = identity === current.start_id || (!identity && processExists(current.pid));
-                    if (live)
+                    // 通常待機ではkill(0)だけを使う。macOSのprocess start identityは外部psを起動するため、
+                    // 全waiterが全pollで呼ぶとqueue自身が進めなくなる。PID再利用の照合はstall時だけ行う。
+                    let live = processExists(current.pid);
+                    if (live && Date.now() >= deadline) {
+                        const identity = processStartIdentity(current.pid, this.platform, identityTimeoutMs);
+                        live = identity === current.start_id || (!identity && processExists(current.pid));
+                    }
+                    if (live) {
                         hasLiveChoosing = true;
+                        liveChoosing.add(name);
+                    }
                     else {
                         try {
                             fs.unlinkSync(currentPath);
@@ -564,11 +576,17 @@ export class RuntimeErrorStore {
                     }
                 }
                 if (hasLiveChoosing) {
+                    if (choosingBlockers.size === 0
+                        || [...choosingBlockers].some((name) => !liveChoosing.has(name))) {
+                        deadline = Date.now() + 1_500;
+                    }
+                    choosingBlockers = liveChoosing;
                     if (Date.now() >= deadline)
                         throw new Error("runtime error store is busy");
                     Atomics.wait(new Int32Array(new SharedArrayBuffer(4)), 0, 0, 10);
                     continue;
                 }
+                choosingBlockers = new Set();
                 let firstLive = null;
                 const ticketNames = fs.readdirSync(queue).sort();
                 for (const name of ticketNames.filter((candidate) => ticketPattern.test(candidate))) {
@@ -584,8 +602,11 @@ export class RuntimeErrorStore {
                     }
                     if (!name.endsWith(`-${current.token}.ticket`))
                         throw new Error("runtime error lock ticket が不正です");
-                    const identity = processStartIdentity(current.pid, this.platform, identityTimeoutMs);
-                    const live = identity === current.start_id || (!identity && processExists(current.pid));
+                    let live = processExists(current.pid);
+                    if (live && name === blockingTicket && Date.now() >= deadline) {
+                        const identity = processStartIdentity(current.pid, this.platform, identityTimeoutMs);
+                        live = identity === current.start_id || (!identity && processExists(current.pid));
+                    }
                     if (!live) {
                         try {
                             fs.unlinkSync(currentPath);
@@ -601,6 +622,10 @@ export class RuntimeErrorStore {
                 }
                 if (firstLive === ticketName)
                     break;
+                if (firstLive !== blockingTicket) {
+                    blockingTicket = firstLive;
+                    deadline = Date.now() + 1_500;
+                }
                 if (Date.now() >= deadline)
                     throw new Error("runtime error store is busy");
                 Atomics.wait(new Int32Array(new SharedArrayBuffer(4)), 0, 0, 10);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "aiterm-mcp",
-  "version": "0.24.0",
+  "version": "0.24.2",
   "mcpName": "io.github.kitepon-rgb/aiterm-mcp",
   "description": "Persistent tmux terminal MCP that lets Claude Code drive Codex CLI's interactive TUI, including slash commands and $imagegen. Also runs durable PTY sessions for SSH, containers, REPLs, and coding agents.",
   "keywords": [