{"version":"2.1.224","anchor":"clearer-refusal-when-a-name-matches-a-device-gated-remote-se","canonical_anchor":"clearer-refusal-when-a-name-matches-a-device-gated-remote-se","heading":"Clearer refusal when a name matches a device-gated remote session","tier":"notice","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/clearer-refusal-when-a-name-matches-a-device-gated-remote-se","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Clearer refusal when a name matches a device-gated remote session\n\nMessaging a reply-only remote session now explains why, instead of a generic not-found.\n\n**What**\n\nSending a message to a name that only matches a reply-only remote session now explains that specifically, rather than returning a generic not-found. The text states that the Claude Code Remote send_message connector cannot reach these sessions and that the \"untrusted device\" error it produces is misleading.\n\n**Details**\n\n- When the peer list itself fails to load, the fetch is now marked as failed so the caller hedges instead of flatly refusing.\n- Only reachable when cross-session messaging is active in the session.\n\n**Evidence**\n\n`it cannot reach these device-gated sessions, and its \"untrusted device\" error is misleading`\n\n- Area: Cross-Session Messaging\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}