polygram 0.10.0-rc.4 → 0.10.0-rc.6

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

@@ -40,6 +40,7 @@ const { LogTail } = require('../tmux/log-tail');
 const { sessionLogPath, pipeToParser } = require('../tmux/session-log-parser');
 const { computeCostUsd } = require('../model-costs');
 const { getTopicConfig } = require('../session-key');
+const { POLYGRAM_DISPLAY_HINT } = require('../telegram/display-hint');
 
 // Context window per model. All Claude 4.x models are 200k. If
 // Anthropic ships a model with a different window, promote this to
@@ -62,16 +63,26 @@ 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;
@@ -223,6 +234,15 @@ class TmuxProcess extends Process {
       }
       args.push('--debug-file', this.debugLogPath);
       if (agent) args.push('--agent', agent);
+      // Cross-backend parity: SDK appends polygram's Telegram display
+      // hint to every agent's systemPrompt (lib/sdk/build-options.js).
+      // Without this, the spawned claude session has no idea it's
+      // replying through a Telegram bot — shumorobot 2026-05-15 caught
+      // the model emitting shell-style canned strings ("No response
+      // requested.") as actual Telegram replies for that reason.
+      // `--append-system-prompt` is preserved by claude CLI in
+      // addition to (not in place of) the agent's own prompt.
+      args.push('--append-system-prompt', POLYGRAM_DISPLAY_HINT);
 
       // R2-F8: spawn errors must fail loud, not silent-catch.
       await this.runner.spawn({

package/package.json

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