polygram 0.11.0-rc.7 → 0.11.0-rc.9

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
   "name": "polygram",
-  "version": "0.11.0-rc.7",
+  "version": "0.11.0-rc.9",
   "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/channels-process.js

@@ -365,53 +365,96 @@ class ChannelsProcess extends Process {
       '--dangerously-load-development-channels', 'server:polygram-bridge',
     ];
 
-    // Parity audit P8: branch on existingSessionId. `--session-id <id>`
-    // creates a NEW claude session with that id; `--resume <id>` resumes the
-    // EXISTING conversation. Lazy-respawn after bridge-disconnect must use
-    // --resume so conversation history is preserved. Mirrors
-    // tmux-process.js:514-518.
+    // Resolve config FIRST so the --resume file-check below has the correct
+    // cwd (it picks up topic precedence). Other flags get pushed in order
+    // after this.
+    const topicConfig = opts.threadId && opts.chatConfig?.topics?.[opts.threadId];
+    const agent  = topicConfig?.agent  || opts.chatConfig?.agent  || opts.agent;
+    const model  = topicConfig?.model  || opts.chatConfig?.model  || opts.model;
+    const effort = topicConfig?.effort || opts.chatConfig?.effort || opts.effort;
+    const resolvedCwd = topicConfig?.cwd || opts.chatConfig?.cwd || opts.cwd;
+
+    // Parity audit P8 + rc.8 fs-guard (2026-05-26 shumorobot Music topic):
+    // `--session-id <id>` creates a NEW claude session with that id;
+    // `--resume <id>` resumes the EXISTING conversation. Lazy-respawn after
+    // bridge-disconnect must use --resume so conversation history is
+    // preserved. Mirrors tmux-process.js:514-518.
     //
-    // rc.6 note: pre-channels session ids (created by sdk/tmux backends and
-    // persisted in polygram's DB) are NOT cross-backend compatible — claude
-    // indexes session files under a cwd-derived projects dir that may not
-    // match what channels-mode passes, leading to silent "No conversation
-    // found" exit. The fix lives at the data layer, not here: operator
-    // clears pre-channels session ids from polygram's sessions table before
-    // flipping a chat to channels (see ops/migrate-to-channels.sql).
-    if (opts.existingSessionId) {
+    // rc.8 ghost-session guard: polygram persists claude_session_id to its
+    // DB as soon as the bridge handshakes (onInit), but claude only writes
+    // the JSONL after a successful turn. If an early channels attempt fails
+    // before claude completes any turn, polygram's DB ends up with a
+    // claude_session_id that has NO corresponding file under claude's
+    // projects dir. Subsequent `--resume <ghost-id>` makes claude exit
+    // clean with "No conversation found" — exactly the Music topic stall
+    // observed at 04:04:29 (session_id=567c72db never persisted; rc.4
+    // pane snapshot proved it).
+    //
+    // Fix: before passing --resume, verify the session JSONL actually
+    // exists under the launch cwd. If not, drop the ghost id and use
+    // --session-id with the freshly-generated uuid — claude creates a
+    // fresh session and onInit re-upserts the DB row.
+    //
+    // Resume cases preserved:
+    //   - in-daemon lazy respawn (file written after first successful turn)
+    //   - daemon restart on a chat that completed at least one turn
+    // Resume cases correctly dropped:
+    //   - cross-backend stale ids (different cwd → different projects dir)
+    //   - ghost ids from failed-before-first-turn attempts
+    let canResume = false;
+    let resumePath = null;
+    if (opts.existingSessionId && resolvedCwd) {
+      // claude's projects dir naming: cwd with '/' → '-'.
+      // Verified live at ~/.claude/projects/-Users-ivanshumkov-Music-rekordbox/
+      const cwdMangled = resolvedCwd.replace(/\//g, '-');
+      resumePath = path.join(os.homedir(), '.claude', 'projects', cwdMangled, `${opts.existingSessionId}.jsonl`);
+      try { canResume = fs.statSync(resumePath).isFile(); } catch { canResume = false; }
+    }
+    if (canResume) {
       claudeArgs.push('--resume', opts.existingSessionId);
     } else {
       claudeArgs.push('--session-id', this.claudeSessionId);
+      if (opts.existingSessionId) {
+        this.logger.warn?.(
+          `[${this.label}] channels: dropping DB session ${opts.existingSessionId} — ` +
+          `no local file at ${resumePath || '<unknown cwd>'}. Starting fresh with ${this.claudeSessionId}.`,
+        );
+      }
     }
-
-    // Parity audit P4: per-chat / per-topic agent flag. Without this, chats
-    // configured with agent='music-curation' / 'shumabit' silently fall back
-    // to claude's default. Mirrors tmux-process.js:527.
-    // Topic precedence over chat — same as tmux pattern (parity audit P7).
-    const topicConfig = opts.threadId && opts.chatConfig?.topics?.[opts.threadId];
-    const agent  = topicConfig?.agent  || opts.chatConfig?.agent  || opts.agent;
-    const model  = topicConfig?.model  || opts.chatConfig?.model  || opts.model;
-    const effort = topicConfig?.effort || opts.chatConfig?.effort || opts.effort;
     if (agent)  claudeArgs.push('--agent', agent);
     if (model)  claudeArgs.unshift('--model', model);
     if (effort) claudeArgs.push('--effort', effort);
 
-    // Mirror TmuxProcess pattern (lib/process/tmux-process.js:522-525):
-    // honor opts.permissionMode === 'bypassPermissions' by passing
-    // --dangerously-skip-permissions. In that mode Claude auto-approves all
-    // tool uses, so permission_request notifications stop firing (the bridge
-    // relay becomes inactive — that's the chat owner's choice).
-    // Default (no bypass): permission_request flows through the relay → TG
-    // approve/deny buttons via polygram's onApprovalRequired handler.
+    // rc.9 (2026-05-26 shumorobot first-turn-dead-zone diagnosis): channels
+    // backend defaults to permissionMode='bypassPermissions'. Without it,
+    // claude TUI shows the canonical interactive permission prompt for
+    // every `mcp__polygram-bridge__reply` call:
+    //
+    //   polygram-bridge - reply(...) (MCP)
+    //   Do you want to proceed?
+    //   ❯ 1. Yes  2. Yes, and don't ask again  3. No
+    //
+    // Channels mode has no interactive surface — there's no human at the
+    // tmux pane to press a number — so every first-turn hangs until the
+    // 30-min turn timeout fires. Reproduced + fixed live via
+    // `scripts/spikes/channels-first-turn.mjs`: without bypassPermissions
+    // the spike times out at 60s with claude "Marinating" forever; with
+    // bypassPermissions it replies in ~5s.
+    //
+    // The bridge DOES relay `notifications/claude/channel/permission_request`
+    // (channels-bridge.mjs:258) for the EXPERIMENTAL channel-permission
+    // API, but claude TUI doesn't route ordinary MCP tool calls through
+    // that channel — it shows the regular TUI prompt. So the relay path
+    // isn't reachable from a fresh-spawn channels turn.
     //
-    // Trust + dev-channel confirmation dialogs are SEPARATE concerns and
-    // still need _handleStartupDialogs polling either way — skip-permissions
-    // only affects per-tool prompts, not workspace-trust or dev-channels
-    // confirmations.
+    // Config can still override (e.g., chats that genuinely want a
+    // different mode set `permissionMode` in chat/topic config); the
+    // default ensures bots actually reply out of the box.
     const permissionMode = topicConfig?.permissionMode
       || opts.chatConfig?.permissionMode
-      || opts.permissionMode;
-    if (permissionMode) claudeArgs.push('--permission-mode', permissionMode);
+      || opts.permissionMode
+      || 'bypassPermissions';
+    claudeArgs.push('--permission-mode', permissionMode);
     if (permissionMode === 'bypassPermissions') {
       claudeArgs.push('--dangerously-skip-permissions');
     }
@@ -466,8 +509,8 @@ class ChannelsProcess extends Process {
     // --mcp-config MUST be last (variadic flag)
     claudeArgs.push('--mcp-config', this.mcpConfigPath);   // P0 #1: file path, not inline JSON
 
-    const cwd = topicConfig?.cwd || opts.chatConfig?.cwd || opts.cwd;
-    if (cwd) claudeArgs.unshift('--add-dir', cwd);
+    // resolvedCwd was computed above (line ~375) for the --resume file-check.
+    if (resolvedCwd) claudeArgs.unshift('--add-dir', resolvedCwd);
 
     // rc.5 (2026-05-25 shumorobot diagnosis): the launch cwd MUST be the
     // resolved topic/chat cwd, not just opts.cwd. claude's TUI indexes
@@ -486,7 +529,7 @@ class ChannelsProcess extends Process {
     // Real tmuxRunner.spawn signature: {name, cwd, command, args, envExtras, paneWidth}
     await this.runner.spawn({
       name: tmuxName,
-      cwd: cwd || opts.cwd || process.cwd(),
+      cwd: resolvedCwd || opts.cwd || process.cwd(),
       command: this.claudeBin,
       args: claudeArgs,
     });

package/package.json

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