Compare · Cloud coding agents
Whose computer is your code on while the agent works?
The answer decides which toolchain runs, which local state the agent can see, and who holds a copy of the repository. A cloud runner works on a copy, on infrastructure it manages. With PRCHD, the agent works in your real checkout, on your computer, with the tools already set up there.
Cloud runner
PRCHD
Every row comes back to where the code sits.
| Cloud agent runner | PRCHD | |
|---|---|---|
| Where the working copy lives | A provider-managed environment | Your real checkout, on your computer |
| Whose toolchain runs | A configured remote environment | The one already set up on your computer |
| Local uncommitted state | Present only if uploaded | Already there, beside the work |
| Which agent runs | The agent the service configured | Your installed Claude Code, Codex, or Grok CLI |
| When you close the phone | The task keeps running remotely | The task keeps running on your computer |
| Where you review | A browser or the product’s UI | Phone views rendered by your computer |
Where cloud runners are better
Zero local setup is a real advantage.
- Start from a device, with no computer to prepare first
- Work on a repository you have never checked out
- Keep running when your own computer is unavailable
- Run more at once than one computer’s CPU and memory allow
Handing work to a teammate belongs on both sides now. A team host runs on a computer the team shares and binds a Slack channel to a project, so anyone already in that channel can pick up the thread — and the branch, the transcript, and the record stay on the team’s own computer.How a team host works →
What your own computer gives you
The environment you actually debug.
- Your installed toolchain and exact versions
- Your local services and configuration
- Your existing uncommitted state
- Your agent CLI, provider account, and rate limits
- The working copy stays on your computer — the only place PRCHD needs it
Where PRCHD sits
A remote control, not a place to run the agent.
Your agent sessions stay on your computer. PRCHD gives them a phone-sized surface for direction, diff review, commands, terminals, and git. Your phone reaches your computer directly over your tailnet; the public PRCHD service sits outside that path and never receives source code.
Keep the code where the toolchain is.
Install the host on your computer, then pair your phone over Tailscale.