Multi-Node Relay
Multi-node turns Orbit from a single-machine tool into a small distributed system. Several machines each run Orbit, register as peers on one account, and become targets you can send work to — so a Windows PC and a Mac can be driven from the same interface, with each running the prompts it’s suited for.
Machines as peers
Section titled “Machines as peers”Each machine is a first-class node on your account. From Settings → Sivants → Connected Machines, a “Run on: [machine ▾]” picker lets you queue a prompt on one machine that targets another; the prompt executes remotely and streams its output back to you. If a connection drops mid-run, Orbit reconciles on reconnect using a ring buffer and a prompt:sync step, so you don’t lose the output. Each project can carry a default execution target.
Two-tier MCP routing
Section titled “Two-tier MCP routing”One account-wide MCP URL routes tool calls to any machine through the relay. Account-scoped tools need no node parameter; node-local tools default to your primary node but accept an optional node parameter to target a specific machine. Per-machine MCP URLs remain available as a fallback, and you manage the tokens under Connected Machines → MCP Tokens.
Bridge
Section titled “Bridge”Bridge is a related idea at the instance level: a human-gated message channel between two AI instances, where every drafted reply waits in an Outbox until you Approve & send and participants are read-only. It ships as a visual preview on mock data, with the live relay wired in a follow-up.