Google quantifies the distraction of code TODO comments for coding agents
Understand this story
The Google Developers Blog published research stating that TODO(bug/...) comments left in codebases distract coding agents. The study, based on distributed tracing across thousands of engineers and hundreds of millions of agent steps, quantified the distraction these comments cause for agents. According to Google, 13% of agent sessions exposed the agent to such TODO references, of which 6% triggered follow-up actions, and 83% of that 6% were not requested by developers.
AI overview based on source reports · Updated 34 min ago
Coverage timeline
Follow the coverage to explore different perspectives.
- Google Developers BlogFeaturedAgent Distraction
The post reports that 13% of agent file-reading sessions expose the agent to inline TODO(bug/...) or FIXME(bug/...) references, and in 6% of encounters the agent takes follow-up action on that bug ID, 83% of which are unprompted by the developer. Cross-referencing these detours against live bug status, it finds 41% chase already-closed or obsolete tickets while 57% involve still-open bugs where the agent expanded scope, and a fixed-effects regression shows unprompted bug detours add 70% more steps, 77% more tokens and 105% more wait time per session. The authors built agents that scan codebases and remove confirmed-obsolete bug references, reporting thousands removed over six months with over 95% acceptance from human reviewers.
Activity for this story
Not enough continuous observations to show a trend yet.