{"version":"2.1.280","anchor":"cross-machine-tool-routing-gets-explicit-reconnect-wait-mess","canonical_anchor":"cross-machine-tool-routing-gets-explicit-reconnect-wait-mess","heading":"Cross-machine tool routing gets explicit reconnect-wait messaging","tier":"notice","area":"Multi-Machine","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/cross-machine-tool-routing-gets-explicit-reconnect-wait-mess","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Cross-machine tool routing gets explicit reconnect-wait messaging\n\nCross-machine tool routing now explains clearly when it's waiting for a machine to reconnect versus giving up\n\n**What**\n\nWhen a tool call needs to run on another machine (for example through Remote Control or cloud sessions) and that machine hasn't reconnected yet after its cloud worker was replaced, Claude Code now shows specific text explaining what's happening. There are distinct messages for:\n\n- the machine attached earlier but hasn't reconnected yet\n\n- the machine did not reconnect and the wait timed out\n\n- no machine at all currently serves the requested tool\n\n**Why**\n\nThis replaces vague or missing feedback with a clear explanation of why a cross-machine tool call is stuck or was refused.\n\n- Area: Multi-Machine\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}