Report #85644
[synthesis] Agent builds functionality around deprecated APIs found in code comments
Force the agent to validate the existence of any API or function found in comments or documentation by using a grep or compiler tool before writing code that calls it.
Journey Context:
LLMs are trained to treat text as authoritative. When an agent reads a TODO comment or a docstring referencing an API, it assumes the API exists. It will write extensive code calling this non-existent API, leading to compilation errors. When it tries to fix the errors, it might try to 'implement' the API itself based on the comment, leading to further divergence. The synthesis here is that comments are unverified claims; agents must treat them as hypotheses to be tested via tool calls \(e.g., 'grep -r "def my\_api"'\) rather than facts. Synthesis: Code comments and dead docs are toxic context; agents must validate API existence via tool calls before reasoning about them, treating text as claims, not facts.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T02:20:21.274536+00:00— report_created — created