How does an agentic workflow differ from a chatbot or a cron job?
A chatbot answers when you ask something and then stops. A cron job or script runs at a fixed time and does exactly the same thing every time. An agent loop, which keeps an agentic workflow running, sits in between. A scheduler starts the agent at set times, but the agent decides what to do next, based on a task list and rules. It reads the task and chooses an approach. It uses tools such as a CMS, a terminal or an API, and checks the result before it closes the task.
The difference is judgment at every step. A script gets stuck as soon as the input differs from what it expects. An agent sees that a task is unclear, takes a different route or deliberately leaves the task open with a question for a person. You can read what an AI agent is and how it works in what is an AI agent.
Anthropic draws the same line in its December 2024 guide to building effective agents. It writes: "Workflows are systems where LLMs and tools are orchestrated through predefined code paths." Agents, on the other hand, "dynamically direct their own processes and tool usage." An agentic workflow puts that flexible agent inside a fixed frame of tasks and rules. Guides on agentic workflows often name three patterns: planning, tool use and reflection. You will find them in the five steps below: the agent plans, uses tools and has its own work checked.
How does a team of subagents work?
One agent that does everything itself fills up: every search, every file and every intermediate step stays in the same conversation. That is why a main agent splits up the work. It hands well-defined subtasks to subagents and only gets their final report back.
In Hermes this is called delegation. According to the documentation, each subagent starts with a completely fresh conversation and its own terminal, and it inherits the main agent's tools. Only the summary goes back to the main agent. By default, up to ten subagents run at the same time. You can also give subagents a different model. For example, a fast and inexpensive model does the research, while the main agent plans with a stronger one.
This creates a team with roles. An explorer gathers sources, files or data. A builder carries out a well-defined change. A reviewer checks the result without knowing the builder's reasoning. That is the point: a second pair of eyes that does not follow the same flawed line of thought. For demanding reviews, you put a stronger model on that role. A setup like this, with several agents working together, is also called a multi-agent system.
What does one round of an agentic workflow look like?
Every round follows the same five steps. The order is fixed; what the agent does within a step depends on the task.