Prompt Bloat

also known as Prompt Accretion, Eternal System Prompt

Anti-pattern: every bug fix adds a sentence to the system prompt; nothing is ever removed.

Context

A production agent has been live for months and the system prompt has grown one sentence at a time. Each bug fix, edge case, and customer complaint adds another instruction; nothing is ever removed because removing a line feels riskier than leaving it. There is no owner of the prompt as a whole, no review on prompt diffs, and no eviction policy for instructions that are no longer relevant.

Problem

Past a few thousand tokens, the prompt starts to squeeze retrieved context and tool definitions out of the model's attention budget, prompt-cache reuse degrades because every small edit changes the cached prefix, and instructions that were added at different times begin to contradict each other. The model resolves the contradictions inconsistently, so newer rules silently override older ones for some inputs and not others. This is distinct from a hero agent, which is about scope; this is about the accretion process itself, where the prompt is treated as append-only documentation rather than as code.

Forces

Adding a sentence feels free; removing one feels risky.
No clear owner of the prompt's overall design.
Eval coverage rarely catches bloat-driven regressions.

Example

A coding-agent team adds one sentence to the system prompt every time a customer reports an edge case. Eighteen months later the prompt is 6500 tokens, prompt-cache misses are common, and the model's instruction-following is visibly degraded — newer rules contradict older ones. The team names it prompt-bloat: the prompt goes under PR review with a length budget, recurring procedures are lifted into agent-skills, stable rules move into a constitutional charter, and a quarterly pruning sprint trims dead weight. The prompt halves and quality climbs back.

Diagram

Solution

Therefore:

Don't. Treat the prompt as code: PR review, eval gate on length, quarterly pruning sprints. Lift recurring procedures into agent-skills. Move stable rules into a constitutional charter.

What this pattern forbids. By definition, this anti-pattern imposes no useful constraint; the missing eviction policy is the failure.

And the patterns that stand alongside it, or against it —

alternative-toAgent Skills★— Package author-time procedures (markdown + optional resources) the agent loads on demand for specific task types.
alternative-toConstitutional Charter★— Define rules the agent reads every turn but cannot modify, encoding inviolable boundaries.
complementsHero Agent✕— Anti-pattern: stuff every capability into one agent with one giant prompt.
complementsContext Window Dumb-Zone Cap★— Hold context-window utilization below a working threshold (~40%) to keep the model out of the 'dumb zone' where it begins ignoring earlier instructions and hallucinating.