{"version":"2.1.248","anchor":"cross-session-messages-from-sub-agents-now-say-whose-address","canonical_anchor":"cross-session-messages-from-sub-agents-now-say-whose-address","heading":"Cross-session messages from sub-agents now say whose address they were sent under","tier":"notice","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/cross-session-messages-from-sub-agents-now-say-whose-address","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Cross-session messages from sub-agents now say whose address they were sent under\n\nMessages a sub-agent sends elsewhere now say they went under the session's address.\n\n**What**\n\nWhen a sub-agent sends a message to another session, the tool result now explains that the message went out under the session's address rather than the agent's, and where any reply will land. It is on for everyone on this build, with no flag.\n\n**Details**\n\n- Applies to both delivery paths: the inter-session bridge and the local socket path.\n- Two wordings: a one-way form used when the bridge only has a one-way route, or when the socket path finds no messaging socket of its own, and the default form.\n- The user-visible display string is the parenthetical variant.\n\n**Evidence**\n\n`; sent under this session's address: any reply will be delivered to this session's main conversation, not to this agent`\n\n- Area: Cross-Session Messaging\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}