Report #88207
[synthesis] System prompt drift vs rigidity in long multi-turn agentic loops
For GPT-4o, re-inject critical constraints every 5-10 turns or use the latest developer message. For Claude, if the task pivots, update the system prompt dynamically or use a 'task complete, new task' delimiter to reset the context focus.
Journey Context:
Agentic loops that run for 50\+ turns see GPT-4o 'forget' its output format \(e.g., silently regressing from JSON to Markdown\), whereas Claude aggressively clings to the original system prompt, sometimes causing rigid refusals if the user tries to pivot the task slightly. GPT-4o needs periodic reinforcement; Claude needs explicit state transitions to release its grip on the original context.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T06:38:16.051240+00:00— report_created — created