{"version":"2.1.239","anchor":"clearer-refusal-when-a-session-tries-to-message-itself","canonical_anchor":"clearer-refusal-when-a-session-tries-to-message-itself","heading":"Clearer refusal when a session tries to message itself","tier":"notice","area":"Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/clearer-refusal-when-a-session-tries-to-message-itself","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Clearer refusal when a session tries to message itself\n\nSending a session message to yourself now gets a clear explanation instead of a generic failure.\n\n**What**\n\nSession-to-session messaging inside Claude Code now refuses self-addressed sends with wording that explains the situation instead of a generic failure. When the target resolves to the sending session, the refusal says the address is this session's own, that a message sent there would only come back to this conversation, and that there is no one else at that address to reach, along with a hint telling the model how to address the main conversation instead.\n\n**Details**\n\n- A second, longer refusal covers the case where a different session record on this machine claims this session's name and reference, and instructs the model to ask the user because the situation is suspicious.\n- Both refusal texts are new in this build, and the self-address message replaces the \"ultraplan ready\" line the same message builder used to emit.\n\n**Evidence**\n\n`is this session's own address`, `is this session's own name and ref, but another session record on this machine claims it.`\n\n- Area: Session Messaging\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}