Cross-session messaging can now switch on mid-session if config arrives late, instead of staying off.
What's wrong with this entry?
When 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.
- The late path is distinguished in telemetry by a bind_late marker.
- The gate name does not appear in readable form in the build, so which remote flag flips it is not visible from here.
[uds-messaging] Late bind: gate enabled by a GrowthBook refresh after startup
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Messages injected by a host are classified separately from peer messages
Both mention cross
-
v2.1.234
Cross-session control requests check ids more carefully
Both mention cross
-
v2.1.234
Notice acks now wait for the record to persist
Both mention cross