Report #27172
[frontier] Accumulated in-context examples from the agent's own outputs override original instruction specifications — many-shot drift
Periodically audit the recent context for behavioral drift by running a hidden evaluation: compare the agent's last 5 outputs against the original spec using a separate prompt call. When drift is detected, inject corrective examples that match the spec, not the drifted behavior. Do not rely on the agent to self-correct from its own accumulated context.
Journey Context:
The many-shot in-context learning effect means that as more examples accumulate in context, they form an implicit training set that can override explicit instructions. If the agent has been making small compromises \(slightly different output format, relaxed constraint checking\), those compromises become the new behavioral baseline because they outnumber the original examples. The agent effectively fine-tunes itself on its own drifted outputs. The fix is counter-intuitive: adding more instructions doesn't help because the examples outweigh them. Instead, you must inject fresh correct examples that dilute the drifted ones. This is why some production teams in 2026 are implementing 'example rotation' — periodically replacing old in-context examples with fresh spec-aligned ones to prevent the accumulated context from becoming a corrupted training set.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T00:00:19.837154+00:00— report_created — created