{"version":"2.1.242","anchor":"groundwork-for-running-tools-on-another-machine-over-the-dev","canonical_anchor":"groundwork-for-running-tools-on-another-machine-over-the-dev","heading":"Groundwork for running tools on another machine over the device bridge","tier":"soon","area":"Remote Tools","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/groundwork-for-running-tools-on-another-machine-over-the-dev","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Groundwork for running tools on another machine over the device bridge\n\nTool calls and Bash can be routed to another machine over a device bridge.\n\n**What**\n\nA new client-side layer can route a tool call, Bash or an attached machine's own MCP tools, to a different machine reached through the device bridge. It negotiates a protocol version, forwards permission prompts back into your session, and reconciles calls that dropped or timed out by asking the host what happened. None of it exists in the previous build.\n\n**Details**\n\n- Reconciliation outcomes are reported as replayed, still running, host restarted, or not received.\n- Permission asks forwarded back include automatic-mode classifier verdicts.\n- New telemetry events: `tengu_remote_tool_forward`, `tengu_remote_tool_targets`, `tengu_remote_tool_classifier` and `tengu_remote_tool_serve_hook_held`.\n- Users would see text listing attached machines, plus errors for an unreachable host or a protocol mismatch.\n- Every entry point is behind the same boolean check: the attached-machines notice is only shown when it passes, the runtime is only loaded when it passes, and each routed call re-checks it and fails with the code `gate_off`. The name of that check and what it defaults to are not resolvable from the build.\n\n**Evidence**\n\n`The attached machine could not be reached through the device bridge right now; the call did not run. Try again shortly.`\n\n- Area: Remote Tools\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 5\/5\n- Present in the build but not switched on"}