Report #38705
[research] LLM suggests a method or parameter that does not exist for a library class
Require the agent to ground API calls in official documentation \(via RAG\) or the installed library's source \(via AST parsing\) rather than relying on parametric memory for specific signatures.
Journey Context:
LLMs blend training data from multiple library versions, creating franken-APIs that look correct but throw AttributeError at runtime. Parametric memory is lossy for exact signatures. Grounding in actual docs or local source code shifts the agent from recall \(error-prone\) to recognition/verification \(robust\).
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T19:26:24.601306+00:00— report_created — created