Context compression cut token use, but broke AI agent reliability
PepperWestern2263 · reddit · 2026-07-23
A Reddit user says context compression for AI agents reduced token usage, but also broke reliability in subtle ways.
They split context into three categories:
- Disposable context: repeated search results, duplicated docs, long file listings, verbose logs. Good candidates for filtering or summarization.
- Load-bearing context: exact error messages, file paths, line numbers, patch anchors, test names, acceptance criteria. Even small rewrites can break the next step.
- Machine-consumed context: JSON, shell output, CSV, patches, or anything parsed by another tool. This is where compression caused the most surprising failures.
The main lesson: the goal should not be the smallest possible context, but the smallest context that still preserves the evidence and interfaces needed for the next action.
The author asks how others handle this in production, and whether teams use explicit no-summarize rules or rely on retrieval.
More from coding & agent
- Dev builds interactive 3D product experience with GPT-6 Astra + Hyper3D Rodin — nikola_mr64990 · 2026-09-11
- Codex tip: use Sol with Astra and Luna sub-agents to save usage — pvncher · 2026-09-11
- agents-best-practices: a provider-neutral Agent Skill for designing and auditing agentic harnesses — tom_doerr · 2026-09-11
- Cognition's SWE-2 uses a KKT duality argument in RL to shift the effort Pareto curve — YouJiacheng · 2026-09-11
- First-ever Three.js Conference lands in Paris, with a panel on AI-shortened design workflows — OdinLovis · 2026-09-11
- Data engineering, not agent frameworks, is the real bottleneck for enterprise AI agents — dhruv2038 · 2026-09-11