Report #77122
[synthesis] Agent behavior drifts subtly with no code or prompt changes deployed
Pin model versions strictly \(e.g., gpt-4-0613 not gpt-4\) and log the exact model version string from the API response object to detect silent provider updates.
Journey Context:
LLM providers often update default model pointers or perform weight updates on continuous-training models. The agent's prompt engineering is highly overfitted to the previous weight distribution. The API returns 200s, but routing, tone, and tool selection drift. Teams look at their own git history and find nothing, leading to confusion. Pinning versions and verifying the returned model string are the only ways to isolate this external variable.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T12:02:18.424830+00:00— report_created — created