One person, many agents, and a phone
How I run many coding agents across a Mac and a rented Linux box from my phone, and the parts you need to build the same.
- Topic
- Systems
- Reading
- 3 min
Agents write most of my code now. Most of my day goes on deciding which of them get to keep going, and I need to do that from anywhere, a phone included, without any agent reaching something it shouldn’t. Here is how the setup works and what it is built from, if you want the same.
Two machines, one private network
Anything that needs a secret stays on the Mac, along with the dev servers and the browser for UI work. A rented Linux server does the rest. It’s a 16-core box on a one-week trial that cost a few euros. It runs headless builders that need no credentials, and it has its own logins, so nothing gets copied over from the Mac.
Both machines sit on a private Tailscale network. The server’s firewall drops all public traffic, so only the tailnet can reach it. Two small pages are served to the tailnet and nowhere else, a report page and the agent board.
flowchart TB
P["Phone<br/>Moshi · RustDesk · browser"] --> T(("Tailscale<br/>private"))
T --> MAC
T --> LIN
subgraph MAC["Mac · holds the secrets"]
I["Steward"] --> S["Lead"]
B1["Builders"]
V["Dev servers<br/>board · reports"]
S ~~~ B1 ~~~ V
end
subgraph LIN["Linux worker · no secrets"]
B2["Headless builders"]
L2["Its own logins<br/>Claude · GitHub"]
B2 ~~~ L2
end
MAC --> G["GitHub<br/>cards · checks · reviews"]
LIN --> G
G --> Q{"One gate"}:::lit
Q -->|proven| D["Dev branch"]
Q -->|needs me| O["Me"]
One session orchestrates
Every agent is a Claude Code session in herdr. herdr is a terminal multiplexer, and it shows whether each session is working, idle, done or blocked, on either machine.
One long-running session never writes product code. It’s the lead, and everything goes through it. It reads the board, starts builders, passes decisions along, merges what is proven and writes a hand-off note for when I come back. A second session, the steward, gathers what needs my attention and reports it to the lead, so it reaches me from one place.
GitHub is the feedback loop
Most of the job is triage. Issues become cards on a GitHub Project with five columns. A card is ready only when it says what done means and how to prove it. A builder claims a card with a lease, works in its own git worktree and opens a pull request.
After that, the builder answers to the checks. It reads CI, tests, linters and review comments, from people and from review bots, and responds before anyone looks. Only work that clears a strict gate merges on its own. Anything that touches production or money comes to me, and so does any action an agent was refused. No other agent retries a refused action.
A skill builds the workstation
I never set up the workstation by hand. One skill installs everything on it: Ghostty and herdr, Hunk for diffs, Lazygit, Neovim, Raycast, Nerd Fonts, Tailscale and Moshi. A second skill sets herdr to a baseline. When I change something live, the change goes into the skill too, so running it again rebuilds the same machine. The setup looks like this site, with Departure Mono on an amber theme. Amber marks one thing only, an agent’s state.
Build your own
- Put the machines on a tailnet and close everything else: Tailscale SSH and Tailscale Serve for pages only you can open. Decide early how agents sign in over SSH, because check mode makes every new session wait for your approval.
- Rent a worker by the week (Hetzner Cloud) and give it its own logins rather than your secrets.
- Run agents in Claude Code inside herdr, one git worktree each.
- Make the board the source of truth: GitHub Projects, driven with the GitHub CLI, and merges held to required status checks.
- Steer from the phone with Moshi for terminals and RustDesk in direct IP mode for the desktop.
Open questions
- How many agents can one person review before the review becomes the bottleneck?
- Which decisions can safely move from “ask me” to the gate, and how would I know when one shouldn’t have?
- Is a second remote worker worth it, or does it just move the waiting somewhere else?