Side by side
Agent & Workflow
In this scoped distinction, an agent dynamically directs its process while a workflow primarily follows control flow prescribed by code.
These are useful design patterns, not mutually exclusive product categories. Hybrid systems are common.
Swap columns ⇄| Dimension | Agent | Workflow |
|---|---|---|
| Purpose | Pursue a goal by choosing actions based on results. | Carry out an arranged process. [Anthropic] |
| Role in the system | A decision-making loop within an application. | Application-defined sequencing and branching. [Anthropic] |
| Inputs and outputs | Goals, context and observations inform subsequent actions. | Step inputs are processed along configured paths. [Anthropic] |
| Persistence | State retention depends on implementation. | State retention depends on implementation. [Anthropic] |
| Example | Choose a follow-up investigation after inspecting a tool result. | Classify a request, retrieve a policy, then draft an answer. [Anthropic] |
| Boundary caveats | Autonomy is bounded by the available tools and controls. | A workflow can include models and agent-like steps. [Anthropic] |
Evidence for this distinction
- Building effective agents ↗ (opens in new tab)Anthropic · 2024-12-19
Relevant section: What are agents?; Building blocks; Agents; Appendix 2
Last editorial review: 2026-09-13.