Context engineering
Give an agent the right instructions, relevant evidence, system state, and task boundaries before it reasons or acts.
CONTEXT · TOOLS · ORCHESTRATION
Harvey approaches agents as complete software systems—not isolated prompts. The focus is on grounded context, clearly scoped tools, observable workflows, validated outputs, and human control.
ENGINEERING APPROACH
A useful agent needs more than a model response. It needs application context, bounded capabilities, state, validation, recovery paths, monitoring, and an interface that makes its progress understandable.
Give an agent the right instructions, relevant evidence, system state, and task boundaries before it reasons or acts.
Connect models to focused APIs, application services, search, data, and automation capabilities through explicit tool contracts.
Break complex goals into observable steps with routing, retries, state management, and clear completion conditions.
Use predictable schemas and validation so agent decisions can safely connect to real software workflows.
Constrain tool access, validate actions, and keep people in control when a workflow could affect important systems or data.
Measure answer quality, tool selection, latency, failures, and task completion instead of judging an agent only by its demos.
REPRESENTATIVE AGENT LOOP
Each step creates an observable checkpoint instead of hiding the entire task inside one prompt.
WHAT GOOD LOOKS LIKE
Grounded answers instead of unsupported confidence
Small, auditable tools with explicit permissions
Structured state across multi-step workflows
Human approval for consequential actions
Evaluation based on real task outcomes
Clear loading, progress, and recovery states
BUILD AN AGENTIC WORKFLOW