Report #61061
[frontier] Agent behavior in later turns shaped more by first few exchanges than by system prompt
Carefully script or prime the first 2-3 exchanges of every agent session to demonstrate the exact tone, style, and constraint adherence you want. Never let the first exchange be a simple greeting — make it a substantive demonstration of the agent's identity in action.
Journey Context:
The first few exchanges create a strong anchoring effect that shapes all subsequent behavior. If the agent's first response is verbose and chatty, it will tend to stay verbose. If terse and technical, it stays terse. The model treats its own prior outputs as strong evidence of its behavioral identity. The frontier practice is 'first-exchange priming' — designing initial exchanges to set the behavioral tone before the real task begins. Some teams use a 'warmup protocol': a scripted first exchange demonstrating desired behavior. This is more effective than trying to correct drift later because early outputs create a behavioral ratchet that resists change. Tradeoff: costs tokens and adds latency, but the anchoring effect is strong and persistent across the entire session.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T08:58:43.662214+00:00— report_created — created