@link-assistant/hive-mind 2.0.1 → 2.0.2

package/CHANGELOG.md

@@ -1,5 +1,42 @@
 # @link-assistant/hive-mind
 
+## 2.0.2
+
+### Patch Changes
+
+- 19aea85: fix(retry): auto-resume on "Stream idle timeout - partial response received" (#1937)
+
+  A long-running solve session (391 turns, ~$34.11) had its streaming response
+  stall mid-answer. The Claude CLI surfaced it as a `result` event with
+  `is_error: true`, `subtype: "success"`, and:
+
+  ```
+  API Error: Stream idle timeout - partial response received
+  ```
+
+  Instead of retrying with the session preserved, the harness fell straight
+  through to the generic failure path and exited with code 1 after **zero
+  retries** — abandoning the whole session even though it had a valid session ID
+  and printed the exact `--resume` command needed to continue.
+
+  Root cause: the shared retry classifier `classifyRetryableError()`
+  (`src/tool-retry.lib.mjs`) had no branch for the stream-idle-timeout family, so
+  `isRetryable` was false, `isTransientError` evaluated to false, and the unified
+  exponential-backoff retry block was never entered.
+
+  This error is a transient transport-level stall (a slow/stuck server-sent-events
+  socket), not a request-content rejection — the on-disk session transcript stays
+  valid, which is why a manual `--resume` works. The fix adds one branch to
+  `classifyRetryableError()` returning
+  `{ isRetryable: true, isCapacity: false, label: 'Stream idle timeout (partial response)' }`,
+  so the existing retry block resumes the session with the same context after an
+  exponential backoff. Because the classifier is shared, this fixes the behaviour
+  for **all** tools (claude/codex/gemini/opencode/qwen/agent) at once.
+
+  Added `tests/test-issue-1937-stream-idle-timeout-retry.mjs` (17 assertions) and a
+  full case study with timeline, root-cause analysis, upstream references, and the
+  captured logs under `docs/case-studies/issue-1937`.
+
 ## 2.0.1
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@link-assistant/hive-mind",
-  "version": "2.0.1",
+  "version": "2.0.2",
   "description": "AI-powered issue solver and hive mind for collaborative problem solving",
   "main": "src/hive.mjs",
   "type": "module",

package/src/tool-retry.lib.mjs

@@ -43,6 +43,22 @@ export const classifyRetryableError = value => {
     return { message, isRetryable: true, isCapacity: false, label: 'Stream disconnected before completion' };
   }
 
+  // Issue #1937: Stream idle timeout. When the Anthropic streaming response stalls
+  // (no bytes for the SDK's idle window) after the model has already emitted part of
+  // its answer, the Claude CLI aborts the turn and surfaces a synthetic assistant /
+  // result message:
+  //   "API Error: Stream idle timeout - partial response received"
+  // This is a transient network/streaming stall (a slow or stuck server-sent-events
+  // socket), not a request-content error, so the session is still valid and safe to
+  // resume. Before this branch classifyRetryableError() did not recognise it, so
+  // isRetryable was false and the whole solve session aborted with exit code 1 even
+  // though `--resume <sessionId>` could continue with the same context. Switching
+  // models does not help (the stall is in the response stream, not model capacity),
+  // so isCapacity is false → retry with the session preserved after a backoff.
+  if (lower.includes('stream idle timeout') || (lower.includes('idle timeout') && lower.includes('partial response'))) {
+    return { message, isRetryable: true, isCapacity: false, label: 'Stream idle timeout (partial response)' };
+  }
+
   // Issue #1881: Transient socket / network disconnects from the SDK's underlying fetch.
   // When the HTTP(S)/streaming socket drops mid-request, the Claude/Codex CLI surfaces a
   // synthetic assistant message such as: