polygram 0.5.7 → 0.5.9

package/lib/process-manager.js

@@ -168,6 +168,12 @@ class ProcessManager {
    * If the queue is empty, kill now; otherwise mark the entry so it kills
    * itself when the last pending resolves. Next send() respawns fresh
    * with whatever config spawnFn reads at that moment.
+   *
+   * onRespawn fires with `wasDrained=true` ONLY when we waited for an
+   * in-flight turn to finish before swapping. The immediate-kill case
+   * (queue empty at request time) calls onRespawn with `wasDrained=false`
+   * so callers can decide whether to post a user-visible confirmation
+   * (which is redundant noise when the user wasn't waiting on a turn).
    */
   requestRespawn(sessionKey, reason = 'config-change') {
     const entry = this.procs.get(sessionKey);
@@ -181,17 +187,17 @@ class ProcessManager {
     });
     if (entry.pendingQueue.length === 0) {
       // Queue empty — kill immediately, fire onRespawn after close.
-      this._killAndNotifyRespawn(sessionKey, reason).catch(() => {});
+      this._killAndNotifyRespawn(sessionKey, reason, false).catch(() => {});
       return { killed: true, queued: 0 };
     }
     return { killed: false, queued: entry.pendingQueue.length };
   }
 
-  async _killAndNotifyRespawn(sessionKey, reason) {
+  async _killAndNotifyRespawn(sessionKey, reason, wasDrained) {
     const entry = this.procs.get(sessionKey);
     await this.kill(sessionKey);
     if (this.onRespawn && entry) {
-      try { this.onRespawn(sessionKey, reason, entry); }
+      try { this.onRespawn(sessionKey, reason, entry, wasDrained); }
       catch (err) { this.logger.error(`[pm] onRespawn: ${err.message}`); }
     }
   }
@@ -321,7 +327,10 @@ class ProcessManager {
               chat_id: entry.chatId,
               reason,
             });
-            this._killAndNotifyRespawn(sessionKey, reason).catch(() => {});
+            // wasDrained=true: this path runs after the queue emptied
+            // naturally (an in-flight turn finished), so the user was
+            // waiting and the confirmation message is meaningful.
+            this._killAndNotifyRespawn(sessionKey, reason, true).catch(() => {});
           }
         }
       }

package/package.json

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

@@ -811,7 +811,18 @@ function buildConfigKeyboard(chatConfig, show = 'all') {
 // Card text shown above the inline keyboard. Includes plain-language
 // guidance on when to pick which model / effort, since most users
 // (especially in shared groups) don't know which option to tap.
-const MODEL_VERSIONS_DESC = { opus: 'claude-opus-4-6', sonnet: 'claude-sonnet-4-6', haiku: 'claude-haiku-4-5' };
+//
+// Model versions: polygram passes the alias ("opus", "sonnet", "haiku")
+// to claude, which resolves it to the latest snapshot. We mirror those
+// snapshots here for display only, and verify them on each release with
+// `claude --model <alias>` (probing the system:init event's `model`
+// field). Bumping is a manual step — when claude releases a new
+// snapshot the alias maps to, update this map and ship.
+const MODEL_VERSIONS_DESC = {
+  opus: 'claude-opus-4-7',
+  sonnet: 'claude-sonnet-4-6',
+  haiku: 'claude-haiku-4-5',
+};
 
 function formatConfigInfoText(chatConfig, show, sessionKey) {
   const alive = pm.has(sessionKey) && !pm.get(sessionKey).closed;
@@ -1196,7 +1207,9 @@ async function handleMessage(sessionKey, chatId, msg, bot) {
     ...(tid && { message_thread_id: tid }),
   });
 
-  const MODEL_VERSIONS = { opus: 'claude-opus-4-6', sonnet: 'claude-sonnet-4-6', haiku: 'claude-haiku-4-5' };
+  // Single source of truth at module scope (MODEL_VERSIONS_DESC) — see the
+  // comment there for the bump procedure.
+  const MODEL_VERSIONS = MODEL_VERSIONS_DESC;
 
   const botAllowsCommands = !!config.bot?.allowConfigCommands;
   const cmdUser = msg.from?.first_name || msg.from?.username || null;
@@ -2161,8 +2174,13 @@ async function main() {
     },
     // Fires after a graceful /model or /effort drain has actually
     // swapped to the new settings. Post a confirmation back to the
-    // chat so the user knows the switch happened.
-    onRespawn: (sessionKey, reason, entry) => {
+    // chat ONLY when wasDrained=true — the user actively waited for an
+    // in-flight turn to finish before the switch took effect, so the
+    // explicit "switched" message is meaningful. When the kill was
+    // immediate (queue empty), the inline-card update + button toast
+    // already convey "done", and a separate message is just noise.
+    onRespawn: (sessionKey, reason, entry, wasDrained) => {
+      if (!wasDrained) return;
       const chatId = entry.chatId;
       if (!chatId) return;
       const chatConfig = config.chats[chatId];