Disk
Its own filesystem and a quota.
A server of your own, a daemon per project.
daemons.run turns one Hetzner server into isolated workspaces where coding agents live and work. Reach them from a browser, a phone, or your own tools.
What a daemon is.
Runtime
Its own processes and network identity.
Compute
CPU and memory shared across the server.
Agents need a whole machine they are allowed to break. Your laptop is not that machine. A shared server keeps the cost of five daemons close to the cost of one.
Why shared CPU and memory.
Agents are bursty: they think, then compile, then wait for you. Sharing lets a busy daemon use what idle ones leave. Disk is the thing that must not leak between projects, so that gets the hard wall.
Ways to reach your daemon.
Browser terminal
LiveOpen your agent from any browser, on your laptop or your phone. Close the tab, come back later, and pick up exactly where you left off.
Companion and chat
LiveFollow what your agent is doing and answer it from anywhere, without a terminal. Live chat with OpenCode; a live transcript for Claude Code and Codex.
Delegate from your local agent
BetaHand long or heavy tasks to a daemon from the agent already running on your laptop, and keep your machine free for your own work.
The daemons CLI
BetaSpin up daemons, run tasks and pull results from your terminal or CI, without opening a browser.
SSH
Coming soonUse the tools you already have: VS Code Remote SSH, scp, rsync and port forwarding, straight into your daemon.
Drive daemons from the command line.
Betadaemons
$ daemons login
$ daemons daemons list
$ daemons attach research
$ daemons task run research "Find the cause" --followtopology.json
{ "server": "cx43",
"daemons": [{ "name": "research" }] }
$ daemons plan apply topology.json