{"version":"2.1.283","anchor":"tool-calls-to-a-remote-machine-check-it-is-alive-before-forw","canonical_anchor":"tool-calls-to-a-remote-machine-check-it-is-alive-before-forw","heading":"Directory sync checks the remote machine is alive before forwarding a command","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/tool-calls-to-a-remote-machine-check-it-is-alive-before-forw","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Directory sync checks the remote machine is alive before forwarding a command\n\nBefore forwarding a command, directory sync now checks the machine is still reachable and fails fast, blaming the machine, if it is away\n\n**Unclear.** It is not clear which setups this check runs in, since it depends on the remote machine's version and on sync support that was not traced.\n\n**What**\n\nWhen a session uses directory sync (keeping files in step with another machine, such as your own computer), commands are forwarded to that machine. Before forwarding, Claude Code can now check that the machine is still there.\n\n- The check calls the transport's `checkLive` when the sync engine supports `pushPoint`.\n\n- If the machine is offline, or has been silent too long and misses the probe, it is marked away, the outcome is `away`, and the call fails without sending anything.\n\n- The error says the machine did not answer a liveness check and that nothing was sent. The failure is attributed to the machine (\"machine\") rather than \"this_side\", and recorded with clearance `machine_away`.\n\n- Before, the command went straight to waiting for in-flight syncs and forwarding.\n\n**Why**\n\nCommands no longer hang against a machine that has gone away, such as a laptop that was closed, and the error makes clear the problem is on that machine's side.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}