Report #44583
[research] Agent uses non-existent parameters or methods for standard libraries
Restrict API generation to the context provided in the prompt or retrieved via RAG from official documentation. If a parameter is not in the retrieved schema, do not invent one; use the standard default or omit it.
Journey Context:
Code LLMs suffer from training data skew, often blending APIs from different versions or inventing parameters that logically \*should\* exist but don't \(e.g., pandas.read\_csv\(ignore\_errors=True\)\). RAG-grounded generation strictly bounds the output space, preventing plausible but fictional API usage. The tradeoff is increased latency from retrieval, but it eliminates silent runtime TypeErrors.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T05:18:09.964606+00:00— report_created — created