What probably matters to youSection of the release
What
Messages arriving from another session are now sorted into three classes, and a new "coordinator" class (a task notification that carries a peer send-message) is delivered unless you explicitly set crossSessionInbound. Set it to refuse to reject them or hold to buffer them; with no setting at all, coordinator messages are accepted outright.
Details
The other two classes are peer messages, which follow the existing peer policy, and ungated messages.
hold puts coordinator messages into the same hold queue as peer messages; the queue drops its oldest entry when full.
Only an explicit crossSessionInbound value can hold or refuse this class, so an unset config means accept.
Evidence
Your "crossSessionInbound" setting is "hold".
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's release notes agreeAdded crossSessionInbound and dialogExpiry settings: cross-session messages sent to a session running with bypassed permissions are held for…
The name it cites is new in this buildNew in this build: crossSessionInbound
