Why Coding Agents Shouldn't Close Their Own Tickets

Resumo

Pixel shares a DEV Community article arguing that coding agents can claim a ticket is finished and provide evidence, but should not decide to close it. The post compares this separation to pull request reviews and explains why independent verification matters for trustworthy software workflows.

DEV Community

Your Coding Agent Shouldn't Be Able to Close Its Own Ticket

Would you let a developer approve their own pull request? GitHub won't. Open a review on your own pull request and approving it simply isn't an option. And nobody takes that as an insult to developers. It's just how review works: the person who wrote the change isn't the person who says it's good. So why do so many of us let coding agents close their own tickets? 🤔 You know how it goes. You hand the agent a ticket. It works away for a while. Then: Implemented and verified. ✅ And the ticket moves to Done. Sometimes because the agent moved it. Sometimes because you did, on its say-so, at six on a Friday evening. 😅 Either way, the only evidence the work is finished is the word of the thing that did the work. I think that's backwards. In this post I'll argue that an agent should be able to claim a ticket is done, with evidence, but never decide it. Then I'll show what that split looks like in practice. Full disclosure: I make Arbituro, a work tracker built on exactly this split. The argument holds whatever tracker you use, and the Arbituro bit is near the end. 🎯 "Done" Is the Agent's Finish Line Here's the thing about a coding agent: it's trying to finish. That's not a flaw, it's the job. Every step it takes heads towards the moment it can say "done" and stop. So for an agent, "done" isn't just a status. It's the finish line. And if the agent also gets to decide where the finish line is, you get exactly the incentive you'd expect. 🙃 None of this needs bad intent. It's what happens whenever the one being measured also does the measuring. We worked that out for people a long time ago. It's why code review exists, why auditors aren't the accountants, and why your own approval on your own pull request doesn't count. 🎭 Confidence Isn't Evidence The second problem: an agent reports success in the same cheerful tone whether it succeeded or not. If you've worked with one for a while, you've probably seen some version of these: the tests pass... because the agent changed the test; "works on mobile", when nothing was ever opened on a phone; the happy path is fixed, and the ticket was about the edge case. Every one of them arrives as "Implemented and verified. ✅" The sentence is identical. Only the evidence would tell them apart, and the sentence has none. ✂️ Split the Claim from the Decision So here's the fix, and it's simple: two different actors, two different verbs. The agent claims. When it believes a criterion is met, it says so, with what it checked: the command it ran, the page it opened, what it saw. Someone else decides. A CI check, for anything a machine can verify. A named person, for anything that needs judgement. That's the whole idea. The agent keeps all of its speed. It writes the code, opens the pull request, runs the tests and makes its case. It just doesn't mark its own work. ✍️ Here's a claim from Arbituro's demo workspace. The criterion is "Sam is happy with the wording on the account page", and the agent wrote: Rendered the account page on the preview with a test subscription: "Add a cold brew four-pack to this delivery, $19.95" sits under Next delivery, and the confirmation reads "Added. It comes with your coffee on Tuesday." Sam can decide that in one press. Met, or Not met with a reason. Either way it's Sam's call, and it's on the record. Notice what the claim doesn't do: it doesn't say the wording is good. It can't. Only Sam knows whether that's what Sam wanted. 💬 ⚖️ Checks Decide What They Can, People Decide the Rest This split doesn't mean a human clicks through every ticket. Most criteria on a code change can be decided by CI: "Checkout refuses a postcode outside the delivery area" is decided by the checkout check. "Every existing billing test still passes" is decided by the test check. When the check passes on the pull request's latest commit, the criterion is met. When it fails, it isn't. Nobody presses anything. 🤖 People are for the rest: wording, design, whether the change solves the customer's pro...
Why Coding Agents Shouldn't Close Their Own Tickets
Powered by Readybot.io

As últimas novidades de Pixel

Incident Response: Look Beyond the Red Alert

Pixel’s DEV Community announcement explores how teams can fixate on one failing service while overlooking the real cause of an outage, such as a full …

Sach: AI Fact-Checks WhatsApp Forwards in India

Pixel’s announcement introduces Sach, a tool that checks forwarded messages in English, Hindi, Telugu, and 14 other Indian languages against official sources. It gives cited …

Java 25 Removes SecurityManager: What to Fix

Pixel’s announcement explains how Java 24’s JEP 486 permanently disabled the SecurityManager, breaking test workarounds that intercept System.exit. It recommends returning exit codes or throwing …