Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.248 Home All releases ←olderv2.1.247 v2.1.250newer→
Claude Code v2.1.248

Headless output failures report a transport write failure instead of raw error text

You'll notice
Useful2 Signal2
Headless Mode

Headless output failures say "transport write failure" and put the real reason in the log.

What

When the output stream dies in headless mode, the "session has ended" message now says "transport write failure" for redacted or remote sessions rather than printing the underlying error. The full reason is written to the error log instead.

Evidence

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.

See this entry in the whole of v2.1.248 →