Click any tag below to further narrow down your results
Links
David Breunig's talk on how context engineering emerged after the long-context push of 2024, why bigger context windows introduced new failure modes, and the six patterns builders now use to manage what goes into a model's context. It's a useful map of where the practice has been and where it's headed.
- Million-token context windows didn't solve the problem. Long contexts add room for errors as well as information, leading to failure modes like context poisoning, distraction, confusion, and clash.
- Gemini 2.5 playing Pokémon shows poisoning in practice: a fact baked into its weights (the tea bribe from the older game) got stuck in its context and cost it hours. Performance also degraded past roughly 100,000 tokens, with the agent repeating old actions instead of planning new ones.
- Breunig's research cites shows instruction-following drops as bad examples pile up in context, affecting every model tested, including smaller ones that fall below half adherence after a few contradictions. The six-tool toolbox (augmentation, loadout, quarantine, pruning, offloading, summarization) has stayed stable as these problems emerged.
@0xMortyx on X
A 90-minute Google Cloud workshop walks through building production AI agents, moving from basic retrieval-augmented generation (RAG) to Graph RAG, memory, and multi-agent orchestration. The post shares a timestamped chapter guide and links to a written roadmap covering the same progression.
- The workshop is organized as a progression: RAG, then Graph RAG, then memory, then multimodal agent graphs.
- Hands-on sections cover setting up a production agent stack, Graph RAG with semantic search, extracting graph context, and orchestrating specialized agents.
- The author frames it as one of the clearer hands-on examples of teams moving beyond plain RAG toward graph-based context.