polygram 0.10.0-rc.3 → 0.10.0-rc.5

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
   "name": "polygram",
-  "version": "0.10.0-rc.3",
+  "version": "0.10.0-rc.5",
   "description": "Telegram integration for Claude Code that preserves the OpenClaw per-chat session model. Migration target for OpenClaw users. Multi-bot, multi-chat, per-topic isolation; SQLite transcripts; inline-keyboard approvals. Bundles /polygram:status|logs|pair-code|approvals admin commands plus history (transcript queries) and polygram-send (out-of-turn IPC sends with file-upload validation) skills.",
   "keywords": [
     "telegram",

package/lib/process/tmux-process.js

@@ -62,23 +62,40 @@ const STREAMING_HINT_RE = /esc to interrupt/;
 //
 //   ⏺ Bash(rm foo.txt)
 //     ⎿  Do you want to do this?
-//          1. Yes
+//        ❯ 1. Yes
 //          2. Yes, allow always for similar commands
 //          3. No, and tell Claude what to do differently
 //
+// The TUI renders a `❯` selection cursor inline before the
+// highlighted option (always option 1 at first paint). Earlier
+// rc.1-rc.4 regex assumed no inline cursor and silently failed to
+// match every approval-gated tool call in production, hanging the
+// session in the TUI until orphan-sweep killed it (see
+// tests/tmux-process-approval.test.js inline-cursor regression).
+//
 // SECURITY (audit H1 fix): require BOTH the question text AND a
 // following numbered menu line ("1. ...") so a malicious assistant
 // message text like "Do you want to proceed?" can't trigger a fake
 // approval card by itself. The menu is part of the TUI's pause
 // state; the assistant can't render it without actually being paused.
-const APPROVAL_PROMPT_RE = /Do you want to (?:proceed|do this|continue)\??[\s\S]{0,400}?(?:^|\n)\s*1\.\s+/im;
+// The optional `❯` cursor in [^\S\n]*(?:❯[^\S\n]+)?1\. is still
+// bounded to the line containing `1.`, so the security property
+// holds — only a real menu line satisfies it.
+const APPROVAL_PROMPT_RE = /Do you want to (?:proceed|do this|continue)\??[\s\S]{0,400}?(?:^|\n)[^\S\n]*(?:❯[^\S\n]+)?1\.\s+/im;
 // Pull the tool name + raw arg snippet from the line preceding the
 // approval prompt. Capture-pane preserves the ⏺ marker.
 const TOOL_INVOCATION_RE = /⏺\s+([A-Za-z_]\w*)\s*\((.*?)\)\s*$/m;
 
 // ─── Defaults — overridable per construction for tests ───────────────
 
-const DEFAULT_READY_TIMEOUT_MS = 30_000;
+// Cold-spawn budget for claude TUI to reach "? for shortcuts" / "accept
+// edits on" state. 30s was enough in dev (interactive shell, warm
+// keychain) but consistently timed out under launchd in production:
+// MCP server starts each have a 30s connection timeout, and the
+// keychain/Aqua context warm-up is slower outside an attached terminal.
+// 120s is generous; the only cost is waiting longer when something is
+// genuinely stuck (we kill + retry in that case anyway).
+const DEFAULT_READY_TIMEOUT_MS = 120_000;
 const DEFAULT_TURN_TIMEOUT_MS  = 5 * 60_000;
 const DEFAULT_POLL_MS          = 250;
 const DEFAULT_QUIESCE_MS       = 500; // require READY for this long before declaring done
@@ -624,22 +641,32 @@ class TmuxProcess extends Process {
 
   async _waitForReady() {
     const deadline = this._now() + this.readyTimeoutMs;
+    let lastBuf = '';
     if (this.pollScheduler) this.pollScheduler.acquire();
     try {
       while (this._now() < deadline) {
         // OPTIMIZATION: ready hint lives in the bottom ~5 lines of the
         // pane. Polling 1000 lines each tick is wasteful — cap at 80
         // for a ~12× cheaper tmux subprocess.
-        const buf = await this.runner.captureWide(this.tmuxName, { lines: 80 });
-        if (READY_HINTS_RE.test(buf)) return;
+        lastBuf = await this.runner.captureWide(this.tmuxName, { lines: 80 });
+        if (READY_HINTS_RE.test(lastBuf)) return;
         await this._waitForNextTick();
       }
     } finally {
       if (this.pollScheduler) this.pollScheduler.release();
     }
+    // On timeout, surface what the TUI was actually showing so the
+    // operator can diagnose whether it was hung, on a setup prompt,
+    // or just slow to render the ready hint. capture the last ~40
+    // lines for the error event payload + log.
+    const tail = lastBuf.split('\n').slice(-40).join('\n');
+    this.logger.warn?.(
+      `[${this.label}] TUI did not signal ready in ${this.readyTimeoutMs}ms; last pane tail:\n${tail}`,
+    );
     throw Object.assign(new Error('TmuxProcess: TUI did not signal ready'), {
       code: 'TMUX_READY_TIMEOUT',
       tmuxName: this.tmuxName,
+      paneTail: tail,
     });
   }
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "polygram",
-  "version": "0.10.0-rc.3",
+  "version": "0.10.0-rc.5",
   "description": "Telegram daemon for Claude Code that preserves the OpenClaw per-chat session model. Migration path for OpenClaw users moving to Claude Code.",
   "main": "lib/ipc/client.js",
   "bin": {