{"version":"2.1.224","anchor":"cross-session-messages-from-a-coordinator-are-now-delivered-","canonical_anchor":"cross-session-messages-from-a-coordinator-are-now-delivered-","heading":"Cross-session messages from a coordinator are now delivered by default","tier":"use","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/cross-session-messages-from-a-coordinator-are-now-delivered-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Cross-session messages from a coordinator are now delivered by default\n\nTask notifications from a coordinator session now arrive automatically unless you set crossSessionInbound to refuse or hold.\n\n**What**\n\nMessages 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.\n\n**Details**\n\n- The other two classes are peer messages, which follow the existing peer policy, and ungated messages.\n- `hold` puts coordinator messages into the same hold queue as peer messages; the queue drops its oldest entry when full.\n- Only an explicit `crossSessionInbound` value can hold or refuse this class, so an unset config means accept.\n\n**Evidence**\n\n`Your \"crossSessionInbound\" setting is \"hold\".`\n\n- Area: Cross-Session Messaging\n- Names: `crossSessionInbound`, `refuse`, `hold`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 4\/5"}