{"version":"2.1.283","anchor":"bridge-not-connected-failures-are-now-tagged-as-the-machin","canonical_anchor":"bridge-not-connected-failures-are-now-tagged-as-the-machin","heading":"A disconnected bridge is now reported as the machine not answering","tier":"internal","area":"Remote Tools","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/bridge-not-connected-failures-are-now-tagged-as-the-machin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### A disconnected bridge is now reported as the machine not answering\n\nWhen the bridge is not connected, the failure is now flagged as the machine not answering, the same way as a failed liveness check\n\n**Unclear.** It is not clear what part of Claude Code reads the new flag, or whether it changes how these failures are shown or retried.\n\n**What**\n\nWhen Claude Code tries to reach a machine through its bridge (the connection used to talk to that machine) and the bridge is not connected, the result is still reported as unreachable. It now also carries a flag saying the machine is not answering.\n\nThat puts it in the same group as a failed liveness check, which is a quick test of whether the machine is still responding. In that case nothing was sent to the machine.\n\n**Why**\n\nIn practice, a dropped bridge and a machine that fails a liveness check are now reported as the same kind of problem.\n\n- Area: Remote Tools\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}