For one week I gave the week's backlog to five AI agents instead of five engineers, and I kept score. Not a hackathon toy — the real board, the real repo, the real merge button. Here is the honest tally before I tell you what it means:
23 PRs opened by agents
14 merged
3 reverted within 48h
1 near-miss: an agent "cleaned up" a migration and nearly dropped a staging table
6 still open, waiting on a human decision they couldn't make
That is not a disaster and it is not a miracle. It is the most useful week of data I have collected on where this actually works, so let me be specific instead of vibes.
Five agents, each with a narrow job, wired to the repo and CI:
The rule: no agent could merge. Every PR still landed on me. I wanted to measure the agents, not hand them the keys.
The 14 that merged were almost all the same shape of work:
Notice the pattern. Everything that shipped was work where the hard part was typing, not deciding. When the spec was unambiguous, the agents were faster than my team and they did not get bored on file 27 of 30, which is exactly where humans introduce the typo.
The test agent was the surprise MVP. It wrote the tests we had been "getting to" for six months. It had no ego about it and no better idea to pitch. It just wrote the tests.
The 3 reverts and the near-miss all share a shape too:
That last one is the whole game. An agent that writes both the code and the tests will make them agree with each other, not with reality. This is not a model-quality problem you wait out. It is structural, and it is why the test agent had to be a different agent from the one writing the code.
Here is the part nobody puts in the thread.
I did not save a week of work. I moved it. The bottleneck left "writing the code" and reappeared, larger, in two places:
By Thursday I understood the real trade. Agents didn't replace my engineers. They replaced the fast, low-judgment middle of the work and handed me back a job that is almost entirely spec-writing and judgment — the two things I was worst at making time for.
After the week I did not fire anyone and I did not turn the agents off. I changed what they're pointed at:
The honest headline isn't "AI replaced my dev team." It's: AI deleted the part of the job that felt like work, and left me the part that is the actual work. Whether that's a threat or a gift depends entirely on whether you were adding value in the typing or in the deciding.
I ran this on xenition — the agent platform we build — because "dogfood your own agents on your own backlog" is the only benchmark I trust. The tally above is from one real week; your mileage will move with how well your tickets are written, which turns out to be the whole point.
What's the smallest, most boring task on your board right now? That's the one to hand over first. Tell me in the comments what broke when you did.