# Orchestrate agents across every machine you own

Link your laptop, a Linux build server and a Windows workstation. Agents on one start threads, open browsers and use simulators on another, and you approve it all from your phone.

- Agents start threads and open browsers on linked machines
- Simulators and emulators on one machine, used from any other
- Continue a thread on another machine, uncommitted changes and all
- Every machine's threads in one window, and in the phone app

## One fleet, many machines

Run ace on your laptop, a Linux build server and a Windows workstation, then link them. Linked machines can use each other: an agent on your laptop can delegate a long test run to the build server, or open a browser on the workstation to check a page there.

Devices travel across the fleet too. An agent on the Linux build server can test your app on the iOS Simulator running on your Mac, and an agent on your laptop can use the Android emulator on your workstation, each with the device approval you'd give locally.

Each machine sets how much other machines may do on it: nothing, read, or read and act. Every thread, wherever it runs, shows in the same window with its live status, you can start a new one on any machine from there, and an approval can be answered on whichever machine you're at. When a machine's run slots are full, delegated work waits in its queue instead of failing.

## Move work to the machine that should do it

Continue on another machine takes a thread's project and branch, uncommitted changes included, to another of your machines and starts a thread there from this one's history. The data goes straight from machine to machine, so you can kick it off from your phone on cellular.

## Your phone and tablet, paired

Sign in to your ace account on iPhone or iPad and every machine on it is there. Or pair a machine through a link or a QR code, for view only or view and act, and for as long as you choose. From it you follow every machine's threads, answer approvals, watch the browser and drive your desktops' simulators. Android is coming soon.

Paired devices follow and steer agents; they don't run them. Your code and your agents stay on your computers.

## Connect the way you already do

Machines and devices connect directly over your local network, or over Tailscale, where ace uses the machine's tailnet name with a valid HTTPS certificate. Away from both, devices signed in to your ace account reach your machines through ace's end-to-end encrypted relay, or through a relay you host yourself. Nothing joins your fleet unless you pair it or sign it in to your account.

## MCP tools

`delegate`, `wait`, `agents_status`, `browser_open`, `sim_list`, `sim_act`, `thread_start`

## Questions

### Can an agent use a simulator on another machine?

Yes. Simulators, emulators and browsers on a linked machine are available to agents on the others, as far as that machine's access setting allows, and you approve each device the same way as locally.

### Can an agent on one computer start work on another?

Yes. Linked machines let agents start threads, delegate to other agents and open browsers on each other, as far as each machine's access setting allows.

### Can I move a thread to another machine?

Yes. Continue on another machine takes the project and branch, uncommitted changes included, and starts a thread there from this one's history.

### How do my devices connect?

Directly over your local network or Tailscale when they can. From anywhere else, through ace's end-to-end encrypted relay once they're signed in to your ace account, or through a relay you host. Devices join only when you pair them or sign them in.

Page: https://acehq.dev/features/fleet/