[brentrager]

Problem

On the SMOODEV-4125 bench, six gpt-6-luna turns died on stream read error: error decoding response body, after 17 to 428s, and were counted INCONCLUSIVE. chat_stream retries only the initial send. A body that breaks in transit failed the whole turn, and the error was formatted with {e}, so the source chain (reset, truncation or timeout) was lost.

Solution

• Body read errors (OpenAI-compatible and Anthropic paths) are now a typed StreamInterrupted (re-exported) that carries the full source() chain.
• run_with_channel re-asks the same request up to MAX_STREAM_RETRIES (2) times with 500ms/1s backoff, and emits AgentEvent::LlmStreamRetry { iteration, attempt, max_retries, error }.
• It retries ONLY when all of these hold:
  • the response has not completed (Done not seen);
  • no answer text reached the consumer (so a server streaming the reply never shows it twice);
  • the error is a StreamInterrupted, not a refusal or a malformed event.
• Tool calls dispatch and the conversation/cost are recorded only after a complete response, so a retry never repeats an action or bills twice. The retry sits ahead of gateway_list_price_for / record_cost_and_check_budget.
• MockLlmClient::push_stream_interrupted scripts a mid-stream break.

Verification

• New tests:
  • re-asked once and the turn completes;
  • bounded at 2;
  • an error after a complete tool-call response is NOT retried and the tool is not dispatched;
  • not retried after answer text;
  • only StreamInterrupted qualifies (including through .context());
  • backoff;
  • the source chain is kept.
• cargo fmt --all -- --check, cargo clippy --workspace --all-targets -- -D warnings, cargo test --workspace: all green (640 core lib tests).

For #208 (1.15.0). @stream-usage owns the changeset.

Jira: SMOODEV-4158

🤖 Generated with Claude Code

[changeset-bot]

⚠️ No Changeset found

Latest commit: 935edb5

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR