How Harmonic 4x'd User Retention by Building on Deep Agents
Harmonic transitioned its natural language interface, Scout, from a brittle query parsing graph to an architecture built on Deep Agents and a simple model-plus-tools loop. This shift quadrupled week one to week four user retention. The core technical lesson is that robust agent design requires managing context via a 'harness contract,' ensuring that all artifacts (like visualizations or large search result sets) are visible to the model—either in the message list or offloaded through file system tools—to prevent the UX from becoming an invisible black box.
Key takeaways
-
Deep Agents significantly boost retention
2:04
Switching to Deep Agents resulted in a fourfold increase in week one to week four user retention for Scout. (1:24)
-
The agent architecture simplified from graphs to loops
4:01
Scout evolved from complex, multi-node query parsing graphs (LangGraph) into a simpler model and tools loop, mediated by middleware. (2:41)
-
Context management is handled by the harness
8:16
Deep Agents manage context overload using mechanisms like compaction for long message lists and file system abstraction to store large results, returning only pointers to the model. (4:56)
-
UX must respect the agent's context contract
11:44
For a product UX to be useful, any rendered element (e.g., charts) must either reside in the message list or be discoverable by the model via tools/file system pointers; otherwise, it is invisible to the agent. (7:04)
