{"version":"2.1.265","anchor":"cross-session-messaging-uds-inbox-startup-path-has-its-own","canonical_anchor":"unix-domain-socket-startup-pipeline-gains-named-profiling-ph","heading":"Startup profiling for the cross-session messaging inbox","tier":"internal","area":"Startup","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/cross-session-messaging-uds-inbox-startup-path-has-its-own","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Startup profiling for the cross-session messaging inbox\n\nClaude Code now times each phase of starting the local cross-session messaging inbox and logs when it's skipped\n\n**What**\n\nSession startup now records named timing marks around the setup of the cross-session inbox, a local Unix-domain-socket (a file-based connection used for communication between processes on the same machine) channel that lets separate Claude Code sessions message each other.\n\n- New timing marks bracket the dynamic import and startup call: `setup_uds_start`, `setup_uds_imported`\/`setup_uds_import`, and `setup_uds_end`, corresponding to phases named `setup_uds_messaging`, `setup_uds_dir`, `setup_uds_listen`, and `setup_uds_publish`.\n\n- A new `profileStartup` option is passed into the inbox startup call, which gates three more marks inside it: `uds_inbox_dir_ready`, `uds_inbox_listening`, and `uds_inbox_key_published`.\n\n- If the feature is gated off, startup now logs an explicit message: \"cross-session messaging gate off (will late-bind if a GrowthBook refresh enables it)\".\n\n**Why**\n\nThis gives clearer visibility into where time goes during cross-session messaging startup, and makes it obvious in logs when the feature is intentionally skipped versus failing.\n\n- Area: Startup\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}