Report #1899
[research] Using outdated library functions or deprecated APIs that dominate training data
Inject current version documentation via RAG and explicitly instruct the model that retrieved API signatures supersede parametric memory; penalize or rewrite known deprecated patterns.
Journey Context:
LLMs default to the most represented version in their training data. If a library changes \(e.g., LangChain, PyTorch\), asking for the 'latest' version often fails because the model's weights strongly favor the older syntax. Parametric memory must be explicitly overridden by contextual grounding.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T08:55:51.347057+00:00— report_created — created