Greate content, thanks a lot for sharing. I have one side comment, afaik what you refer as workflow is what I it is known as a static workflows (a workflow whose steps are hardcoded). This comment comes from my experience with workflow orchestrators, because an AI agent can be underestood as a dynamic workflow where LLMs are called on tasks and the tasks to be executed are defined on runtime based on the output of LLMs tasks, for example, this video explains how to implement an agent loop with temporal (https://youtu.be/s58zhw9XpEQ?si=cwYL8OwHThgPtun9).
I may be wrong, but any setup of AI agents can be reproduced with a workflow orchestration engine if it supports the following features:
It's a simple yet informative article. Thanks.
Excited to hear that! More incoming
Thanks for the elaborate walkthrough for the good 😊
Always 🙏
Informative article! But first few paragraphs repeated twice haha
Thanks! Substack duplicated them when adding the images. Fixed
Greate content, thanks a lot for sharing. I have one side comment, afaik what you refer as workflow is what I it is known as a static workflows (a workflow whose steps are hardcoded). This comment comes from my experience with workflow orchestrators, because an AI agent can be underestood as a dynamic workflow where LLMs are called on tasks and the tasks to be executed are defined on runtime based on the output of LLMs tasks, for example, this video explains how to implement an agent loop with temporal (https://youtu.be/s58zhw9XpEQ?si=cwYL8OwHThgPtun9).
I may be wrong, but any setup of AI agents can be reproduced with a workflow orchestration engine if it supports the following features:
- workflows are stateful processes
- workflows can interact with other workflows
- external services can interact with workflows