Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.228 ·

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

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

Under the hood No documentation found New Features
JSON All of v2.1.228
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Cross-Session MessagingArea: what it touches
New FeaturesKind: in v2.1.228,
New FeaturesSection of the release
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.

Read from
Names in the bundleCLAUDE_CODE_MESSAGING_TOKEN

See this entry in the whole of v2.1.228 →

Feedback