How to run Claude Code on multiple machines

Install the Commission hub on one Mac, then add your other machines over SSH: other Macs, Linux servers and Windows PCs. Each machine runs its own Claude Code with its own sign-in, and the hub puts every session in one list, so you can start, follow and approve work on any of them from the Mac app, a browser or your iPhone.

Why use several machines

Claude Code works best where the code and the tools already are. That might be a laptop you carry, a desktop with the big repositories, a Linux server or GPU box that never sleeps, and a Windows PC for Windows builds. Commission doesn't move your code. It runs Claude on each machine and gives you one place to drive all of them.

The hub lives on one Mac that stays on. It reaches your other machines over SSH tunnels, and your phone and browsers reach the hub over your Tailscale network. Each machine's host listens only on its own loopback interface.

Add your machines

Open Machines, choose Add machine and enter its SSH address, or pick a device listed under On your tailnet, not in Commission. You can also run commission machine add you@host on the hub. Commission checks the machine, shows a plan of everything it will install and the host key fingerprint, and asks once. It installs as your user and never needs sudo.

  • Linux: glibc 2.28 or newer, systemd and git. Adding a Linux server to Commission walks through it.
  • Other Macs: Remote Login turned on.
  • Windows: Windows 10 (1903 or newer) or 11 with the OpenSSH server. It works, but setup is still rough.
  • Every machine: Claude Code installed and signed in as the user you SSH in as.

One list for every session

Sessions from every machine appear in one list, each with the machine and folder it runs on. What needs you sits at the top. Spaces let you group machines and folders, such as Work and Personal, and the All tab looks across every space.

Activity shows what needs you and what's running on every machine, with one quick action per row, such as Allow once or Stop. The Machines page shows each machine's state: online, reconnecting, Claude signed out there, or a Mac waiting for someone to log in.

Start on any machine

Choose New session, pick the machine and the folder, and write the prompt. It works the same from the Mac app, a browser or the iPhone, and you can set the permission mode, model and effort before you start. A session can also start from a Linear or Jira issue, in its own git worktree.

One job, several machines

For a bigger job, start a coordinator instead of a session: New session › Coordinate, then say what you want done, like three tickets with a PR each. The coordinator breaks the goal into pieces and starts a session for each one in its own worktree and branch, on the machines Settings › Coordinators allows. It runs side by side what can, and stacks what has to wait.

Its questions, permissions and ship plans come to Needs you, and nothing merges until you tap Merge. The batch bar and the Work tab show where every ticket stands, on the Mac, in a browser and on the phone. How coordination works.

Keep them up to date

When a new version is out, Update all at the top of the Machines page prepares every machine's update at once and tells you how many are ready. Review them, untick any you want to leave, and choose Install all. Failures are listed with Retry. Update all never confirms a machine's first contact or a changed host key for you: those open the machine so you can confirm them there.

commission doctor checks a machine's setup, from Claude Code's version and sign-in to git and Tailscale Serve, and says how to fix what it finds.

When a machine goes away

If a machine drops off the network, work there keeps running and Commission keeps reconnecting. If it stays away for a minute, your iPhone gets a "went offline" notification, once per outage. On the phone you can keep writing to its sessions: messages wait and send in order when it's back.

You can also start a session, move one or run an automation on a machine that's offline. The hub holds the work and runs it when the machine returns, and tells you if the machine refuses it. A machine's Connection section says why it can't be reached: Tailscale offline, a relayed or slow path, or a host that's down.

After a reboot, sessions are still there, and a turn that was cut off continues on its own. Any that can't wait in Activity with Resume. Linux machines start their host at boot. A Mac needs someone to log in first, and Commission tells you which one.

Questions

Does each machine need its own Claude plan?Each machine's Claude Code has to be installed and signed in. It can be the same Claude account on every machine, so usage from all of them counts toward that account's limits. Commission adds no plan of its own and doesn't meter Claude.
What if one machine goes offline?Work on it keeps running, Commission keeps reconnecting, and you get a notification if it stays away for a minute. The other machines carry on as normal.
Does the hub have to be a Mac?Most people run the hub on a Mac, and the Mac app is Mac-only. The installer also sets up a hub on Linux, which you then use from a browser on your tailnet and the iPhone app.
Can my team share one hub?Not yet. Commission is built for one person's machines. Anyone on your tailnet can use your hub, so keep your tailnet to your own devices. Each teammate runs their own hub.
Can one job use several machines?Yes. Start a coordinator with New session › Coordinate and give it a goal, like a list of tickets. It starts a session for each piece on the machines Settings › Coordinators allows, and nothing merges until you approve it.

Bring your machines into one list

Install the hub on your Mac, add your other machines over SSH, and every session is in one place. Commission is free while it's in beta.