Headless output write failures now produce a proper failed result object in stream-json.
What's wrong with this entry?
If a message cannot be written to the headless output stream, Claude now writes an Error: line to stderr, marks the turn's summary as failed, and in stream-json mode emits a result object with an error_during_execution subtype built by a shared helper.
- The stderr line begins
Could not write a message to the output stream. - Paired with a
tengu_headless_fatal_errorevent carrying the site, message type, control subtype, drained message count, outstanding stdout bytes and whether stdout was destroyed. - None of this existed in v2.1.226.
Could not write a message to the output stream
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.246
Non-interactive runs retry a response that was cut off mid-stream
Both mention headless mode
-
v2.1.246
Headless idle detection now waits for background tasks and undelivered notifications
Both mention headless mode
-
v2.1.246
Headless runs no longer report themselves busy while blocked on a prompt
Both mention headless mode