Latest stories
Story · 1 report
The State of Context Engineering
Context engineering has evolved from manually selecting prompt information to building software harnesses that retrieve, filter, prune, summarize, and isolate information for AI models. Dave Breunig argues that the central task is deciding which behavior should be enforced by deterministic code and which should be delegated to probabilistic model calls. Long context windows, which expanded from roughly 128,000 tokens to millions beginning with Gemini 1.5, can accommodate more data but also more errors and conflicting signals. Breunig identifies context poisoning, distraction, confusion, and clash as major failure modes. Google reported that Gemini 2.5 playing the original Pokémon Red repeatedly pursued tea, an objective from Pokémon FireRed embedded in its training data, despite the older game requiring lemonade. Research by Carolina Camassa and Derek Shiller found that contradictory examples in a conversation can increasingly override explicit instructions. Google also reported that Gemini 2.5 began repeating historical actions rather than making new plans once Pokémon-agent context grew well beyond 100,000 tokens. Harness techniques include retrieval-augmented generation, selective tool loading, fresh-context subagents, history pruning, external storage, and compaction. Breunig says agentic models introduce tool-environment biases and “context inertia,” in which agents persist with an unproductive hypothesis. Anthropic’s Memento tests and research from Microsoft and UC Berkeley found that periodically clearing conversational context while retaining work artifacts can restore exploration and improve results.
dbreunig.com
🔥🔥🔥🔥🔥2 min summary
10/25/2026
No more articles to load
