A developer on r/ClaudeCode ran an audit on one project and found the same work built twice, over and over:
2 cost-query APIs differing only by case —
LlmCostQueryAPIandLLMCostQueryAPI1 command API defined twice
2 copies of the API contract itself
Code review passed all of it. Not because reviewers were lazy — because a duplicate is invisible to the diff by construction. Review shows you what changed in this pull request. The first copy lives in another file, another week, another agent session. It is never on the screen, so it is never questioned.
The cure runs at write time, in 45 milliseconds
Their fix is a hook, not a meeting. After every Write or Edit, the hook looks each new function, class, route and table up in a generated index of everything the project already owns — ignoring case and word order. On a match, it names the owner and asks the agent to extend that instead.
It never blocks. It just makes the invisible visible at the one moment it can still be cheap.
The first version grepped the whole repo on every write: 6.1 seconds , past the hook's 2-second timeout — so it said nothing, silently. The index lookup takes about 45 milliseconds. A guardrail that times out is not a guardrail. It is a rumour of one.
The pattern underneath
Agents do not check what exists before building. They build. Every control you actually trust has to live where the work happens:
Review cannot see it → index what you own
The check is too slow → it will be skipped or time out silent
The rule is in a doc → the agent will not read it at the moment it matters
My agents work the 3AM shift so no human has to. The hooks work it with them — naming what already exists before they build it again.
What has your agent rebuilt this month that was already sitting in your repo?
Disclaimer
This post describes my personal experience with my own systems and accounts, in my own words. It is a first-person account of what I observed and what I do in my own work — not a statement of any company’s intentions, policies, or internal decisions. Where I do not know something, the post says so.
I am not affiliated with, endorsed by, or speaking for any company, product, or vendor named in this post. All product and company names are trademarks of their respective owners and are mentioned only to describe the experience accurately.
Any error messages, documentation excerpts, or figures quoted here are reproduced from my own records or from the public sources linked in the post, believed accurate at the time of writing. Product behavior changes over time; verify against current official documentation before relying on any detail.
Nothing in this post is professional, financial, legal, or security advice for your specific situation. Examples are illustrative — validate in your own environment before running anything in production.
Corrections are welcome. If any company named here publishes an official statement, or if any detail is wrong, I will update this post and note the correction. The goal is an accurate public record, not a verdict.
© 2026 Honey Kiran. All rights reserved.
Honey Kiran · DevOps & Platform Engineering
AI agents transforming DevOps, infra, platform, security & SRE. The shift nobody works anymore: deep dives, 3AM Files, and OpsBites.
Examples are illustrative — validate in your own environment before running in production.

Top comments (0)