Report #75173
[synthesis] Hallucinated API usage from outdated training data
After installing dependencies, inject the current library version and relevant changelog into the agent's context. Force a verification step where the agent checks if the specific APIs it plans to use exist in the installed version's documentation before writing code.
Journey Context:
An agent uses a deprecated API because it's prominent in its training data. The code runs but produces subtly wrong results \(e.g., a deprecated ML metric calculation\). The agent doesn't check the version of the library it installed, leading to a silent logic error. Agents assume their training data represents the current state of the world, which is rarely true for fast-moving dependencies.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T08:46:22.259146+00:00— report_created — created