Run agents on your other machines

Fleet shows your Beam fleet in n10 Desktop: the machines you own, joined under one passkey. Once the fleet has a second machine, you can launch worktrees, agents and terminals on it from this one.

Fleet is a section at the bottom of the sidebar, below your repositories. Before you open a repository, it sits beside the repository picker. It starts expanded; click its header to collapse it, and the header then shows the fleet's state. The machine count in the status bar, and Show Fleet in Settings → Machines, bring it back into view. Setting up, pairing and adding a machine happen inside the section. Its header's … menu, also on a right-click, shows the fleet fingerprint and holds Reset fleet….

Your passkey provider must support the WebAuthn PRF extension; Fleet's Passkey compatibility note lists what vendors document.

Create a fleet

On your first machine, choose Create a fleet in the Fleet section. Name this machine and the fleet, or keep the defaults, and choose Create fleet. Two passkey prompts follow:

1. Create your fleet passkey saves a passkey for beam.n10.is.
2. Authorize this machine uses it to sign this machine into the fleet.

For each, choose Open in browser or Copy link, or scan the QR code with your phone. Check that the browser page shows the same machine name and fingerprint as n10 before you approve. Each link expires after five minutes.

Add a machine

• Another machine with n10 Desktop: in its Fleet section, choose Join an existing fleet, name the machine and choose Join fleet. Approve Authorize this machine with the fleet's existing passkey; don't create a new one.

• A headless machine: install Beam and join from its terminal. It draws a QR code to scan with your phone.

  npm install -g @notaharness/beam
  beam join --label buildbox

After joining, compare the fleet fingerprint on the new machine with the one in the Fleet header's … menu on a machine already in the fleet (beam status on a headless one). In n10, answer Matches or Doesn't match. If they don't match, the machine joined a different fleet: choose Reset fleet… and join again.

Launch on another machine

With a second machine in the fleet, the launch dialog and the new-terminal dialog get a Machine selector, and the command palette gets Open terminal on buildbox for each connected machine.

The worktree, the tmux session and the agent all run on the machine you pick, for a new branch or an existing one, and the terminal shows up in n10 like any other. That machine needs:

• a clone of the repository at the same path as on this machine;
• tmux 3.2 or newer;
• the agent's CLI, installed and signed in.

If the connection drops, the pane shows that it is reconnecting. The agent keeps running on the other machine.

The machine list

Fleet lists every machine with its fingerprint and state: connected directly or through a relay, offline, or revoked. Each machine's menu renames it on this machine, sets what it may do on this machine, and revokes it.

A machine's access decides what it may open here: Shells and messages, the default, Messages only, or No access.

Orchestra players on other machines

An Orchestra player started on another machine with --machine reports back over Beam. While n10 Desktop runs, it delivers those reports to the orchestrator on this machine: a Claude session, or an agent session n10 started, and only from machines allowed Shells and messages. n10 doesn't deliver to a Codex orchestrator; run Orchestra's relay.sh for that, as its README describes.

Revoke a machine, or start over

Choose Revoke buildbox… from a machine's menu. A dialog opens; approve its one passkey prompt. The fleet stops accepting that machine for good. Revoking doesn't erase anything on it.

Reset fleet…, in the Fleet header's … menu, takes this machine out of its fleet after you type reset to confirm, so you can create or join one again. It doesn't affect other machines or the passkey. If you lose the passkey, reset every machine and build the fleet again.

Limitations

• On another machine, n10 can launch an agent on a new or existing branch, but can't yet check out a branch on its own, remove a worktree or rebase.
• Plans go to an agent on this machine only; see plans.
• The terminal UI has no Fleet.
• Headless machines must run macOS or Linux.