# Remote Fleet > Links every computer where you are signed in to AgentsRoom into one view. - Area: Desktop, mobile and web - Plans: All plans - Last checked against the product: 2026-09-24 - Web page: https://agentsroom.dev/docs/remote-fleet ## What it does Links every computer where you are signed in to AgentsRoom into one view. The sidebar shows your local projects and, below them, the projects that live on your other machines, with live presence (online, offline, how many agents are working there). A project that exists only on another machine opens as a remote workspace; an agent of a project you have on both machines can be launched on either. The remote machine spawns the agent locally and streams its terminal back to you over the end-to-end encrypted relay; your code never moves. The same mechanism lets you invite teammates to attach to agents running on your machine. A team run started on another machine (by hand or by a trigger there) shows up as a team box too, with its steps, its counter and the machine it runs on, not as a handful of unrelated agents. Since 1.182.0 the terminals of the bottom bar (dev commands, blank shells, SSH tabs) open on your other machines appear in the project's terminal bar too, and you can follow them from here. Since 1.184.0 you can also close one of those terminals, stop a team run or stop an agent on the other machine without walking to it, from the desktop and from the phone, and a remote session looks like a local one: the bottom bar stays, the tab is colored, and a small machine badge sits at the top right of the pane. ## Where to find it - Sidebar, section **On my other machines**: each project says "On " or " is offline", with "N agents running on ". - Inside a project: the agent list has a **Remote** category ("Runs on ") under the cloud agents, and **Add an agent on another machine**. - Agent context menu: **Run on** > **This computer** or another online machine; **Stop on **. - Inside a project, a team run hosted elsewhere gets its own box after the local team boxes, in both sort modes: the run title, "current / total" steps, the machine name on the right (its tooltip reads "Team run on "), then a cross ("Stop this run on ", or "Dismiss this run on " once it is finished), then the **Relay** or **Team** banner and one row per step. Its consoles hang under the step they play (Team) or in a "Playing " card (Relay). - Project context menu: **Open on **, and **Shared with me** for projects other accounts opened to you. - Terminal bar at the bottom of the project: the tabs of your other online machines come after the local tabs, with the machine's name in small after the tab name. Hovering a remote tab shows a cross ("Close this terminal on "). Clicking the tab opens it in the center pane, laid out exactly like a local terminal: the bare grid, the bottom bar still there, and a small floating badge at the top right reading " · " with a detach icon and a cross. - Phone: the **Remote** action of a project. ## How to use it 1. Sign in with the same account on each machine; they discover each other through the relay, nothing to configure on the router, no VPN, no port to open. 2. Project on both machines: open the project here, pick an agent, **Run on** the other machine (or **Add an agent on another machine**: pick the **Machine**, then the **Role on **). Its row shows "Runs on "; opening it replaces the terminal pane while you keep your local files, changes and terminals. If that same agent also has a live session here, the local one wins: no remote badge, and clicking it opens the console on this computer. 3. Project only there: click it in **On my other machines** ("This project is not on this machine: it opens as a remote workspace"). The remote view shows that machine's agents in a rail, grouped like the local list (**Needs input**, **To review**, **Active**, **Seen**, then **Inactive** below a separator); the rail scrolls and its add-agent button stays reachable at the bottom, its menu opening upwards (since 2026-09-23). 4. **Detach** stops following an agent without stopping it. **Stop** ends it on its machine for good; it is offered on the row and in the menu while the agent runs elsewhere, in place of delete. 5. Team run box: click a step or its console to attach to that console. The cross in the box header stops the run on its machine ("Stop this run on ", after the same "Cancel this team run?" confirmation as a local run; a finished run is dismissed instead). Hand-off and answers still belong to the host: "Hand-off and answers stay on . From here you can open its consoles or stop it." A stalled step or a question the run is waiting on ("The team is waiting for you") is shown with the same banners as a local run, to be answered on the host. 6. Remote terminal tab: click it to attach. What you type goes straight to that shell, so there is no composer and no confirmation. The badge at the top right names the tab and the machine; its detach icon stops following it ("Stop following this terminal. It stays open on .") and its cross closes the terminal on the other machine ("Close this terminal on "), the same way the cross of a local tab does. Your own local tabs stay in the bottom bar while you follow a remote session. Right-click the remote terminal for **Copy** (greyed without a selection) and **Paste**, then **Clear buffer** and **Settings**; there is no **Restart**, since the process lives on the other machine. 7. When the other machine turns a request down you get the reason ("That machine does not have this project any more", "You do not have access to that agent on that machine") instead of a timeout. ## Settings - `relayWsUrl` (global, advanced): the relay the fleet rooms travel through. Leave the default. - No fleet-specific toggle: signing in on a second machine is the setup. ## Agent tools (MCP) None. `projects_list` and the `agents_*` tools act on the machine the agent runs on. ## Providers All providers, no difference. One machine can run Claude agents, another Codex, another Antigravity; they show side by side. ## Mobile Yes: the **Remote** action of a project opens a machines > projects > agents screen and a remote terminal, without switching the paired desktop. Stopping and detaching work the same way there: the header of the remote console offers **Stop** ("Stop this agent on ?", "Its session ends there for good."). A team run of another machine comes as a card inside its project (title, machine, counter, mode banner, steps) with its consoles listed under it; tapping a step opens a console, and the card's cross stops the run ("Cancel this team run?", "The run stops on and its consoles close there."). Hand-off and answers stay on the host, as on the desktop. The host's open terminals are listed after its runs and agents, one row per tab with a **Running** or **Idle** pill when the host reports activity and " · terminal" under the name; tapping one opens the screen "Remote terminal on ", where the keyboard types into that terminal. The row's cross and the screen's **Close** button close the terminal on the host ("Close this terminal on ?", " closes there, and whatever runs in it stops."). Every stop or close from the phone asks for confirmation first. ## Limits - Presence and control travel through the cloud relay even between two machines on the same LAN, so keystrokes take a round trip; there is no direct peer-to-peer path yet. - An offline machine keeps its place in the list, greyed out; its agents cannot be reached until it is back. - A custom uploaded avatar of an agent that exists only on the host does not travel; the row falls back to the role artwork. - Remote agents have their own terminals on the host; the browser, files and changes panels you see are those of the machine you are on. - The relay sees only encrypted blocks and an anonymous room id. - Agents started by a trigger on another machine are never listed here, and are not counted in "N agents running on ": they belong to their trigger's run history on that machine, where **Run history** shows them. A team run a trigger started is the exception: its consoles are announced, so its box shows like any other run. - An agent live on two machines at once is shown and opened locally; the remote copy is not offered a second row. - A remote team run box exists only while its machine is online and answering; the consoles of a silent machine stay listed, greyed, without their box. A step can take about ten seconds to change state on the other screen. - A project another account shared with you never shows its team runs: the box names the team, its steps and the subject of the run, which is not part of an attach grant. The host must run a version that announces its runs; an older one still lists plain agents. - Remote terminal tabs: only online machines are listed, and a tab of a machine that goes silent disappears with it. Database tabs are never listed. A project shared by another account never exposes its terminals (a terminal is a raw shell on the owner's machine, no access grant covers it). The tab cannot be dragged or split from here, the detached terminal window does not show remote tabs, and the host must run 1.182.0 or later (1.184.0 or later to close it or stop a run from afar). If the host closes the tab while you follow it, the pane keeps the last output received. ## Common questions - **Do I need SSH, a VPN or port forwarding?** No. Both machines connect outwards to the relay; nothing is opened inbound. - **Is my code synced between machines?** No. Each machine keeps its own clone and runs its agents on it; only encrypted control messages and output travel. - **How many machines?** As many as you sign in on. - **The other machine says "No answer".** Check that AgentsRoom is open and signed in there ("Sign in on a second computer"). - **Can teammates join?** Yes: invite them into a project and they attach to your agents with per-agent access. See [Project Sharing](https://agentsroom.dev/docs/project-sharing.md). - **I see the agents of a team run from my other computer, but not the team.** Since the run box came in, the host announces its live runs and the agents regroup under them. If they still come as separate rows, the host runs an older version, the run is finished, or the project was shared to you by another account. - **Can I hand off or cancel a remote run from here?** You can stop it: the cross of the run box (desktop) or of the run card (phone) ends it on its machine after a confirmation, and its consoles close there. Handing off and answering an Await question still happen on the machine that runs it. - **Can I see the dev server running on my other Mac?** Yes. Open the project here: its terminal bar lists the tabs open on the other machine (name, then the machine's name), as long as that machine is online. Click one to read its output live and type into it. To close it, use the cross of the tab or of the badge at the top right of the pane: the terminal closes on the other machine, exactly as if you had closed it there. - **A remote agent's terminal is squeezed into a narrow column.** A phone is driving it: the host sized it for the phone screen. The pane shows "The terminal has been resized for the mobile screen." with **Take back control**, which gives it your window's width again (since 2026-09-24, Grok agents included; the other machine needs a version that relays it, and your window may need a restart after an update). - **Can I copy text out of a remote terminal?** Yes: select, then right-click > **Copy**, or the usual copy shortcut. Right-click > **Paste** types the clipboard into the remote shell. - **The remote terminal tab I saw a minute ago is gone.** The other machine went offline, or the tab was closed there. A remote tab is a live session, not something kept for later like an agent. ## Related - [Project Sharing](https://agentsroom.dev/docs/project-sharing.md): the same rooms used to invite other accounts. - [Remote SSH Offload](https://agentsroom.dev/docs/remote-ssh-offload.md): run agents on a bare server over SSH instead. - [Remote Agent Control](https://agentsroom.dev/docs/remote-agent-control.md): the phone as the controller. - [Mobile-Desktop Sync](https://agentsroom.dev/docs/mobile-desktop-sync.md): the encrypted relay both rely on. - [Agent Teams](https://agentsroom.dev/docs/teams.md): the team runs whose box travels between machines. - [Dev Terminals](https://agentsroom.dev/docs/dev-terminals.md): the terminal bar whose tabs travel between machines. - [SSH Connections](https://agentsroom.dev/docs/ssh-connections.md): an SSH tab open on another machine is listed the same way.