polygram 0.12.0-rc.28 → 0.12.0-rc.29

package/lib/process/cli-process.js

@@ -690,6 +690,22 @@ class CliProcess extends Process {
       'as normal — only the FINAL user-visible message needs to go through',
       'the reply tool.',
       '',
+      // TEMPORARY mitigation (2026-06-08 Shumabit@UMI wedge): AskUserQuestion opens
+      // a blocking TUI selection widget the channel can't answer → the session
+      // parks until manually Esc'd. REMOVE this whole rule when the rich
+      // question→Telegram-keyboard feature ships (see docs design); claude should
+      // then use the native question tool again. Tracked so it isn't forgotten.
+      '### Asking the user a question / offering choices — HARD RULE',
+      '',
+      'NEVER use the AskUserQuestion tool or any interactive menu / selection',
+      'widget. They open a blocking terminal prompt the user on Telegram CANNOT',
+      'see or navigate — it silently wedges the entire session until it is manually',
+      'cleared. (Rich tap-to-answer choices are coming; until then this is a hard rule.)',
+      '',
+      'To ask a multiple-choice question, write the options as a numbered list',
+      'inside your `mcp__polygram-bridge__reply` text and ask the user to reply with',
+      'the number (or free text). Do the same for yes/no and any selection.',
+      '',
       '### Sending FILES (tracks, images, docs) to the user',
       '',
       'The `mcp__polygram-bridge__reply` tool takes an optional `files` array of',

package/package.json

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