{"version":"2.1.224","anchor":"messages-relayed-between-your-own-sessions-are-now-labelled-","canonical_anchor":"messages-relayed-between-your-own-sessions-are-now-labelled-","heading":"Messages relayed between your own sessions are now labelled as such","tier":"internal","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/messages-relayed-between-your-own-sessions-are-now-labelled-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Messages relayed between your own sessions are now labelled as such\n\nMessages relayed from your other sessions are now tagged as peer sends rather than looking like scheduled triggers.\n\n**What**\n\nA message delivered to one session from another of your sessions, sent by the model through a coordinator SendMessage, now carries `subkind: \"peer-send-message\"` on its origin instead of being indistinguishable from a scheduled trigger. Anything reading `origin.subkind` should expect this additional value alongside `scheduled-trigger`.\n\n**Details**\n\n- These deliveries keep the same prompt authority as task notifications but are now distinguishable on the wire.\n- The classifier stamps the new value when an inbound message arrives over the coordinator path, so the receive-side `crossSessionInbound` setting can apply to it.\n\n**Evidence**\n\n`so the receive-side crossSessionInbound setting can apply to it`\n\n- Area: Cross-Session Messaging\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5"}