polygram 0.10.0-rc.2 → 0.10.0-rc.4

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.2",
+  "version": "0.10.0-rc.4",
   "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

@@ -78,7 +78,14 @@ 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 +631,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/lib/tmux/tmux-runner.js

@@ -173,13 +173,16 @@ function createTmuxRunner({ logger = console, runFn = run } = {}) {
         stderr: err.stderr,
       });
     }
-    // Set a wide pane to reduce capture-pane wrap artifacts.
-    // Best-effort — if the set-option fails, capture-pane -J fallback
-    // in captureWide() handles the wrap case.
+    // Try to widen the detached pane so claude TUI has room to render
+    // long lines. `resize-window` is the supported way; older
+    // attempts used a non-existent `pane-width` option that always
+    // errored (tmux 3.x: pane-width is a format variable, not a
+    // settable option). capture-pane -J in captureWide() handles
+    // any remaining wrap artifacts.
     try {
-      await runFn('tmux', ['set-option', '-t', name, '-w', 'pane-width', String(paneWidth)]);
+      await runFn('tmux', ['resize-window', '-t', name, '-x', String(paneWidth)]);
     } catch (err) {
-      logger.warn?.(`[tmux-runner] set-option pane-width failed for ${name}: ${err.message}`);
+      logger.debug?.(`[tmux-runner] resize-window failed for ${name}: ${err.message} (capture-pane -J handles wrap)`);
     }
     return name;
   }
@@ -200,10 +203,19 @@ function createTmuxRunner({ logger = console, runFn = run } = {}) {
    *   2. \n → MULTILINE_SEPARATOR  (F-spike-3)
    *   3. set-buffer + paste-buffer  (atomic; bracketed-paste-aware
    *      in modern claude TUI versions)
+   *   4. brief drain delay so a subsequent send-keys (e.g. Enter) is
+   *      processed as a key event by the TUI, NOT consumed as part of
+   *      the paste's bracketed-paste content.
    *
-   * NO Enter is sent. Caller follows up with `sendControl(name, 'Enter')`
-   * when they want to submit. (Splitting paste + Enter lets callers
-   * verify the text landed via capture-pane before submitting.)
+   * INCIDENT (0.10.0-rc.2): without the drain delay, send-keys Enter
+   * fired immediately after paste-buffer was being swallowed by
+   * claude TUI's bracketed-paste handler — the paste sat in the input
+   * area unsubmitted. Manual `tmux send-keys ... Enter` unstuck it.
+   * 80ms is enough on macOS tmux 3.6a for the close-bracket ESC[201~
+   * to land before any subsequent key arrives.
+   *
+   * NO Enter is sent here. Caller follows up with
+   * `sendControl(name, 'Enter')` when they want to submit.
    */
   async function pasteText(name, text) {
     const sanitized = sanitize(text);
@@ -218,6 +230,8 @@ function createTmuxRunner({ logger = console, runFn = run } = {}) {
       await runFn('tmux', ['delete-buffer', '-b', bufName]).catch(() => {});
       throw err;
     }
+    // Drain delay — see incident note above.
+    await new Promise((r) => setTimeout(r, 80));
     return { sanitized, oneLine, stripped: text.length - sanitized.length };
   }
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "polygram",
-  "version": "0.10.0-rc.2",
+  "version": "0.10.0-rc.4",
   "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": {