{"version":"2.1.286","anchor":"cross-machine-messaging-unavailable-message","canonical_anchor":"cross-machine-messaging-unavailable-message","heading":"Clearer message when messaging sessions on other machines is blocked","tier":"notice","area":"SendMessage","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/cross-machine-messaging-unavailable-message","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Clearer message when messaging sessions on other machines is blocked\n\nWhen sending messages to sessions on another machine is blocked, Claude Code now gives the reason and says local sessions still work\n\n**Unclear.** What causes cross-machine messaging to be blocked is not stated.\n\n**What**\n\nClaude Code sessions can send messages to one another. When messaging sessions on another machine is blocked, Claude Code now says \"Cross-machine messaging is unavailable:\" followed by the reason, and adds \"Messages to sessions on this machine still work.\" A block caused by a data residency rule, which limits where data may go, gets its own separate message.\n\n**Why**\n\nYou get an explicit reason when messages to another machine cannot be sent, and know that sessions on your own machine are unaffected.\n\n- Area: SendMessage\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}