{"version":"2.1.248","anchor":"messages-sent-by-an-agent-are-labelled-with-the-session-addr","canonical_anchor":"messages-sent-by-an-agent-are-labelled-with-the-session-addr","heading":"Messages sent by an agent are labelled with the session address","tier":"notice","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/messages-sent-by-an-agent-are-labelled-with-the-session-addr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Messages sent by an agent are labelled with the session address\n\nMessages a subagent sends under the session address are now labelled in your transcript.\n\n**What**\n\nWhen a subagent sends a message using the session's own address, Claude Code now attaches a note for the model and a suffix in the transcript, and distinguishes a one-way send from one whose replies come back into the main conversation.\n\n**Details**\n\n- Two variants: a send that expects no reply, and one marked as having replies routed into the main conversation.\n- The same helper produces both the model-facing text and the display suffix, so what you see and what the model sees stay in step.\n\n**Evidence**\n\n`replies go to the main conversation`\n\n- Area: Cross-Session Messaging\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}