Loop vs Workflow vs Agent

A workflow enumerates steps a person invented. A loop is a compiled standing order that fires when a signal repeats. An agent reasons when the path is not yet known. Anthropic’s guidance on building effective agents is blunt about the distinction: encode the job when you can; reserve autonomy for inputs that will not sit still. Operators need the noun that matches how stable the job is — not the noun that wins the demo.

Three words, disambiguated up front, plus the sibling people keep folding in:

• Loop. A compiled standing order: triggers, a trusted recipe, outcomes on a run page, skip when nothing changed. See what is loop engineering and six things that start a loop. Loops are for work that repeats on recognizable signals.
• Eval loop. An independent verification that a job finished — tests, schema, read-back, signer — not the model’s claim. See eval loops for enterprise agent harnesses. A loop may include eval steps; “eval loop” is not “loop.”
• Agentic workflow. A designed sequence of steps toward a goal, with business stop conditions — including a person before a live system changes. See what is an agentic workflow. Workflows are what someone invented; they are versioned and hosted on a workstream.
• Agent. A reasoner that picks tools when the path is not fully enumerated. See what is an agent harness and a loop is not an agent.

If your buying conversation starts with “we need an agent,” pause. That sentence often means three different jobs. Buying the wrong one wastes the quarter — not because the model is weak, but because the operating object is wrong. McKinsey’s 2025 State of AI keeps showing high usage and uneven scale. Scale, in this vocabulary, usually means compiling what worked — into a workflow or a loop — not hiring a larger model to improvise the same close every month.

Workflow — steps a person invented

A workflow is a sequence someone designed: extract, compare to a playbook, quote the CRM fields, wait for the named signer, write or refuse. The author is a person. The instance is durable. The finish line is named before the run starts.

Workflows excel when:

• the stop conditions matter as much as the steps — budget, approval, empty result, a clause that is non-standard
• roles differ by step — analyst drafts, controller signs, counsel refuses
• the job is interactive — humans join mid-flight with context attached
• you must version the definition — “which workflow ran last Tuesday?” is a fair audit question

A workflow is the right object when the path is known enough to draw and still needs a person at a gate. Month-end sign-off is a workflow even if a loop assembled the pack. Discount exceptions are a workflow even if a loop watched the stage change. The designed sequence is how you keep roles from collapsing into “the model posted it.”

Workflows fail when teams treat them as magic. A checklist in a prompt is not a workflow. A chat with tools is not a workflow. A Lucidchart on a wiki is not a workflow runtime. A workflow has a durable instance, a finish line, and a record that survives the session. If you hide the chat and cannot reconstruct which step was waiting on a person, you bought conversation.

Operator test: Can an independent reader reconstruct which steps ran, what was waiting on a person, and what was refused — without Slack search?

What is human-in-the-loop AI belongs here more than it belongs on the loop. Loops can pause; workflows are often about the pause. The pause is the product. If your vendor cannot show a named stop, you do not have a workflow. You have a script with optimism.

Loop — a compiled standing order

A loop is what you run when the world sends the same signal again: Monday close, file in folder, stage flipped, billing event, someone presses run now. See six things that start a loop. The author compiled the recipe once. The trigger admits a run. The run page is the contract.

Loops excel when:

• the recipe is stable enough to reuse without re-prompting
• skip semantics matter — “nothing changed” should be a first-class outcome
• operators need a run page, not a transcript
• the same kernel should answer to several triggers without several copies

Loops are not “set and forget” if forget means no record. A good loop logs quiet outcomes, notifies the roster, and attaches outputs where the next role expects them. How to evaluate loop engineering is the RFP sheet for this object. NIST’s AI Risk Management Framework Measure function assumes you can observe those outcomes. A loop without a run page is not observable. It is email archaeology.

Loops fail when they are copied from someone’s channel, when skip is implemented as “don’t email,” or when every step secretly calls a model. On the happy path, a loop is not an agent: it should not re-derive the job. If Monday’s close still begins with “please do the usual,” you have not compiled anything.

Operator test: Run it ten times with empty inputs. Do you get ten run pages that say skipped — or ten emails saying error?

Loop engineering vs harness engineering draws the line: loop engineering compiles repeat work; harness engineering tightens the environment when interactive agents fail. You need both crafts. They fail differently. A loop that guesses at 3am is a harness problem you imported into unattended hours.

Agent — reasons when the path is unknown

An agent (in the product sense) chooses actions when you cannot enumerate every branch upfront: read these ten documents and tell me which clause conflicts; investigate why margin diverged across three regions; draft three options for a novel pricing exception. LangChain’s definition is a useful shorthand: Agent = Model + Harness. The harness is not optional. Without tools, stops, and a budget, you have a chatbot with aspirations.

Agents excel when:

• inputs are messy or novel — PDFs, threads, ambiguous tickets, a vendor paper the team has not seen
• the path emerges during the job — you would not trust a fixed script yet
• the cost of a wrong step is bounded — read-only tools, draft-only outputs
• a human will compress the result into a decision artefact

Agents fail when teams use them as cron with charisma. If the job is the same every Monday, an agent rediscovering the steps is expensive theatre. It is also a control failure: the path that ran last week is not a path you can open next week. Stanford HAI’s AI Index is a reminder that capability is not the scarce resource. Operational maturity is.

Operator test: If you hid the chat and kept only the artefact, would the company still know what changed? If not, you bought conversation, not control.

Score agents with how to evaluate an agent harness, not with this page’s skip-semantics tests. The hero metric for an agent is whether you can stop a write and replay what was refused. The hero metric for a loop is whether you can skip quietly and prove it.

Three-way comparison

None of these rows replaces your CRM. They describe how work runs on top of systems of record. The enterprise AI operating system metaphor is the kernel version of the same problem — isolation, permissions, durable state — applied to jobs rather than applications. This article stays at the operator nouns. Use the OS page when you need the kernel language; use this page when someone says “agent” and means a Monday report.

ISO/IEC 42001 will not tell you which noun to buy. It will ask whether you can name the system, the owner, and the record. Workflows, loops, and agents all fail that test when they live only in a transcript.

How they compose in one quarter

Real companies stack all three. The stack is not three products competing. It is three stability levels: novel → designed → repeated.

1. Agent investigates a new vendor contract — extracts obligations, flags non-standard terms, drafts a summary for counsel. The path is unknown. The output is a draft. Nothing customer-facing sends.
2. Workflow routes the summary through Legal review on a workstream, with a hard stop before anything leaves the company. Roles stay distinct. The instance is durable. Counsel can refuse.
3. Loop watches the signed folder and, every time a countersigned PDF lands, updates the renewal tracker and notifies RevOps — skipping if the hash matches last week’s file. The signal repeats. The recipe does not.

That composition is how you avoid the two failure modes that dominate programmes: agent-for-everything, and checklist-in-a-wiki. The first burns tokens and produces untraceable month six. The second produces a drawing that nobody runs.

Department guides use the same stack with different default nouns:

• Finance and planning — loops for scheduled packs; workflows for close sign-offs; agents for one-off variance forensics. See loops for finance and planning and collaborative AI for finance and planning.
• Revenue operations — loops on stage changes; workflows for discount exceptions; agents for messy account research. See loops for revenue operations and collaborative AI for revenue operations.
• Legal and compliance — workflows for approvals; loops on inbound redlines; agents for first-pass clause comparison. See loops for legal and compliance.

Collaborative AI is the roster pattern underneath all three: multiple roles, one job object, a finish line. The noun you pick does not replace the roster. An agent without a roster is a personal copilot. A loop without a roster notifies a dead channel. A workflow without a roster has nobody to stand at the gate.

What people get wrong

Agent for everything. Impressive week one; untraceable month six. The model will happily re-solve a solved problem. You will pay for it twice: inference, and the incident when it improvises a write.

Workflow without an instance. A diagram is not a runtime. If you cannot open last Tuesday’s run and see the step that was waiting, you have documentation, not a workflow.

Loop copied from someone’s Slack channel. If reuse means “find the old thread,” you have folklore, not loop engineering. Folklore does not survive vacation.

Confusing eval loops with loops. Benchmarks and read-backs verify completion; standing-order loops start and record repeat work. Both can coexist on one job. Collapsing them hides whether you can start work and whether you can prove it finished.

Buying a platform that only sells one noun. If the vendor cannot host a workflow gate, a loop run page, and an agent task on the same roster, you will rebuild org boundaries in email. That is not a tooling preference. It is how departments already work.

Treating RPA as the fourth synonym. Screen replay is a different category. See loop vs RPA. A bot that clicks an ERP has a place. It is not a standing-order loop, a designed workflow, or a reasoner.

Choosing this week

Ask two questions, in this order:

1. Do we know the steps? No → agent, bounded. Yes → workflow or loop.
2. Will the same signal fire again? Yes → loop. No → workflow.

If both yes — stable steps and a repeating signal — start with a loop. Add workflow gates inside it when a named signer must appear. Add an agent step when one stage still needs reading messy inputs. That is the composition above, reduced to a decision tree you can use in a working session.

If both no — unknown steps and a one-off — you are in research. Do not compile yet. Do not buy a bot. Bound the tools, keep the output as a draft, and decide next week whether the path is now known.

The four pillars of an enterprise AI platform is the wider map: communication brings context, collaboration hosts the job, automate repeats the recipe, governance refuses what should not land. Loops, workflows, and agents all sit on that map. They are not a substitute for it.

Related reading: what is collaborative AI, how to evaluate collaborative AI, and what is harness engineering when agents and loops share the same stops.

How this shows up in Nimbus

Nimbus hosts all three nouns on the same workstream. Loops are standing orders with run pages. Agentic workflows are designed sequences with governance gates. Agents run as bounded teammates with scoped grants, not as a second platform. Conflux is often the communication door that starts a loop when a file lands.

Treat that as one vendor’s mapping of the pattern, not as the definition. If you are writing an RFP, paste the questions from how to evaluate loop engineering and how to evaluate an agent harness and run them on whoever claims the nouns. The useful outcome is not a logo. It is whether Tuesday’s close, Tuesday’s exception, and Tuesday’s novel contract can share a roster without collapsing into one chat.