Skip to content

Multi-Node, Relay & Bridge

Settings → Sivants → Connected Machines and the “Run on: [machine ▾]” picker. Multiple machines as first-class peers on one account; queue a prompt on one machine targeting another, executing remotely and streaming output back, with reconnect reconciliation (a ring buffer plus prompt:sync) and a per-project default execution target.

MCP tool: orbit_list_nodes. Deep dive: context/multi-node-relay-alpha-scope.md.

Settings → Sivants → Connected Machines → MCP Tokens, with the URL node.orbit.sivants.com/mcp-v2. One account-wide MCP URL routes tool calls to any machine via the relay — account-scoped tools need no node param; node-local tools default to the primary node — with individual per-machine URLs as a fallback. All tools accept an optional node parameter.

Deep dive: context/multi-node-relay-alpha-scope.md.

The right-rail Bridge panel. A human-gated message channel between two AI instances — every drafted reply waits in an Outbox until Approve & send; participants are read-only. Part A is a visual preview on mock data; the live relay API is wired in a follow-up.

Deep dive: context/relay-spec-v1.2.md.