polygram 0.8.0-rc.34 → 0.8.0-rc.36

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
   "name": "polygram",
-  "version": "0.8.0-rc.34",
+  "version": "0.8.0-rc.36",
   "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 and a history skill.",
   "keywords": [
     "telegram",

package/lib/status-reactions.js

@@ -81,12 +81,17 @@ const DEFAULT_STALL_MS = 45_000;
 const DEFAULT_FREEZE_MS = 180_000;
 // rc.32: thinking-deepening cascade thresholds. Calibrated to Ivan DM
 // 14-day production data (445 turns) — 8% finish <5s, 33% in 5-15s,
-// 25% in 15-30s. 8s catches the meaty band, 20s catches the
-// mid-bracket. STALL still fires at 45s for the genuinely-long 17%.
+// 25% in 15-30s. rc.35 bump: 8s→12s, 20s→30s. User feedback after
+// rc.32 deploy was that the cascade kicked in too eagerly — most
+// 5-15s turns showed 🤨 briefly before resolving, and the resulting
+// emoji churn felt noisy rather than informative. Bumping deeper to
+// 12s lets the entire 5-15s bracket (33%) resolve on plain 🤔, and
+// deepest to 30s lets the 15-30s bracket (25%) resolve on 🤨 without
+// cascading. STALL still fires at 45s for the genuinely-long 17%.
 // CODING / TOOL / WEB / WRITING reset the cascade (any state-change
 // in setState clears the deepening timers).
-const DEFAULT_THINKING_DEEPER_MS = 8_000;
-const DEFAULT_THINKING_DEEPEST_MS = 20_000;
+const DEFAULT_THINKING_DEEPER_MS = 12_000;
+const DEFAULT_THINKING_DEEPEST_MS = 30_000;
 
 // Tool name → state classifier. Case-insensitive substring match so we
 // don't have to enumerate every existing or future tool. Order matters:

package/package.json

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

package/polygram.js

@@ -2537,19 +2537,7 @@ async function handleMessage(sessionKey, chatId, msg, bot) {
       // (queue-head transition) flipped to THINKING the moment we wrote
       // stdin, even though Claude could spend hundreds of ms loading.
       // Result: long flat 🤔 with nothing happening; users assumed stall.
-      //
-      // rc.33: also stop typing here. Telegram's "typing…" indicator
-      // shows for ~5s after the LAST sendChatAction tick. If we stop
-      // typing at turn-end (~5-10s post final reply), the indicator
-      // persists 5s past when the user sees the reply — confusing
-      // ("bot replied AND is still typing?"). Stopping at the first
-      // chunk means typing fades naturally as the streamer emits the
-      // bubble. Reactions (THINKING/CODING/etc) take over as the
-      // "still working" signal for long agent turns.
-      onFirstStream: () => {
-        reactor.setState('THINKING');
-        stopTyping();
-      },
+      onFirstStream: () => reactor.setState('THINKING'),
     });
     const elapsed = ((Date.now() - t0) / 1000).toFixed(1);