The DEV team recently wrote about their "looping factory". The numbers they report: average request time inside Rails fell from about 70 ms to 16 ms, and since they started the loops, 351 of 444 merged pull requests came from autonomous loops.
I do not run anything like that scale. These are notes from a solo builder on what I think transfers, based on the post and on my own work with agent safety.
Idea 1: do not be the clipboard
The post describes a trap: you stop typing code but become "human middleware", pasting context into a terminal and rubber-stamping diffs. The fix is a loop that runs without you for routine work.
Even at small scale this applies. If you paste the same context into an agent three times a week, that is a loop waiting to be written.
Idea 2: loops need live data, not guesses
Per the post, their first loop read code and guessed at bottlenecks, with weak results. It improved once agents saw real telemetry before touching a file. For a solo project the version is smaller: give the agent your real error log or benchmark output, not "make it faster".
Idea 3: tests are the contract
When code is cheap to rewrite, the durable part is what surrounds it: schemas, contracts, tests. A loop is only as safe as the tests that judge its output. On my own library I used a mutation check (42 deliberate bugs, all caught) because green tests that cannot fail are worthless.
Where I would still keep a human
A perf PR can be reverted. Some actions cannot: deleting data, sending email, spending money. For those I would not let a loop decide.
That is the problem my library mcp-safe-actions solves for MCP tools: a destructive tool does nothing until a human approves, and the model cannot approve itself.
Rule of thumb: loop the reversible, gate the irreversible.
What I do not know
- I have not run loops at their scale, so I cannot say how well this holds up there.
- Cost, flaky CI and model quota are real issues; the post covers some of them.
- I am drawing on their write-up only; read it for the actual setup.
Question
Which task in your week would you hand to a loop first, and which one would you never?
Top comments (0)