Report #46411
[research] Hallucinating APIs, parameters, or methods for niche, outdated, or obscure libraries with high confidence
Force a calibrated uncertainty step: if the library or API is not standard \(e.g., standard Python/JS built-ins\), require the agent to explicitly search documentation via a tool or state 'I don't know' rather than guessing.
Journey Context:
LLMs confidently hallucinate APIs for low-frequency tokens because they don't inherently know their training data boundaries. Forcing a retrieval step for non-canonical code acts as a grounding anchor and prevents the model from blending APIs from different libraries.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T08:22:30.733562+00:00— report_created — created