Side by side
Workflow & Agent
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 | Workflow | Agent |
|---|---|---|
| Purpose | Carry out an arranged process. | Pursue a goal by choosing actions based on results. [Anthropic] |
| Role in the system | Application-defined sequencing and branching. | A decision-making loop within an application. [Anthropic] |
| Inputs and outputs | Step inputs are processed along configured paths. | Goals, context and observations inform subsequent actions. [Anthropic] |
| Persistence | State retention depends on implementation. | State retention depends on implementation. [Anthropic] |
| Example | Classify a request, retrieve a policy, then draft an answer. | Choose a follow-up investigation after inspecting a tool result. [Anthropic] |
| Boundary caveats | A workflow can include models and agent-like steps. | Autonomy is bounded by the available tools and controls. [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.