polygram 0.5.4 → 0.5.6

package/package.json

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

@@ -571,6 +571,37 @@ async function sendToProcess(sessionKey, prompt, context = {}) {
 const CONCURRENT_WARN_THRESHOLD = 20;
 const inFlightHandlers = new Map(); // sessionKey → count
 
+// Set true by the SIGTERM/SIGINT handler. Module-scoped so the
+// fire-and-forget catch in dispatchHandleMessage can check it: when
+// polygram is going down, in-flight handlers reject with "Process
+// killed" / "Process exited" but those failures aren't "real" — the
+// next boot's replay will re-dispatch them. Suppressing the user-facing
+// error reply during shutdown removes a misleading post-mortem apology
+// the user shouldn't see. (The boot replay's own _isReplay flag handles
+// the OTHER half: suppressing if the replay itself fails.)
+let isShuttingDown = false;
+
+// Map a handler-error to a user-facing reply that says what happened
+// and what to do next. The technical strings come from process-manager
+// (idle / wall-clock timeouts) and node child_process (Process exited /
+// killed). Anything we don't recognise falls back to a generic line
+// with a single-line snippet of the error so the user can at least
+// distinguish unique failures from the obvious "try again" cases.
+function errorReplyText(err) {
+  const msg = err?.message || '';
+  if (/idle with no Claude activity/i.test(msg)) {
+    return '⏳ I went quiet too long without finishing. Try resending or simplifying the task.';
+  }
+  if (/wall-clock ceiling/i.test(msg)) {
+    return '⏱ This was taking too long, so I stopped. Try resending or simplifying the task.';
+  }
+  if (/Process (exited|killed)/i.test(msg)) {
+    return '💥 Something crashed on my end. Try again.';
+  }
+  const reason = msg.split('\n')[0].slice(0, 120);
+  return `Hit a snag: ${reason || 'unknown error'}. Try resending.`;
+}
+
 // Sessions the operator just /stop'd (or natural-language "стоп"). Keyed
 // by sessionKey → timestamp of abort. ANY pending that rejects within
 // ABORT_GRACE_MS of the mark is considered abort-caused — its generic
@@ -627,14 +658,16 @@ function dispatchHandleMessage(sessionKey, chatId, msg, bot) {
       aborted: wasAborted || undefined,
       replay: isReplay || undefined,
     }), 'log handler-error');
-    // Suppress the "Sorry, I couldn't process" reply when this turn is a
-    // boot replay — the user typed this message minutes ago and has long
-    // moved on. A late apology just adds more noise to the post-restart
-    // chat (alongside the "Это снова реплей" cascade we're fixing).
-    if (!wasAborted && !isReplay) {
+    // Suppress the user-facing error reply when:
+    //  - boot replay (user typed this minutes ago and moved on)
+    //  - polygram is shutting down (the failure is "Process killed" /
+    //    "Process exited" which isn't a real error — boot replay will
+    //    re-dispatch it on next start)
+    //  - user just /stop'd (already saw their abort acknowledgement)
+    if (!wasAborted && !isReplay && !isShuttingDown) {
       tg(bot, 'sendMessage', {
         chat_id: chatId,
-        text: `Sorry, I couldn't process that message. The operator has been notified.`,
+        text: errorReplyText(err),
         reply_parameters: { message_id: msg.message_id },
       }, { source: 'error-reply', botName: BOT_NAME }).catch((replyErr) => {
         console.error(`[${sessionKey}] failed to send error reply: ${replyErr.message}`);
@@ -2157,10 +2190,9 @@ async function main() {
   // replay picks it up. Prevents "Sorry, I couldn't process that message"
   // from showing on every restart.
   const SHUTDOWN_DRAIN_MS = 30_000;
-  let shuttingDown = false;
   const shutdown = async () => {
-    if (shuttingDown) return;
-    shuttingDown = true;
+    if (isShuttingDown) return;
+    isShuttingDown = true;
     console.log('\nShutting down...');
     // 1. Stop accepting new inbound first so nothing new queues behind the drain.
     if (bot && bot._stop) bot._stop();