Source Intelligence

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.234 Home All releases olderv2.1.233 v2.1.235newer
Claude Code v2.1.234

The stdin transport now answers the remote-transport questions

Under the hood
Useful1 Signal3
Transports

Plain stdin sessions now declare they are not remote, so remote-only delivery acks and one auto-mode capability skip out.

What

The plain stdin transport declares that it is not a remote transport, that the host owns the origin of anything arriving on stdin (used to decide whether an inbound message counts as user-driven), and that a confirmed flush always succeeds. Remote-session code branches on that: delivery acks bail out with "not-remote-session", and one auto-mode capability requires a remote transport plus the remote session id.

Evidence

hostOwnsStdinOrigin

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.234 →