alvin-bot 4.18.2 → 4.18.3

package/CHANGELOG.md

@@ -2,6 +2,14 @@
 
 All notable changes to Alvin Bot are documented here.
 
+## [4.18.3] — 2026-04-23
+
+### 🐛 Hotfix: 4.18.2 triggered unwanted failover to Ollama
+
+**Bug in 4.18.2:** The empty-stream detector yielded an `error` chunk, which the registry's `queryWithFallback()` interprets as "primary provider failed" and immediately switches to the fallback (Ollama/Gemma 4). User saw `⚡ Claude (Agent SDK) unavailable — switching to Gemma 4 E4B` after every token rotation — the opposite of the intended behavior.
+
+**Fix:** yield a `text` chunk instead of `error`. Same user-visible message, same cache-invalidation, but no failover cascade. The next CLI subprocess spawns with the fresh Keychain token automatically, and claude-sdk stays selected.
+
 ## [4.18.2] — 2026-04-23
 
 ### 🐛 Fix: silent empty-stream after OAuth-token rotation

package/dist/providers/claude-sdk-provider.js

@@ -309,33 +309,40 @@ export class ClaudeSDKProvider {
                         ? (usage.input_tokens || 0) + (usage.cache_creation_input_tokens || 0) + (usage.cache_read_input_tokens || 0)
                         : 0;
                     const outputTok = usage?.output_tokens || 0;
-                    // v4.18.2 — Silent-empty-stream detection.
+                    // v4.18.3 — Silent-empty-stream detection (replaces 4.18.2 approach).
                     //
                     // If the stream terminated cleanly but produced ZERO text chunks,
-                    // something went wrong that the SDK didn't surface as an error:
-                    // most commonly a stale OAuth token after /extra-usage or /login
-                    // rotated the Keychain entry while our in-memory SDK client was
-                    // still holding the old one. The CLI subprocess silently gets a
-                    // 401, emits no text, and we complete the stream with
-                    // accumulatedText === "". The user sees "(Keine Antwort)".
+                    // something went wrong that the SDK didn't surface as an error.
+                    // Most common cause: the OAuth token in the Keychain was rotated
+                    // (e.g. right after /extra-usage or /login) while our in-memory
+                    // SDK client still held the old one — the CLI subprocess silently
+                    // gets a 401, emits no text, and we complete with
+                    // accumulatedText === "".
                     //
-                    // We flip this from silent failure to explicit error. Clearing
-                    // the availability cache forces the next heartbeat probe to
-                    // re-check `claude auth status` with a fresh subprocess (which
-                    // reads the current Keychain entry).
+                    // CRITICAL: we must NOT yield an "error" chunk here — the registry's
+                    // queryWithFallback() treats that as "primary failed" and kicks off
+                    // a full failover to the next provider (Ollama). That's exactly
+                    // wrong: the next CLI subprocess would have picked up the fresh
+                    // token by itself. Instead we:
+                    //   1. Invalidate the availability cache so the next heartbeat
+                    //      re-probes `claude auth status` with a fresh subprocess.
+                    //   2. Return a friendly "text" chunk explaining what happened,
+                    //      so the user sees a clear message (not "(Keine Antwort)")
+                    //      and knows to resend — without tripping the failover.
                     if (accumulatedText === "" && outputTok === 0) {
                         this.invalidateAvailabilityCache();
+                        const hint = "⚠️ Claude antwortete mit leerem Stream (meist nach /extra-usage, /login oder Token-Refresh). " +
+                            "Der SDK-Token-Cache wurde geleert — bitte schick die Nachricht einfach nochmal.";
                         yield {
-                            type: "error",
-                            error: "Claude returned an empty response. " +
-                                "This can happen right after /extra-usage, /login, or a token refresh — " +
-                                "the SDK held a stale auth token. I've invalidated the cache; please resend your message.",
+                            type: "text",
+                            text: hint,
+                            delta: hint,
+                            sessionId: resultMsg.session_id || capturedSessionId,
                         };
-                        return;
                     }
                     yield {
                         type: "done",
-                        text: accumulatedText,
+                        text: accumulatedText || "",
                         sessionId: resultMsg.session_id || capturedSessionId,
                         costUsd: "total_cost_usd" in resultMsg ? resultMsg.total_cost_usd : 0,
                         inputTokens: inputTok,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "alvin-bot",
-  "version": "4.18.2",
+  "version": "4.18.3",
   "description": "Alvin Bot \u2014 Your personal AI agent on Telegram, WhatsApp, Discord, Signal, and Web.",
   "type": "module",
   "main": "dist/index.js",