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
- Data engineering, not agent frameworks, is the real bottleneck for enterprise AI agents — dhruv2038 · 2026-09-11
- GPT-6 Astra beats Factorio with enemies in 44 in-game hours at ~$4,500 API cost — liminal_bardo · 2026-09-11
- 105 hidden bugs, 2 repos: DeepSeek V4.1 Flash fixes 24 at $1.80 vs Opus 5's 27 at $51.33 — ChartsJournalX · 2026-09-11
- Investment Analyst Asks How to Build a Claude-Based Diligence Agent Stack — Careless_Tie2286 · 2026-09-11
- Treating agents like 50 First Dates: a 3-layer context system so every conversation doesn't start from zero — evielync · 2026-09-11
- Running the Firefox MCP on Android via Termux, ngrok, and mcp-proxy — Nervous-Strain7544 · 2026-09-11