Multi-Node, Relay & Bridge

Multi-Node Relay

Settings → Account → Connected Machines and the “Run on: [machine ▾]” picker. Every machine signed into the same Sivants account is a first-class peer; 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.

One machine is marked primary (Connected Machines → Set as primary), project authority gives each project one owning machine, prompt numbering is shared across the account, and each run gets an isolated worktree. Keeping each project on one machine is recommended; working the same project from several machines is supported if git is kept clean and pushed.

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

Cross-node project import

Import Project wizard → pick a connected machine. Imports a project from another connected Orbit node instead of requiring a separate clone or manual copy.

Per-machine app header tint

Hidden Dev Tools drawer → Machine Header Tint. Each installation can keep the default header, choose a light-blue identifier, or derive a legible tint from local node identity — a quick visual cue for telling installs apart when several are open at once. The choice is local and does not sync across machines.

Release-by-tag multi-node build intents

Mobile Builds / Dispatch build lanes, and the Ship/Upload modal. Dispatch publishes one annotated release tag and creates durable per-target build intents; each assigned node claims and builds that same tag in a detached worktree, so every release target is built from one immutable source rather than whatever each machine happens to have checked out. Target assignments stay correct across a page refresh.

Coordinated desktop draft publication (Build All)

Project window → Builds / Dispatch → Build All. Records one desktop release version, builds Windows and macOS from that same tag, and joins the verified artifacts into a single, non-clobbering GitHub draft release. Go Live — publishing that draft — always remains a human action.

Node MCP (two-tier MCP routing)

Settings → Account → 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.

Bridge — inter-instance relay

The right-rail Bridge panel. A human-gated message channel between two Claude instances. Every outbound post is a pending draft — its exact text is shown before a separate approval step delivers it (a two-step outbound approval, so drafting and sending are never the same click). Blocked drafts stay visible along with the safety-judge reason that blocked them, and delivered messages retain any judge flag they picked up along the way. On the receiving side, inbound Bridge queue insertion is authorized through receiver-owned execution grants — the receiving instance controls what an inbound message is allowed to queue, not the sender.

MCP tools: relay_channels, relay_poll, relay_post, relay_history, relay_status. Deep dive: context/specs/relay-spec-v1.2.md.