{"version":"2.1.283","anchor":"bridge-not-connected-failures-now-marked-machinenotansweri","canonical_anchor":"bridge-not-connected-failures-now-marked-machinenotansweri","heading":"Unreachable-machine errors now note when the machine is not answering","tier":"internal","area":"Remote Tools","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/bridge-not-connected-failures-now-marked-machinenotansweri","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Unreachable-machine errors now note when the machine is not answering\n\nWhen a call to a connected machine fails because it is not connected, the error now also records that the machine is not answering\n\n**Unclear.** Where the new marker is read and what message it produces is not clear.\n\n**What**\n\nWhen Claude Code calls a connected machine and the call fails because that machine is not connected, the resulting \"unreachable\" error now also carries a marker saying the machine is not answering.\n\n**Why**\n\nThis may allow a clearer message when a paired device is offline.\n\n- Area: Remote Tools\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}