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
printRowscall sites. - While a turn is running, these rows wait in
_rowsHeldForTurnEnd. When the turn stops,_releaseRowsHeldForTurnEndadds 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.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
It is unclear whether this behaviour always applies or only when that remote switch is on.