polygram 0.11.0-rc.8 → 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.8",
+  "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

@@ -425,22 +425,36 @@ class ChannelsProcess extends Process {
     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:
     //
-    // 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.
+    //   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.
+    //
+    // 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');
     }

package/package.json

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