Skip to content
Orbit Docs

Set Up Multi-Node

Published Updated

Multi-node lets one account drive several machines — for example, a Windows PC for web work and a Mac for iOS builds.

Steps

Section titled “Steps”
  1. On each machine, open Settings → Account → Connected Machines.
  2. Sign into the same Sivants account on each machine — every signed-in machine appears here automatically as a peer.
  3. To run work on a specific machine, use the “Run on: [machine ▾]” picker when queuing a prompt. The prompt executes there and streams output back.
  4. Set a default execution target per project so routine work goes to the right machine automatically.
  5. Optionally mark one machine primary from Connected Machines → Set as primary — node-local MCP tool calls route there by default.

Keep each project on one machine when you can; working the same project from several machines is supported, but only if you keep git clean and pushed between sessions — project authority still assigns each project one owning machine, and prompt numbers are shared across the account.

Routing MCP tool calls

Section titled “Routing MCP tool calls”

Use the account-wide MCP URL and tool calls route 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. Manage tokens under Connected Machines → MCP Tokens; per-machine URLs remain as a fallback.

Section titled “Related”