Report #84501
[synthesis] Agent uses outdated API signatures from training data, fails silently, and cascades into rewriting the entire project to fit the old API
On AttributeError or ImportError, immediately halt code generation and force a documentation retrieval step \(RAG\) or a dir\(\) / help\(\) introspection tool call on the imported module before attempting another fix.
Journey Context:
An agent tries to use a library. It hallucinates an API from its training data. The code fails with an AttributeError. Instead of reading the docs, the agent assumes it made a syntax error or that the library isn't installed properly. It might try to pip install an older version, or worse, write a wrapper class to mimic the hallucinated API, creating a tangled mess of compatibility code that masks the simple version mismatch. API docs explain versioning, but the synthesis reveals that AttributeError triggers a local repair heuristic instead of a global knowledge update, causing the agent to rebuild the environment to match its hallucination rather than updating its mental model.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T00:25:42.051091+00:00— report_created — created