codex
gofer: run Claude Code and Codex as reviewable jobs on your own machines
With three or four Claude Code and Codex sessions open across two computers and a container, I kept losing track of simple things. Which session is waiting for me? What did the agent I asked to fix a test change, and did it run the tests? The job I handed out last night: did it finish, get stuck, or crash an hour in? And when Iโm away from my desk, can I check from my phone and approve something?
gofer is the tool I wrote for that. In one line: your agents, your machines, one control plane. It runs Claude Code, Codex, ACP agents or plain commands as tracked, reviewable jobs on every machine you own, with no cloud in between and no inbound ports to open on the workers.
The basics up front: gofer is MIT licensed, a single Go binary with a web console built in. The current version is v0.199. It is still 0.x, it ships often, and interfaces may change; the CHANGELOG is the source of truth. Here is what it does.
