Your agents lack context: Here's how to fix "You're absolutely right!" — Brandon Waselnuk, Unblocked
Summary
AI agents require more than just access to information; they need a 'context engine' to achieve true understanding of a company's operations, business logic, and historical decisions. The talk details how agents fail when they lack deep, organizational context, leading to wasted tokens and time. The solution involves building a context engine that ingests data from disparate sources (e.g., ticketing systems, code repos) and provides structured, conflict-resolved context to the model in a token-optimized manner.
Key takeaways
-
The Context Gap
AI-generated code must feel like it was written by a long-term team member, which requires deep operational context that current agents lack. This gap compounds as agents scale from simple tab completion to background processes.
-
Failure Modes of Context
7:00
Common approaches like the 'curated context trap' (where documentation rots) and the 'MCP plateau' (where agents suffer from satisfaction of search bias) fail because access to information is not the same as understanding it.
-
The Role of the Context Engine
9:12
A proper context engine must perform conflict resolution (e.g., resolving conflicting architecture diagrams vs. Slack messages), respect permissions (OAuth/SSO), and deliver context in a token-optimized way.
-
Efficiency Gains
13:00
Implementing a context engine can lead to significant efficiency gains, demonstrated by a reduction from 21 million to 10.8 million tokens and a two-hour reduction in wall-clock time for the same task.
Technical details
-
Context Engineering Principles
552s
The engine must provide six key characteristics: unified system context, conflict resolution, personalized relevance, permission enforcement, token optimization, and the ability to map and discover unknown unknowns.
-
Agent Scaling Issues
110s
As agents move into parallel or background roles, they face 'doom loops,' resulting in wasted search tokens and a 'review tax' because they lack understanding of business logic and deployment procedures.
-
Contextual Retrieval
630s
The engine ingests real-time data from multiple sources (e.g., instant management tool chains) and outputs context to the exact workflow, going beyond simple Retrieval Augmented Generation (RAG) to handle relational data queries.
-
Tools and Techniques
726s
The speaker demonstrated tools like a social network graph that maps team members and commits, and the 'repo rules agent,' which indexes rules files to help deduplicate context and improve retrieval.
Mentioned resources
- Unblocked
- relational context engine workshop
- readiness.unblocked.com
Channel & topics
Watch on YouTube · Back to latest
This independent, AI-assisted summary is provided for commentary and informational purposes. It may contain errors or omit important context. Please watch the original video for the creator's complete presentation. Video, thumbnail, and related copyrights belong to their respective owners.