Running multiple Claude Code agents at once, across machines

One agent is a tool. Three agents is a management problem.

The moment you are running Claude Code in more than one place — a refactor on the workstation, a test suite on the laptop, something long and boring on a server that exists only to run agents — the hard part stops being can I reach it and becomes which one needs me right now.

This is what that looks like in practice. For the mechanics of it, see managing multiple Claude Code sessions.

Every session in one list

Register as many machines as you like. Run termlink host on each, and every one of them shows up under your Google account, in a single list in the web client.

Switch between them the way you switch between chats. Whether the sessions live on one machine or ten makes no difference to the list.

A MacBook, a Windows workstation and a Linux agent box each running Claude Code, relayed into one TermLink list showing which session is running, waiting, and done — Three machines, three agents, one list — and the status is readable without opening any of them.

The line that does the work

Each card in that list shows the agent's most recent message on that session. One line, per machine:

● macbook        ● Running the test suite…
● workstation    ● Do you want to run this command?
● agent-box      ● Done — 14 files changed, tests passing

That is the whole triage surface, and it is enough. Read three lines and you know that the laptop is busy, the workstation is blocked on a question, and the server finished while you were away. You go to the one that is waiting.

Without it you would be opening three tabs and reading three screens to learn the same thing.

Set the ones you trust free

Turn Auto-Yes on for the sessions whose work you already accept — the test run, the contained refactor — and those agents stop coming back to you for permission at all. Leave it off on the one that is doing something you want to see first.

Now the list sorts itself. The Auto-Yes sessions grind away without you; the ones that surface a question are the ones actually asking for a human.

Machines that only run agents

A headless box is the natural home for a long agent job, and it is exactly the machine that remote desktop tools cannot help you with — there is no desktop session to stream. TermLink does not need one. termlink host on the server, claude in the terminal, and you check on it from your phone like any other session.

The host dials out, so the box can sit behind NAT with no port open and nothing listening.

What to expect

The cap is on active sessions, not on viewers: Free runs two at a time and Pro runs eight, so a larger fleet needs Pro. Either way you can watch from as many browsers and phones as you like.
Every session within the cap streams live, with no session time limit and no reconnect wait — on Free as well as Pro. Sessions are the only thing the plans differ on.
There are no notifications yet. Nothing pings you when an agent finishes; you glance at the list. For a fleet of agents that is usually the faster habit anyway.
The termlink host process has to stay running on each machine. TermLink is not a daemon — see TermLink vs SSH, tmux, and remote desktop.

Frequently asked questions

Can I run multiple Claude Code agents at the same time?

Yes. They are separate terminal sessions, so nothing stops you running several — on one machine or spread across many. The limit that matters is your own attention, which is what the one-line-per-machine list is for.

How many can I run at once with TermLink?

Two concurrent sessions on the free plan, eight on Pro. The cap counts sessions, not machines you have registered and not people watching — pricing has the detail.

Can agents run on the same machine?

Yes. In practice people split by repository rather than by machine: one agent per working tree, wherever that tree lives. Two agents editing the same files is a problem regardless of what is relaying the terminal.

Do I have to keep the browser open?

No. Each session lives in a terminal on its own machine, so closing the tab does not interrupt any of them. Reconnect and each terminal is repainted as its agent left it.

Can I mix Claude Code with other agents?

Yes. It is a real terminal, so Codex CLI and Cursor Agent run alongside Claude Code — Auto-Yes reads each one's own approval prompt. Claude Code is the one we support most closely. See a session manager for AI coding agents.

Will anything tell me when an agent needs me?

No — there is no push, email, or browser notification today. What you get is the list and the latest-message line on each card. Be clear-eyed about that: it is a glance, not an alert.

Start with one machine and add the rest later: getting started with TermLink. For the mechanics, see managing multiple Claude Code sessions.