World's Fair 2026
User Signal Dies at the Retrieval Boundary - Sonam Pankaj, StarlightSearch
Overview
This talk addresses a critical failure point in AI agents: the inability of evaluation signals to inform future actions, leading to repeated errors. The core thesis is that current agent memory systems are static and do not learn from past successes or failures. The presentation introduces a new runtime experience, Agent RX, designed to bridge this gap by allowing agents to improve dynamically based on outcomes without retraining or manual prompt engineering.
Who should watch
- AI engineers and builders struggling with agents that repeatedly fail on the same tasks.
- Product Managers and engineers seeking to improve the reliability and outcome-informed decision-making of AI agents.
- Developers interested in novel approaches to agent memory and learning from evaluation data.
- Anyone facing challenges with retrieval accuracy and context stuffing in agentic systems.
Key takeaways
- A significant majority of AI agent failures stem from retrieval issues rather than generation problems.
- Current evaluation (eval) signals often die in dashboards, failing to influence agent behavior or memory.
- Existing memory systems typically store static data like user preferences or conversation history, lacking a mechanism for outcome-based learning.
- Agent RX introduces a "utility score" that weights retrieved memories by their historical usefulness in achieving task outcomes.
- This approach treats memory as reasoning, enabling agents to adapt their actions based on past performance and task context.
- Agent RX has demonstrated performance improvements on benchmarks like Towel Bench and agentic task evaluations.
- The system can bake learned reasoning and updates into skills, allowing agents to adapt without prompt re-engineering.
- Limitations include a cold start problem and potential utility drift, though many issues are mitigated.
Notable quotes
*We have been optimizing for the wrong thing. You are paying a lot for your agents memory. This is probably broken, and we have been optimizing for the wrong things.*
*The eval signal dies in the dashboard. This is a missing layer, a system that consume traces, absorb eval, and convert both into retrieval guidance for future runs.*
Unofficial community note. Prefer the recording for nuance.