{"version":"2.1.228","anchor":"local-messaging-inbox-publishes-an-auth-key-so-peers-can-pro","canonical_anchor":"local-messaging-inbox-publishes-an-auth-key-so-peers-can-pro","heading":"Local messaging inbox publishes an auth key so peers can prove who they are","tier":"internal","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/local-messaging-inbox-publishes-an-auth-key-so-peers-can-pro","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Local messaging inbox publishes an auth key so peers can prove who they are\n\nYour local message inbox publishes a key file so other sessions can prove who they are.\n\n**What**\n\nThe 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.\n\n**Details**\n\n- The key file is written after the socket permissions are set.\n- Shutdown in the hard-failure case is recorded with cause `key_publish_failed`.\n- Where the platform treats auth as optional, the failure logs a warning and the inbox keeps running with peers sending unauthenticated.\n\n**Evidence**\n\n`refusing to run an inbox no peer can authenticate to`\n\n- Area: Cross-Session Messaging\n- Names: `CLAUDE_CODE_MESSAGING_TOKEN`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}