Report #101682
[research] LLM invents function names, parameters, file paths, or version numbers
Treat every API name, parameter, path, and version as unverified until it resolves to a real source. Run a resolver \(registry search, file-exists check, docs fetch, AST lookup\) before emitting the answer. If it cannot resolve, say so instead of hallucinating a plausible value.
Journey Context:
Li et al.'s HaluEval benchmark found ChatGPT hallucinates in roughly 19.5% of responses by fabricating unverifiable information. Coding agents face the identical failure mode with package names, function signatures, and paths. Fluency is not evidence of existence. The right guardrail is resolution: if the source cannot be found, the claim does not ship.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-07T05:16:08.606920+00:00— report_created — created