Report #61979
[architecture] Appending new instructions to a long context window containing outdated or conflicting prior instructions, assuming the LLM will prioritize the newest text
Use a 'scratchpad' or explicit state machine for mutable directives. When a rule changes, overwrite the old state rather than appending the new rule to the context.
Journey Context:
LLMs suffer from the 'primacy effect' and can be anchored by early context. If you tell an agent 'always use Python', then later say 'actually, use Rust', appending the Rust instruction often fails because the agent is anchored to Python. The tradeoff is that managing a mutable state object requires more complex orchestration code than just pushing strings to a list. However, treating the context window as an append-only log is a fundamental architectural mistake for mutable state.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T10:31:11.517587+00:00— report_created — created