Thorsten Ball says his team pushes to main, no code review
Verification moved from the review queue to signals the agent can read for itself.
Thorsten Ball described how his team ships and the summary is short. No pull requests, no code review, straight to main.
No pull requests, no code review. We push to main.
Our agents read production logs, watch deploys, grant feature flags, and check their own work end to end.
The part that makes it more than a provocation is what replaces review. Ball says their agents read production logs, watch deploys, grant feature flags and check their own work end to end. He posted a walkthrough of the setup and a video version on YouTube.
What is actually being removed
It is easy to read this as discipline being thrown out. The claim in the post is narrower. The human gate before merge is gone, and the checking moved downstream to things the agent can observe directly, which is the deploy, the flag and the log line after the change is live. An agent that can read production logs and watch a deploy is checking the same signal a reviewer would eventually be checking anyway, just later and with more evidence in front of it.
That also explains the feature flag detail. If an agent can grant a flag, a change can land on main and still be off for most users, which gives the push to main a blast radius closer to a branch than to a release.
Fits a pattern in his earlier posts
Ball has been arguing for a while that the verification habits built for humans do not transfer unchanged to agents. He previously said agents do not need unit tests the way humans do, which drew pushback at the time, earlier.
Worth being precise about what this is. It is one team describing its own workflow, not a benchmark and not a result anyone outside that team has reproduced. Ball does not say in the post how large the team is, what they ship, or what happens when the agents get it wrong. The walkthrough and the video are where the mechanics live, and anyone planning to copy this should start there rather than from the headline.
Have the good opinion, not the loud one
One email a day. Under three minutes. What working engineers found out about coding with AI.