Follow Discord
Sweep 29 Sep 2026 · 18:10Z Build v2.1.285 506 read Stable v2.1.280 Latest v2.1.285 Next v2.1.285 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.285 ·

Diagnostics file can now record slow or stalled streaming responses

With CLAUDE_CODE_DIAGNOSTICS_FILE set, Claude Code can log a record whenever a piece of a streamed response arrives slowly

Use it now No documentation found Improvements
JSON All of v2.1.285
Use it nowTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
DiagnosticsArea: what it touches
ImprovementsKind: in v2.1.285,
What probably matters to youSection of the release
What

The diagnostics file set with CLAUDE_CODE_DIAGNOSTICS_FILE can now capture stalls in streamed responses. A streamed response arrives as a series of pieces, called frames. When a frame arrives slowly, Claude Code writes a cli_sse_frame_stall record noting:

  • the gap before the frame arrived
  • how far Claude Code's own processing had fallen behind
  • how much CPU time was used

The stall watcher is only created when CLAUDE_CODE_DIAGNOSTICS_FILE is set and the code reading the stream asks for it. Otherwise nothing is measured.

Separately, the waits between reconnect attempts and between retried requests are now worked out by one shared routine instead of separate calculations.

Why

This is for troubleshooting only. Nothing changes unless you set the diagnostics file, and if you do, it gives you a way to see where a slow response was held up.

Read from
Names in the bundleCLAUDE_CODE_DIAGNOSTICS_FILE
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear whether every streamed response is watched once the diagnostics file is set, or only some.

See this entry in the whole of v2.1.285 →

Feedback