4 ms·
Anthropic[0] and Google[1] are both pushing for a clear definition of an “agent” vs. an “agentic workflow” tl;dr from Anthropic: > Workflows are systems where
by jumploops 2y ago
Anthropic[0] and Google[1] are both pushing for a clear definition of an “agent” vs. an “agentic workflow”
tl;dr from Anthropic:
> Workflows are systems where LLMs and tools are orchestrated through predefined code paths.
> Agents, on the other hand, are systems where LLMs dynamically direct their own processes and tool usage, maintaining control over how they accomplish tasks.
Most “agents” today fall into the workflow category.
The foundation model makers are pushing their new models to be better at the second, “pure” agent, approach.
In practice, I’m not sure how effective the “pure” approach will work for most LLM-assisted tasks.
I liken it to a fresh intern who shows up with amnesia every day.
Even if you tell them what they did yesterday, they’re still liable to take a different path for today’s work.
My hunch is that we’ll see an evolution of this terminology, and agents of the future will still have some “guiderails” (note: not necessarily _guard_rails), that makes their behavior more predictable over long horizons.
[0]https://www.anthropic.com/engineering/building-effective-agents https://www.anthropic.com/engineering/building-effective-age...
[1]https://www.youtube.com/watch?v=Qd6anWv0mv0 https://www.youtube.com/watch?v=Qd6anWv0mv0
- zh2408 2y agoLet me clarify: we are discussing how the Agent is internally implemented, given LLM calls and tools. It can be built using a graph, where one node makes decisions that branch out to tools and can loop back. The workflow can vary. For example, it can involve multiple LLM calls chained together without branching or looping. It can also be built using a graph. I know the terms "graph" and "workflow" can be a bit confusing. It’s like we have a low-level 'cache' at the CPU level and then a high-level 'cache' in software.
- jumploops 2y agoYes, the difference is that in the “pure” agent approach, the model is the only thing directing what to do. In a sense there’s still a graph of execution, but the graph isn’t known until the “agent” runs and decides what tools to use, in what order, and for how long. There is no scaffold, just LLM + MCP (or w/e) in a loop.
- zh2408 2y agoYes!!