Dropbox Dash uses context engineering to improve agentic AI accuracy and performance
Dash's original RAG pipeline handled basic retrieval well but was insufficient for agentic tasks; adding more tools caused analysis paralysis, context rot, and accuracy degradation on longer-running jobs.
Using multiple separate retrieval APIs proved unreliable—the model often failed to call all required sources—and MCP tool definitions consumed excessive tokens, degrading performance.
Dropbox adopted three context engineering strategies—consolidating retrieval into a single unified index, filtering context via a knowledge graph, and delegating complex query tasks to a specialized search agent—resulting in faster, more accurate agentic performance with leaner context usage.
Frequently asked questions
What did this team achieve with this AI workflow?
Dropbox adopted three context engineering strategies—consolidating retrieval into a single unified index, filtering context via a knowledge graph, and delegating complex query tasks to a specialized search agent—resul…
What tools did this team use?
Dash, Model Context Protocol, Dash Search, Confluence, Google Docs, Jira.
What results were reported?
Model decision making speed and accuracy: slower, less accurate decision making; Dash accuracy on longer-running jobs: degraded; Model performance with leaner context: leaner contexts don't just save resources; they also make the model smarter; Reasoning clarity and plan efficiency: makes its reasoning clearer, its plans more efficient, and its context use more focused (source-reported, not independently verified).
What failed first in this deployment?
Using multiple separate retrieval APIs proved unreliable—the model often failed to call all required sources—and MCP tool definitions consumed excessive tokens, degrading performance.
How is this back office ops AI workflow structured?
User submits agentic request → Planning agent determines next action → Specialized search agent constructs query → Unified Dash Search index retrieves results → Knowledge graph ranks and filters results → Main agent generates final response.