How Harmonic 4x'd User Retention by Building on Deep Agents

A tight case study from Harmonic on rebuilding their agent product and quadrupling week-1-to-week-4 retention in the process. The core lesson generalizes to any agentic product: anything you render to the user that isn't in the messages list or an agent-accessible file system is invisible to the model, and that invisibility silently degrades every follow-up interaction. Sixteen minutes, one clear design principle, immediately applicable.

• Switching from a complex multi-node query graph to Deep Agents produced a 4x retention improvement from week one to week four
• The critical UX rule: if users see data the agent can't access, the agent loses the ability to reason about it in follow-ups
• Embed visualizations directly in assistant messages with delimiters so the model retains full visibility and can modify them on request
• Design smell test: if you're telling the model to 'trust' that something is rendered, you've probably made it invisible to the agent

Part of Issue Nº 004: OpenClaw's near-burnout, agent teams that ship 99.9% of PRs, and the math behind prompt caching