{"version":"2.1.224","anchor":"cross-session-messaging-inbox-now-actually-starts-at-startup","canonical_anchor":"cross-session-messaging-inbox-now-actually-starts-at-startup","heading":"Cross-session messaging inbox now actually starts at startup","tier":"soon","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/cross-session-messaging-inbox-now-actually-starts-at-startup","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Cross-session messaging inbox now actually starts at startup\n\nStartup can now actually open the local socket that lets other sessions message you.\n\n**What**\n\nStartup opens a local socket so other Claude Code sessions on the same machine can send this one messages. In the previous build the call site was empty. It is off unless the `tengu_harbor_kite` gate is on (in-source fallback false) or `CLAUDE_CODE_HARBOR_KITE` is set, and it never runs on Windows.\n\n**Details**\n\n- Startup clears `CLAUDE_CODE_MESSAGING_SOCKET` and, unless a socket path was passed explicitly, uses the default path.\n- Success and failure are reported as `agents_cross_session_inbox`, with a `bind_failed` reason; setup time is recorded as `setup_uds_messaging_ms`.\n- Skipped with a log line on remote thin clients and when the gate is off.\n\n**Evidence**\n\n`[uds-messaging] Skipped: cross-session messaging gate off`\n\n- Flag `tengu_harbor_kite`: Off by default, switched on for this account (read for one account on one subscription tier against v2.1.224; this account: on, anonymous baseline: on, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Cross-Session Messaging\n- Names: `CLAUDE_CODE_HARBOR_KITE`, `CLAUDE_CODE_MESSAGING_SOCKET`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 5\/5\n- Present in the build but not switched on"}