A versioned remote tool-routing client with permission forwarding and call reconciliation is newly present in the bundle.
What
A 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.
Details
- Reconciliation outcomes are reported as replayed, still running, host restarted, or not received.
- Permission asks forwarded back include automatic-mode classifier verdicts.
- New telemetry events:
tengu_remote_tool_forward,tengu_remote_tool_targets,tengu_remote_tool_classifierandtengu_remote_tool_serve_hook_held. - Users would see text listing attached machines, plus errors for an unreachable host or a protocol mismatch.
- 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.
Evidence
The attached machine could not be reached through the device bridge right now; the call did not run. Try again shortly.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.