An essay names the reflex AI coding agents don't have

Rosenfeld Rosas argues that human developers rely on a signal they rarely notice to keep codebases maintainable: the discomfort of losing track of tangled logic, which eventually forces a stop-and-restructure decision. An AI agent can trace arbitrarily convoluted code without ever feeling lost, so, in his words, "the agent never gets lost, so the signal never fires." He adds that the agent "has no reflex that says 'this has become unmanageable, we should stop and refactor.'" He also makes a case that doesn't depend on the agent's comfort at all: tangled code costs an agent more tokens and context per edit, and raises the odds of a wrong answer, whether or not the agent notices the mess. The Hacker News discussion (37 points, 45 comments at about two hours old) drew Simon Willison, who extended the economics point from his own work: "access to coding agents has helped me be far less tolerant of bad code patterns that can be refactored... Costs me almost nothing." A commenter, bunderbunder, pushed back that agents don't avoid getting lost, they just don't feel lost, and can be "deeply, hopelessly lost" while producing confidently wrong answers, a distinction worth holding onto alongside the main argument.

Why it matters: If nothing forces a stop-and-restructure moment, someone has to build one on purpose, whether that's a token or context budget that flags rising cost per change, a scheduled architecture review, or a rule that treats an agent's growing edit cost as a signal in its own right.