polygram 0.12.3 → 0.12.4

package/lib/process/cli-process.js

@@ -763,19 +763,28 @@ class CliProcess extends Process {
       'DROPPED — it gets re-sent to you or flagged as a lost message. When unsure,',
       'include the id.',
       '',
-      '### Staying responsive on a long task',
+      '### Staying responsive on a long task — show progress, never go silent',
       '',
-      'The user cannot see you working — no live typing reaches them. For any task',
-      'that takes more than a few seconds, send a SHORT status first via `reply`',
-      '(it returns a `message_id`), then call `mcp__polygram-bridge__edit_message`',
-      'with that `message_id` to update the SAME bubble as you make progress,',
-      'finishing with the result. One evolving message beats silence or a flood of',
-      'new ones.',
+      'The user sees NOTHING while you work — no inline text, no tool output reaches',
+      'them. A turn that runs long with no reply looks BROKEN (they see only silence)',
+      'and can hit the turn time-cap before you answer.',
       '',
-      'Write status in PLAIN, friendly language about what you are doing FOR THE',
-      'USER — never tool names or mechanics. Say "Checking your config now…", not',
-      '"Running Bash" or "Calling Read". If the final answer is long, send it as a',
-      'fresh `reply` rather than an edit (an edit is one single message bubble).',
+      'So once you are clearly into multi-step work — you have run a couple of tool',
+      'calls without replying, or the request plainly needs research / several steps —',
+      'send a SHORT one-line status via `reply` (it returns a `message_id`), then use',
+      '`mcp__polygram-bridge__edit_message` on that SAME `message_id` to update the',
+      'bubble as you progress. `edit_message` is for INTERIM status ONLY.',
+      '',
+      'Deliver the FINAL answer as a fresh `reply`, never as an edit: a fresh reply',
+      'notifies the user and carries `consumed_turn_ids`; an edit does neither. If you',
+      'no longer have the status bubble\'s message_id, just send a fresh `reply` —',
+      'never guess an id.',
+      '',
+      'If you will finish in one or two tool calls, just answer — no status bubble.',
+      'Status is for work that takes time, not for quick answers (do not spam it).',
+      '',
+      'Write status in PLAIN language about what you are doing FOR THE USER — never',
+      'tool names. Say "Checking your config now…", not "Running Bash".',
       '',
       // TEMPORARY mitigation (2026-06-08 Shumabit@UMI wedge): AskUserQuestion opens
       // a blocking TUI selection widget the channel can't answer → the session

package/package.json

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