A lot of conversations about AI coding agents focus on obvious failures: hallucinated APIs, broken tests, bad assumptions, or code that simply does not run.
But I think one of the bigger problems is quieter: the agent completes the task, the app still works, the tests may even pass, but the repo is now more disordered than it was before.
That is repo drift. Or, more specifically: repo entropy.
It shows up as bloated files, duplicate helpers, cosmetic modularity, stale scaffolding, local patches that solve one surface while creating inconsistency somewhere else, and custom under-the-hood code that works around the framework instead of working with it.
This is one of the biggest sources of drift I see in AI-assisted development.
