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.228 Home All releases ←olderv2.1.227 v2.1.229newer→
Claude Code v2.1.228

Local messaging inbox publishes an auth key so peers can prove who they are

Under the hood
Useful2 Signal2
Cross-Session Messaging not in their notes

Your local message inbox publishes a key file so other sessions can prove who they are.

CLAUDE_CODE_MESSAGING_TOKEN
What

The local socket other Claude Code processes use to send you messages now writes an auth key file and exports CLAUDE_CODE_MESSAGING_TOKEN to child processes. On platforms where auth is required, a failure to publish the key shuts the inbox down rather than accepting unauthenticated peers.

Details
  • The key file is written after the socket permissions are set.
  • Shutdown in the hard-failure case is recorded with cause key_publish_failed.
  • Where the platform treats auth as optional, the failure logs a warning and the inbox keeps running with peers sending unauthenticated.
Evidence

refusing to run an inbox no peer can authenticate to

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