Messaging a reply-only remote session now explains why, instead of a generic not-found.
What's wrong with this entry?
Sending 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.
- When the peer list itself fails to load, the fetch is now marked as failed so the caller hedges instead of flatly refusing.
- Only reachable when cross-session messaging is active in the session.
it cannot reach these device-gated sessions, and its "untrusted device" error is misleading
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Messages injected by a host are classified separately from peer messages
Both mention cross
-
v2.1.234
Cross-session control requests check ids more carefully
Both mention cross
-
v2.1.234
Notice acks now wait for the record to persist
Both mention cross