You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
API RequestsArea: what it touches
ImprovementsKind: in v2.1.299,
ImprovementsSection of the release
Unclear It is not settled what timeout applies on providers other than the Anthropic API now.
What
The byte-stream idle timeout is how long Claude Code waits when a reply arrives with no new data before treating the stream as stalled. You can also set it yourself with CLAUDE_BYTE_STREAM_IDLE_TIMEOUT_MS. Claude Code can receive a default for this timeout from Anthropic's servers. It now uses that default only when it talks to the Anthropic API directly. When you use another provider, such as Bedrock or Vertex, it no longer falls back to that default.
Before, the fallback applied to every provider, with a different default for providers other than the Anthropic API.
Why
This changes how stalled replies are handled on Bedrock, Vertex and other providers.
tengu_byte_stream_idle_timeout_msNot enough to say
Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.299: not a boolean we can read
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
