Hacker News Reader

>The problem with all of these AI specific workflow engines is they are not durable, so they are process local, suffer crashes, cannot resume, don't have good visibility or distribution, etc. They often only allow limited orchestration instead of code freedom, only one language, etc

So what's the solution?

My biased answer, because I work at Temporal[0], is to use an existing workflow solution that solves all of these problems instead of reaching for a solution that doesn't help with any of these but happens to be AI specific. Most agentic AI workflows are really just microservice orchestrations, the only "AI" involved is prompting an HTTP API that uses AI on its end. So use a good solution for "agentic X" whether that X is AI or any other orchestration needs.

0 - https://temporal.io/solutions/ai

It’s only a true agent if it chooses what to eat for breakfast everyday.

"Workflow can be very dynamic" is a great summary!

What about workflows are not agents?

To me, a workflow is a predetermined set of steps that are followed based on fixed logic. Agents should have some agency to determine which steps in the workflow to perform next, without them being predetermined by fixed logic.