My agent opened 229 PRs to its own repo in two weeks. It isn't allowed to merge any of them.

I work factory shifts and build software on the side. For the last couple of months my main project has mostly been building itself.

Diaktoros is a plugin for Hermes Agent that keeps a GitHub repo moving while I'm away. One agent reviews PRs. A different agent, on a different GitHub account, fixes what the reviewer finds. New issues get triaged and the small ones fixed. Red CI goes to the fixer before the reviewer wastes a review on it.

Between Oct 26 and Nov 9:

  • 328 PRs merged
  • 229 of them written by the fixer agent
  • 327 of the 328 reviewed by the reviewer agent
  • 264 of 439 new issues filed by the loop itself

I merged every one of them. The loop can't.

Why the rules matter more than the model

Agents can open PRs faster than anyone can review them, and an agent that reviews and merges its own work isn't a teammate, it's a liability. So the parts that make decisions aren't a model. They're plain Python:

  • Every PR gets 3 review verdicts. At the cap it stops and goes to an adjudicator agent or to me.
  • Reviewer and fixer are separate accounts, so whoever writes a fix never reviews it. No seat can merge.
  • Every agent turn runs in a bubblewrap sandbox with no GitHub token, no model key and no network. The host makes each GitHub write and rechecks the PR first.
  • Every turn is logged. hermes dk explain tells you why a PR is stuck and what has to happen next.

One PR, start to finish

PR #1988: the fixer picked up a labeled bug. CI went red on a leaked file handle, and the fixer repaired it before review. The reviewer requested changes twice, each finding cited to a line; the fixer answered every one. The third request hit the cap, so the adjudicator checked each finding against the code and ruled the last one was a gap in the review's evidence, not a bug. Then I merged it.

https://github.com/coe0718/diaktoros/pull/1988

The honest part

Setup is heavy right now: Linux with bubblewrap, a gateway reachable over HTTPS, and separate GitHub accounts (or GitHub Apps) for each role. That's deliberate, for safety, but it's a lot. If you maintain a repo that's drowning in PRs and want to try it, I'll help you set it up myself. Open an issue or message me.

Repo: https://github.com/coe0718/diaktoros
Site: https://coe0718.github.io/diaktoros/