TermLink
Open app
← All posts
5 min read

Running several Claude Code agents at once, across machines

A laptop, a workstation, and a box that exists only to run agents. Keeping three or ten Claude Code sessions in one list — and telling at a glance which one is waiting on you.

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.

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.

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 Free plan caps a viewing session at two hours at a time — the agent keeps running, you just reconnect. Pro removes the cap and lifts the limit on registered machines.
  • 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.

Start with one machine and add the rest later: getting started with TermLink.