{"version":"2.1.228","anchor":"the-cross-session-inbox-can-bind-after-startup-if-remote-con","canonical_anchor":"the-cross-session-inbox-can-bind-after-startup-if-remote-con","heading":"The cross-session inbox can bind after startup if remote config turns it on","tier":"internal","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/the-cross-session-inbox-can-bind-after-startup-if-remote-con","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### The cross-session inbox can bind after startup if remote config turns it on\n\nCross-session messaging can now switch on mid-session if config arrives late, instead of staying off.\n\n**What**\n\nWhen the cross-session messaging gate is off at startup and configuration has not settled, Claude Code now installs a watcher that binds the socket later if a config refresh enables it, then publishes the socket path to the session record. Previously the inbox was skipped for the life of the process.\n\n**Details**\n\n- The late path is distinguished in telemetry by a bind_late marker.\n- The gate name does not appear in readable form in the build, so which remote flag flips it is not visible from here.\n\n**Evidence**\n\n`[uds-messaging] Late bind: gate enabled by a GrowthBook refresh after startup`\n\n- Area: Cross-Session Messaging\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}