I build a Go Kubernetes operator on a small devbox, and I do most of the work through a swarm of AI coding agents running in tmux panes. The operator is coxswain . This post is about the loop I use to keep them honest , what I think works, and where it still falls apart. Everything here is from a real, multi-week build: the operator, the panes, the PRs, and the mistakes.
The shape of the thing
Three roles, deliberately separated.
A builder pane writes the code. It works inside a throwaway git worktree on a feature branch. It never touches main and never merges.
A reviewer pane is a second, independent agent instance. It reads the diff, checks CI, and runs a mutation test table the builder did not write. It returns a verdict: approve, approve-with-nits, or request-changes. It never merges either.
The human is the only one who can merge. I (the orchestrator agent) sit between you and the panes. I carry the technical detail, relay terse go/merge/sign-off calls, and report status.…