{"version":"2.1.281","anchor":"wording-change-in-the-remote-call-could-not-be-reached-mes","canonical_anchor":"wording-change-in-the-remote-call-could-not-be-reached-mes","heading":"Wording change in the remote-call 'could not be reached' message","tier":"notice","area":"Remote Devices","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/wording-change-in-the-remote-call-could-not-be-reached-mes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Wording change in the remote-call 'could not be reached' message\n\nThe \"could not be reached\" message for remote calls now says Claude may not be running there or may no longer be connected to this session\n\n**What**\n\nSometimes a call cannot reach another machine or session. The message shown in that case used to say \"If its Claude Code is not running or not attached\". It now says \"If Claude is not running on\" followed by the machine's name, then \"or is no longer connected to this session\". It goes on to ask the user to check it.\n\n**Why**\n\nThe new wording names the machine and describes the two likely causes in plainer terms. That makes it clearer what to look at when a remote call fails.\n\n- Area: Remote Devices\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}