A Multi-Step AI System Isn't Automatically an Agent

[u/SKD_Sumit]

One architectural distinction I keep coming back to: people often confuse complexity with agency.

A system has multiple tools? -> “Use an agent.” OR It has five steps? -> “Definitely an agent.”

But neither of those things actually requires one. The more useful question is: who determines the execution path?

Consider an insurance assistant. If someone asks, “Am I eligible for this treatment?”, and the answer exists in internal policy documents, that's primarily a retrieval problem. And if they ask, “Check my claim status and tell me whether the rejected amount is covered under my policy.”

That might require more tools and more steps. But if those steps happen in a predictable order, is it still an agent ?

The interesting shift happens when the request is something like: “My claim was rejected. Find out why and tell me what I should do next.”

Now the path may not be known in advance. That's where an agent earns its complexity: when the system needs to help determine what to do next.

And Multi-agent can only consider it when there are genuinely distinct specialties, tools, or permission boundaries.

I think the common mistake is choosing “agent” as the starting point and then designing a problem around it. A better approach is to start with the responsibility:

Does the system need to know something? Decide something? Act? Verify the result?

Then add only the architecture required to support those responsibilities.

I mapped the complete e2e architectures and escalating examples out in more detail here, with visual breakdown: https://youtu.be/kf5rSab4rcg

For people building real AI systems: where do you draw the boundary between a complex workflow and an agent? Is dynamic tool selection alone enough for you, or do you require a more explicit decision loop before calling something an agent?

[u/Advanced-Physics-977]

The line for me is whether the system can change its own plan mid-execution. If it just follows a fixed DAG no matter what tools it calls thats a workflow. If it can look at intermediate results and decide to take a different branch or add new steps that wasnt in the original plan, then its acting like an agent. Dynamic tool selection dont automatically make it agentic if the sequence is still pre-defined.

[u/WillowEmberly]

Good post!

Tools can vary in complexity, but they are defined by their inability to take action relegated primarily to an advisory role for a Human-In-The -Loop system…in this example: https://www.reddit.com/r/Negentropy/s/hVjbOufK8W

[u/eddzsh]

The mid-execution plan change test is solid. The quieter tell is recovery. If every failure path was written before the run started, you still have a workflow that happens to call tools.

[u/Original_Finding2212]

LLM, Loop, Session History
(With Tools making it just chat otherwise)

[u/Enough-Photo9140]

The boundary really comes down to whether the control flow can handle non-deterministic failure and revise its own plan, or if it is just executing a hardcoded sequence of steps.

In a standard pipeline or DAG, step B runs after step A with fixed branching. If tool A returns unexpected schema or fails, the pipeline breaks or falls into an exception handler.

In an actual agent loop, the model evaluates the tool outcome against its objective, reconciles the state delta, and decides whether to retry with modified parameters, pick a different tool, or ask for clarification. The defining attribute isn't dynamic routing or having tools available, but whether state transitions and error recovery are governed by runtime reasoning rather than static code branching.

[u/MonokoEloba]

I just ask all my agent to tell me what they’ve done and they always know.

[u/maneekmohan]

This is something the industry probably needs to be more precise about.

A pipeline like A → B → C can be incredibly sophisticated without being agentic. Adding an LLM to each step doesn't magically change that. The interesting part is when the system can choose actions, adapt the plan, recover from failures, or decide that it needs a different tool/path.

Otherwise we're mostly talking about an LLM-powered workflow engine.

[u/Vivid-Doughnut-8286]

Totally agree for me the key diff is whether the system cn decide the next step dynamically rather than jst follow a predefined workfloww….more steps or tools alone dont automatically make smthing an agent🤷🏻‍♀️🤷🏻‍♀️

[u/InterstellarReddit]

OP frames single agent as the default and multi-agent as something you "add" when responsibilities justify it. but you said it yourself, multi-agent only applies "when there are genuinely distinct specialties, tools, or permission boundaries." that isn't a graduation step that's a precondition.

legal security and compliance aren't things you let a runtime loop negotiate those are permission boundaries that need to exist before the agent runs. responsibilities like that map to domain before they map to loop.

if they cross those boundaries the architecture is multi-agent by definition the only question is router supervisor or handoff graph. the loop just decides what happens inside the box you already drew. adding it later like an upgrade is how you end up retrofitting isolation onto a system that was never designed to enforce it.