polygram 0.17.5 → 0.17.7

package/lib/feedback/session-feedback.js

@@ -69,6 +69,22 @@ function createSessionFeedback({
     });
   }
 
+  // Stop the cycle's TYPING the moment it delivers its answer, decoupled from
+  // endCycle. endCycle fires on the Process 'idle' edge (= session idle), which a
+  // later turn delays — so without this the "typing…" indicator spun minutes past the
+  // delivered answer (field: Ivan DM 2026-06-26). The entry is LEFT in place so
+  // endCycle still clears the anchor 🤔 and tears the entry down. docs/typing-tracks-activity-spec.md
+  function stopCycleTyping(sessionKey) {
+    const entry = active.get(sessionKey);
+    if (!entry || entry.typingStopped) return;
+    entry.typingStopped = true;
+    try { entry.stop(); } catch { /* best-effort */ }
+    logEvent('autonomous-cycle-visuals', {
+      chat_id: entry.anchor?.chatId ?? getChatIdFromKey(sessionKey),
+      session_key: sessionKey, state: 'typing-stopped',
+    });
+  }
+
   function endCycle(sessionKey) {
     const entry = active.get(sessionKey);
     if (!entry) return;
@@ -85,7 +101,7 @@ function createSessionFeedback({
     });
   }
 
-  return { startAutonomousCycle, endCycle };
+  return { startAutonomousCycle, stopCycleTyping, endCycle };
 }
 
 module.exports = { createSessionFeedback };

package/lib/handlers/dispatcher.js

@@ -133,8 +133,24 @@ function createDispatcher({
       throw new Error('auto-resume turn produced no text');
     }
 
-    // 4. Send the continuation reply as regular Telegram messages,
-    //    threaded under the original user message.
+    // 4. Deliver the continuation reply — UNLESS the resumed turn already
+    //    delivered it itself. On the channels/cli backend Claude responds via the
+    //    reply tool DURING the turn, so result.alreadyDelivered is set and the main
+    //    dispatch path short-circuits its own deliver (cli-process.js ~2116). The
+    //    resume path must honor it too, or the reply-tool send + this re-send
+    //    double-post the SAME answer (field: shumabit@umi WhatsApp topic 2026-06-27,
+    //    a bridge-disconnect resume sent "Fixed. ✅…" twice). SDK / genuine no-reply
+    //    turns leave it falsy → deliver as before.
+    if (result.alreadyDelivered) {
+      logEvent('auto-resume-already-delivered', {
+        chat_id: chatId, session_key: sessionKey, msg_id: originalMsg.message_id,
+        text_len: result.text.length,
+      });
+      return result.text;
+    }
+
+    // Send the continuation reply as regular Telegram messages, threaded under
+    // the original user message.
     const chunks = chunkMarkdownText(result.text, chunkBudget);
     await deliverReplies({
       bot,

package/lib/sdk/callbacks.js

@@ -216,6 +216,10 @@ function createSdkCallbacks({
         const text = (msg && typeof msg.text === 'string' && msg.text)
           || extractAssistantText(msg);
         if (!text) return;
+        // 0.13 D3 fix: the cycle delivered its answer → stop its "typing…" NOW. endCycle
+        // (Process idle = SESSION idle) is delayed by any later turn, so typing otherwise
+        // spins minutes past the delivered answer. docs/typing-tracks-activity-spec.md
+        sessionFeedback?.stopCycleTyping?.(sessionKey);
         const chatId = getChatIdFromKey(sessionKey);
         const threadIdRaw = getThreadIdFromKey(sessionKey);
         const threadId = threadIdRaw ? parseInt(threadIdRaw, 10) : null;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "polygram",
-  "version": "0.17.5",
+  "version": "0.17.7",
   "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": {