polygram 0.8.0-rc.42 → 0.8.0-rc.44

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.42",
+  "version": "0.8.0-rc.44",
   "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/pm-interface.js

@@ -67,7 +67,11 @@
  *
  *   Optional (only one of the two pms implements these — feature-detect):
  * @property {((sessionKey: string, text: string, opts?: object) => boolean)=} steer
- *   — SDK pm only (rc.9 PostToolBatch hook drains buffer).
+ *   — SDK pm only (rc.9 priority='now' direct push, opt-in shouldQuery).
+ * @property {((sessionKey: string, opts: {content: string, priority?: 'now'|'next'|'later', shouldQuery?: boolean, parent_tool_use_id?: string|null}) => boolean)=} injectUserMessage
+ *   — SDK pm only (rc.42 native autosteer / queue via SDKUserMessage
+ *     priority hint). Returns false on CLI pm (no inputController
+ *     surface) or when sessionKey not found.
  * @property {((sessionKey: string, model: string) => Promise<boolean>)=} setModel
  *   — SDK pm only (Query.setModel live).
  * @property {((sessionKey: string, settings: {effortLevel?: string}) => Promise<boolean>)=} applyFlagSettings

package/lib/pm-router.js

@@ -149,6 +149,16 @@ function createPmRouter({ cliPm, sdkPm = null, pickPmKindFor } = {}) {
       const target = routedPm(sessionKey);
       return typeof target.steer === 'function' ? target.steer(sessionKey, ...args) : false;
     },
+    // rc.42: native autosteer / queue. CLI pm doesn't have an
+    // input-controller push primitive (the binary's stream-json
+    // input is one-shot per pm.send), so it returns false. SDK pm
+    // forwards to its inject implementation.
+    injectUserMessage(sessionKey, opts) {
+      const target = routedPm(sessionKey);
+      return typeof target.injectUserMessage === 'function'
+        ? target.injectUserMessage(sessionKey, opts)
+        : false;
+    },
     resetSession(sessionKey, opts) {
       const target = routedPm(sessionKey);
       return typeof target.resetSession === 'function'

package/lib/stream-reply.js

@@ -55,6 +55,14 @@ function createStreamer({
   schedule = setTimeout,
   cancel = clearTimeout,
   logger = console,
+  // rc.44: by default, KEEP intermediate "thinking out loud" bubbles
+  // when forceNewMessage transitions to a fresh bubble for a new
+  // top-level assistant message. Pre-rc.44 those were pushed onto
+  // archived[] and deleted at turn-end, leaving only the final
+  // answer visible — but users wanted the full reasoning trail
+  // visible, especially in DM debugging contexts. Set to false to
+  // restore the 0.7.2 "delete intermediate" behaviour.
+  preserveIntermediateBubbles = true,
 } = {}) {
   throttleMs = Math.max(THROTTLE_FLOOR_MS, throttleMs);
   let state = 'idle';       // 'idle' | 'live' | 'finalized'
@@ -158,15 +166,26 @@ function createStreamer({
   // emits a new top-level assistant message mid-turn (post tool-result):
   // we want it in its own bubble below the previous one, not appended
   // via editMessageText to the original.
+  //
+  // rc.44: by default, the previous bubble is PRESERVED (not archived
+  // for end-of-turn deletion). Users wanted the full reasoning trail
+  // visible — "thinking out loud" + tool-use intermediates document
+  // what the agent actually did, which is valuable transparency. The
+  // 0.7.2 deletion behaviour assumed users wanted only the final
+  // answer; for chat-style DM debugging that's wrong. Opt back into
+  // the old behaviour with `preserveIntermediateBubbles: false`.
+  //
+  // When preserving, we still cancel the pending throttled edit (it
+  // wouldn't fire after we transition to a new bubble anyway) but
+  // there may be a recently-flushed edit in flight whose result we
+  // don't await — the bubble will display whatever its last
+  // successful edit landed, which is typically very close to the
+  // segment's final text (throttle is 250ms; segments take seconds).
   function forceNewMessage() {
     if (pendingEdit) { cancel(pendingEdit); pendingEdit = null; }
-    // Don't await flushPromise — the caller has decided to start a new
-    // message; whatever the old bubble shows is "done".
-    // 0.7.2: track the previous bubble's msgId for end-of-turn cleanup.
-    // Without this, every intermediate "thinking out loud" assistant
-    // message in a tool-heavy turn leaves a permanent bubble in the
-    // chat — the user wants only the final answer's bubble visible.
-    if (msgId != null) archived.push(msgId);
+    if (msgId != null && !preserveIntermediateBubbles) {
+      archived.push(msgId);
+    }
     msgId = null;
     currentText = '';
     latestText = '';

package/package.json

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

@@ -2303,6 +2303,15 @@ async function handleMessage(sessionKey, chatId, msg, bot) {
     },
     minChars: botCfg.streamMinChars,
     throttleMs: botCfg.streamThrottleMs,
+    // rc.44: preserve intermediate "thinking out loud" bubbles by
+    // default. Per-chat / per-bot opt-out via
+    // `preserveIntermediateBubbles: false` for chats where the
+    // partner-facing UX wants only the final answer (e.g. UMI Group).
+    preserveIntermediateBubbles: chatConfig.preserveIntermediateBubbles != null
+      ? chatConfig.preserveIntermediateBubbles
+      : (botCfg.preserveIntermediateBubbles != null
+        ? botCfg.preserveIntermediateBubbles
+        : true),
     logger: { error: (m) => console.error(`[${label}] ${m}`) },
   });
   // streamer is registered with this turn via pm.send's context (below)