{"version":"2.1.284","anchor":"peer-message-notice-drops-the-reply-via-sendmessage-hint-w","canonical_anchor":"peer-message-notice-drops-the-reply-via-sendmessage-hint-w","heading":"Messages from other Claude sessions no longer tell Claude to reply with SendMessage when it lacks that tool","tier":"notice","area":"Multi-Session","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/peer-message-notice-drops-the-reply-via-sendmessage-hint-w","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Messages from other Claude sessions no longer tell Claude to reply with SendMessage when it lacks that tool\n\nWhen SendMessage is missing, the note on an incoming peer message just says to decide whether to respond, not to reply via SendMessage\n\n**Unclear.** Which session setups leave the SendMessage tool unavailable is not stated.\n\n**What**\n\nWhen a message from another Claude session arrives in the middle of a turn, Claude Code adds a note to it. That note normally ends: \"After completing your current task, decide whether\/how to respond (reply via SendMessage to the `from=` address).\"\n\n- A new `sendMessageToolAbsent` flag is set on queued messages from a peer (another Claude session) when the SendMessage tool is not available.\n\n- With the flag set, the note ends with just \" After completing your current task, decide whether\/how to respond.\"\n\n- In that case, messages injected by the host also keep their host-delivery wording.\n\nThe SendMessage tool's own description is unchanged.\n\n**Why**\n\nClaude is no longer told to use a tool it does not have in that session.\n\n- Area: Multi-Session\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}