Run coding agents on a private server so the laptop can close

A developer has spent four months running Codex orchestrators and worktree subagents on a 12 euro Hetzner server, fed from Linear, with Hermes Agent on Telegram looking after the box.

Done withCodexHermes AgentinLinearTelegramGitHub· Nov 17, 2026

What they did

Kaliada wanted coding agents that keep working after the laptop is shut, so rented a Hetzner CX33 (4 vCPUs, 8 GB RAM, about 12 euros a month), put it behind Tailscale, and ran the Orca server on it so the same agent sessions open from any device. Work starts as a Linear task with screenshots, or as an OpenSpec spec for bigger changes. An architect agent, mostly Codex, reads the task, splits it, and hands pieces to up to five subagents, each in its own Git worktree. Subagents move and comment on Linear tickets, open pull requests that a reviewer agent can bounce, and merges trigger CI gates. Hermes Agent runs on the same machine; Kaliada chats with it on Telegram to install tools, fix the server, create new projects from a template repo on GitHub, and send a daily AI news digest.

How it went

Kaliada has run it for four months, keeping one to five projects going at once; beyond that the person, not the server, becomes the bottleneck. One test pushed to more than 30 agents at the same time on a .NET and PostgreSQL project, the 8 GB of RAM ran out and everything died; one fresh agent then went through the abandoned worktrees and merged them back into a working state. Setup for each project is still partly manual, and the author says the code arrives faster than it can be reviewed.

Worth knowing

Budget memory per agent, especially when projects need Docker. Worktrees and containers do not stop an agent from touching the host, so permissions still matter, and the workflow is not private just because the server is: Linear, Telegram, GitHub and the model providers are all outside services. Switching between models when one hits a limit is still rough.

Try it

With Codex· 5 parts to fill in

You are the architect for [project] on my server. Read the open tasks in [Linear project link or spec file]. For each task, plan the change, then split it into at most [number] subtasks and give each to a subagent working in its own Git worktree on its own branch. Have each subagent comment its progress on the task, open a pull request, and run [the project's tests and linters]. Keep at most [number] agents running at once so the server does not run out of memory. Do not merge anything yourself: stop when every pull request is open and green, and give me a list to review.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related