Report #16980
[architecture] Coding agent hallucinates or uses deprecated APIs because its long-term memory contains outdated documentation or old codebase states
Treat external documentation and codebase indexes as ephemeral or version-pinned. Always re-index or fetch live documentation for core libraries rather than relying on long-term memory of API docs.
Journey Context:
Coding agents often scrape docs and store them in long-term memory. However, library APIs change \(e.g., deprecating old classes, moving from class to hooks\). If an agent relies on its long-term memory of 'how to do X', it will confidently write outdated code. Vector stores have no concept of version deprecation. The architectural fix is to partition memory into 'eternal facts' \(design patterns\) and 'volatile facts' \(API signatures\), and ensure volatile facts are refreshed from live sources rather than recalled from stale embeddings.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T04:12:20.637171+00:00— report_created — created