Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.282 ·

Command output that arrives during a running turn is now held until the turn ends

Output from commands run while Claude is responding is now added after the response instead of landing in the middle of it, behind tengu_foamy_spring

Group of 2 You'll notice Improvements
JSON All of v2.1.282
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
ImprovementsKind: in v2.1.282,
ImprovementsSection of the release

What

A turn is one round of Claude working on your request. Before this release, messages produced by commands during a running turn were inserted into the conversation straight away, in the middle of the turn. A new appendAfterTurn path now holds them back:

  • It covers failed immediate commands sent over the bridge (remote control), where the failure row reads "failed (detail withheld on this connection)", meta messages from commands, a helper that appends meta rows, and several slash-command and printRows call sites.
  • While a turn is running, these rows wait in _rowsHeldForTurnEnd. When the turn stops, _releaseRowsHeldForTurnEnd adds them to the conversation, as long as it is still the same turn that was running.
  • The behaviour sits behind the server-side flag tengu_foamy_spring, which counts as on when the server gives no value. When the flag is off, rows are added immediately, as before.

Why

Output from a command you run while Claude is responding now appears after the response instead of interleaving with it. That keeps the turn's messages in order and avoids a streaming reply being broken up by unrelated rows.

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 unclear whether this behaviour always applies or only when that remote switch is on.

See this entry in the whole of v2.1.282 →

Feedback