polygram 0.8.0-rc.34 → 0.8.0-rc.35

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.35",
   "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/package.json

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