polygram 0.9.0-rc.6 → 0.9.0-rc.7

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
   "name": "polygram",
-  "version": "0.9.0-rc.6",
+  "version": "0.9.0-rc.7",
   "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 plus history (transcript queries) and polygram-send (out-of-turn IPC sends with file-upload validation) skills.",
   "keywords": [
     "telegram",

package/lib/error/classify.js

@@ -60,6 +60,20 @@ const PATTERNS = {
   // "input...missing" or "missing...input" within a tool_use mention.
   missingToolInput: /tool[_ ]use.*(input.*missing|missing.*input)|missing tool call input|tool input required/i,
 
+  // Anthropic API rejected an image content block in the conversation.
+  // 2026-05-13: shumabit Dina DM hit this after accumulating 53 images
+  // over 2 weeks — every new turn 400'd with raw API JSON dumped to
+  // the user. Most common cause: a persisted image in the resumed
+  // transcript that the API now considers invalid (model snapshot
+  // drift, expired URL, bad base64, dimension/size cap, format the
+  // API stopped accepting). Recovery: reset_session — /compact has
+  // to load the same history so it usually fails too.
+  //
+  // Anchor on the literal Anthropic phrase to avoid false positives
+  // on routine "image" mentions. Tightened by requiring an
+  // image-failure verb co-located with "image" or "photo".
+  imageProcess:     /(could not process|cannot process|failed to (process|load|decode)|unsupported|invalid|corrupt(?:ed)?)[^\n]{0,80}\b(image|photo)\b|\b(image|photo)\b[^\n]{0,80}(could not process|failed to (process|load|decode)|is (invalid|corrupted|unsupported))/i,
+
   // Idle/wall-clock timeout from polygram's pm timers, OR
   // model-side timeout. Mapped to a single class; user message is
   // identical either way.
@@ -87,6 +101,7 @@ const USER_MESSAGES = {
   contextOverflow:  '📚 Conversation got too long. Send /new to start fresh.',
   roleOrdering:     '⚠️ Conversation got into a tangled state. Try /new.',
   missingToolInput: '⚠️ Session history looks corrupted. Try /new.',
+  imageProcess:     '🖼 One of the images in this conversation can\'t be re-processed by Claude — likely an older one in the history. Starting a fresh session for this chat.',
   timeout:          '⏳ I went quiet too long without finishing. Try resending or simplifying.',
   format:           '⚠️ Invalid request format. Try rephrasing or /new.',
   // Used both for in-flight retry attempts AND for the post-retry-failed
@@ -106,6 +121,7 @@ const AUTO_RECOVER = {
   roleOrdering:     'reset_session',
   contextOverflow:  'reset_session',
   missingToolInput: 'reset_session',
+  imageProcess:     'reset_session',
 };
 
 // Typed-code short-circuits — set on errors polygram throws itself
@@ -300,8 +316,45 @@ function isTransientHttpError(err) {
   return classify(err).isTransient;
 }
 
+// 2026-05-13: detect the case where SDK reports result_subtype=success
+// BUT the assistant text is actually an API error JSON the SDK wrapped
+// as if it were the model's reply. Happens when the resumed session's
+// transcript has data the API can't reload — most commonly an image
+// content block. Pattern is distinctive ("API Error: <code> {...
+// type:error ...}") so false positives are unlikely.
+//
+// When this matches:
+//   - The text we'd deliver to Telegram is garbage (raw JSON).
+//   - The Claude session is wedged — every future turn will fail the
+//     same way until reset.
+// Returns the same shape as classify() so callers can use it uniformly,
+// or null when the text looks like a legitimate assistant reply.
+const WEDGED_SESSION_RE = /^API Error: \d{3}\s+\{[^}]*"type"\s*:\s*"error"/;
+
+function detectWedgedSessionError(text) {
+  if (typeof text !== 'string' || text.length === 0) return null;
+  if (!WEDGED_SESSION_RE.test(text)) return null;
+  // Once we've confirmed it's a wrapped API error, run classify on the
+  // text — it picks up imageProcess / rateLimit / billing / etc. from
+  // the JSON body. classify is robust to JSON-ish input.
+  const cls = classify(new Error(text));
+  // If classify fell through to 'unknown', return a safe imageProcess
+  // shape — wedged sessions are most commonly image-driven and the
+  // recovery action (reset_session) is correct for all wedge classes.
+  if (cls.kind === 'unknown') {
+    return {
+      kind: 'imageProcess',
+      userMessage: USER_MESSAGES.imageProcess,
+      isTransient: false,
+      autoRecover: 'reset_session',
+    };
+  }
+  return cls;
+}
+
 module.exports = {
   classify,
+  detectWedgedSessionError,
   isTransientHttpError,
   PATTERNS,
   USER_MESSAGES,

package/package.json

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

package/polygram.js

@@ -75,7 +75,7 @@ const { startTyping } = require('./lib/telegram/typing');
 // consumer is lib/handlers/download.js.
 const { createReactionManager, classifyToolName } = require('./lib/telegram/reactions');
 const { createMediaGroupBuffer } = require('./lib/media-group-buffer');
-const { classify: classifyError, isTransientHttpError } = require('./lib/error/classify');
+const { classify: classifyError, detectWedgedSessionError, isTransientHttpError } = require('./lib/error/classify');
 const { createAutoResumeTracker, isAutoResumable } = require('./lib/db/auto-resume');
 const { resolveReplayWindowMs } = require('./lib/db/replay-window');
 // validateIpcFileParam moved with handleSendOverIpc to
@@ -1019,14 +1019,41 @@ async function handleMessage(sessionKey, chatId, msg, bot) {
 
     stopTyping();
 
+    // 2026-05-13 Dina-DM incident: SDK reports result_subtype=success
+    // but the "assistant text" is actually an API error JSON the SDK
+    // wrapped (e.g. wedged image content block in resumed transcript).
+    // Without this guard, polygram delivers the raw JSON to Telegram
+    // as the bot's reply AND never resets the session — every
+    // subsequent turn loops the same wedge.
+    //
+    // Sniff result.text for the wrapper pattern BEFORE the error/text
+    // branch decisions. When detected: synthesize an Error so the
+    // standard result.error path runs (classification → reset_session
+    // → friendly user message → no raw-JSON delivery).
+    if (!result.error && detectWedgedSessionError(result.text)) {
+      const wedge = detectWedgedSessionError(result.text);
+      logEvent('wedged-session-detected', {
+        chat_id: chatId, session_key: sessionKey,
+        kind: wedge.kind,
+        text_preview: result.text.slice(0, 200),
+      });
+      // Promote the wrapped error to result.error so the existing
+      // auto-recover + thrown-error machinery handles it uniformly.
+      // Clear result.text so downstream delivery doesn't send the
+      // raw JSON.
+      result.error = result.text;
+      result.text = '';
+    }
+
     if (result.error) {
       console.error(`[${label}] Error (${elapsed}s):`, result.error);
       reactor.setState('ERROR');
       // 0.8.0 Phase 2 step 8: classifier-driven auto-recovery. If
       // the error kind has autoRecover === 'reset_session' (i.e.
-      // role_ordering / context_overflow / missing_tool_input),
-      // tell pm to reset the session NOW so the user's NEXT
-      // message starts fresh — without them having to type /new.
+      // role_ordering / context_overflow / missing_tool_input /
+      // imageProcess), tell pm to reset the session NOW so the
+      // user's NEXT message starts fresh — without them having
+      // to type /new.
       const cls = classifyError(result.error);
       if (cls.autoRecover === 'reset_session') {
         pm.resetSession(sessionKey, { reason: cls.kind })