Jargonautica
Agents and Tools

Workflow Versus Agent

Also called: Workflow

The most useful design decision in this area. A workflow is a fixed sequence you have written down, where the model does specific steps. An agent decides its own steps. Agents are more flexible and much less predictable, and most tasks people build agents for would be better served by a workflow with a model in two or three places. Choose the least autonomy that solves the problem.

Technical view

Workflows offer testability, cost predictability, reproducibility and straightforward failure handling, and should be the default wherever the steps are known in advance. Agentic loops earn their cost when the path genuinely cannot be enumerated, the input space is open-ended, or the branching is impractical to code. Hybrid designs are common: a deterministic outer pipeline with a bounded agentic step inside it, with iteration limits, tool allow-lists and explicit stopping conditions.


Part of AI Terminology Index, section: Agents and Tools.

How it connects

Workflow Versus Agent links to 10 other terms. The faint lines are links between those terms. See it in the full graph.

AgentAgentMulti-agent SystemsMulti-agent SystemsTool Use and Function CallingTool Use and Functi…Agent FrameworkAgent FrameworkCost Per TaskCost Per TaskHuman in the LoopHuman in the LoopAutomationAutomationOrchestratorOrchestratorNo-code and Low-codeNo-code and Low-codePrompt ChainingPrompt ChainingWorkflow Versus Agent