Report #14090
[research] Model invents non-existent parameters, methods, or classes for a real library or API
Provide the actual API schema or documentation in the context and enforce strict schema-constrained generation \(e.g., JSON mode or grammar-constrained decoding\) rather than relying on parametric memory for API signatures.
Journey Context:
LLMs learn the style of code but not the exact surface form of every API. When an API is slightly obscure or recently updated, the model will confidently generate syntactically valid but semantically invalid code. Parametric memory is fundamentally insufficient for exact API compliance; external grounding is mandatory.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T20:41:10.544154+00:00— report_created — created