polygram 0.8.0-rc.22 → 0.8.0-rc.24

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.22",
+  "version": "0.8.0-rc.24",
   "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

@@ -224,19 +224,21 @@ function createReactionManager({
     // (no point arming over QUEUED/STALL/TIMEOUT itself).
     armStallTimers();
 
-    const elapsed = Date.now() - lastFlushTs;
-    if (elapsed >= throttleMs) {
-      if (pendingTimer) { clearTimeout(pendingTimer); pendingTimer = null; }
-      return flush(stateName);
-    }
-    // Inside throttle window: schedule for the soonest safe flush.
-    if (!pendingTimer) {
-      pendingTimer = setTimeout(() => {
-        pendingTimer = null;
-        flush(currentState);
-      }, throttleMs - elapsed);
-      pendingTimer.unref?.();
-    }
+    // 0.8.0-rc.24: drop the 800ms throttle. Pre-rc.24, when a tool-
+    // using turn fired QUEUED → THINKING → TOOL within a few ms,
+    // the throttle squashed THINKING (pendingTimer flushed
+    // currentState which was already overwritten to TOOL by the
+    // time the timer fired). Users saw 👀 → ❰long pause❱ → 🔥 →
+    // 🥱, missing the 🤔 transition entirely.
+    //
+    // Why the throttle is now redundant: rc.11 added applyChain
+    // which serializes every apply() call to Telegram in
+    // setState() invocation order. So three rapid setStates in
+    // 30ms produce three sequential network calls, each ~200-300ms
+    // round-trip. User sees 👀 → 🤔 → 🔥 progress, smoothly
+    // paced by network latency.
+    if (pendingTimer) { clearTimeout(pendingTimer); pendingTimer = null; }
+    return flush(stateName);
   };
 
   const clear = async () => {

package/package.json

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

@@ -2022,10 +2022,10 @@ async function handleMessage(sessionKey, chatId, msg, bot) {
         chat_id: chatId, text_len: text.length,
         user: cmdUser, user_id: cmdUserId,
       });
-      const preserveBit = text.length > '/compact'.length
-        ? ' with your preservation instructions'
-        : '';
-      await sendReply(`🗜️ Compacting${preserveBit}…`);
+      const hasHint = text.length > '/compact'.length + 1;
+      await sendReply(hasHint
+        ? '🗜️ Compacting with your hint…'
+        : '🗜️ Compacting…');
     } catch (err) {
       console.error(`[${label}] /compact push: ${err.message}`);
       await sendReply(`🗜️ Couldn't trigger compact: ${err.message}`);
@@ -2658,7 +2658,7 @@ async function handleMessage(sessionKey, chatId, msg, bot) {
               `📚 Context window ${pct.toFixed(0)}% full. Three options:`,
               '',
               '• `/new` — start fresh; this conversation ends.',
-              '• `/compact <preserve text>` — summarise older messages, keep what you specify.',
+              '• `/compact` — summarise older messages. Add a hint after the command (e.g. `/compact keep the Q3 commission decisions`) and that becomes the compactor\'s guidance.',
               '• Keep chatting — I\'ll auto-compact when needed; key context is preserved automatically.',
             ].join('\n');
             return tg(bot, 'sendMessage', {