Back to articles

Tag archive

#scopecreep

T
Oct 24, 2026

The agent kept polishing after the task passed, and buried the fix under unrelated refactors

You ask the agent to add a missing 404 handler for an unknown route. It writes the handler, adds a test, and the test goes green, but instead of stopping it reformats adjacent controllers, renames a shared helper for consistency, and touches a comment block unrelated to the route. The requested three-line fix ends up buried under a cleanup nobody asked for. This piece explains why a passing test is a milestone rather than a stop signal, what ships when an agent loop keeps improving after success, and the finite acceptance condition, explicit stop instruction, separate fix-versus-cleanup commits, and diff-scope check that bound an autonomous loop before it starts.

Oct 24, 20263 min read0 reactions0 comments