Europe 2026
Stop babysitting your agents... — Brandon Waselnuk, Unblocked
Overview
This talk addresses the challenge of agents lacking necessary context, forcing engineers to act as the "context engine." It proposes that instead of babysitting agents, a dedicated context engine is needed to provide agents with comprehensive, runtime-relevant information. This engine should understand organizational specifics, resolve conflicts, and deliver token-optimized responses, ultimately enabling agents to produce code and actions that reflect deep team integration.
Who should watch
- AI Engineers
- Product Managers
- Builders working with AI agents
- Those experiencing agents that require constant supervision
- Teams looking to improve agent accuracy and efficiency
Key takeaways
- Agents often start with zero context, requiring engineers to manually build this context, a role that should be automated.
- Naive Retrieval Augmented Generation (RAG) over documentation is insufficient for providing agents with the necessary context.
- Simply connecting more Multi-Call Primitives (MCPs) or increasing context window size does not solve the core problem of understanding and reasoning.
- A context engine should ingest data from various sources, reason across them at runtime, and provide token-optimized, relevant information to agents.
- Key components of a context engine include a social graph for personalized relevance, conflict resolution, and adherence to data governance and permissions.
- A context engine enables agents to produce code and plans that are more accurate, efficient, and reflective of team standards, reducing the need for manual oversight.
- Caching agent outputs can be detrimental as information quickly becomes outdated, leading to inaccurate responses.
- AI-forward teams are leveraging context engines for various applications, including automated responses in engineering channels, ticket enrichment, and incident management.
Notable quotes
*The gap is not intelligence at this point. It is context.*
*An agent should write code that feels like it was written by someone who's been on your team for years.*
Unofficial community note. Prefer the recording for nuance.