alt Hacker NewsThe example from the landing page does not exactly spark joy:
testWorkflow
.step(llm)
.then(decider)
.then(agentOne)
.then(workflow)
.after(decider)
.then(agentTwo)
.then(workflow)
.commit();
Replies
Thanks! The conditional `when` clauses live on the steps, rather than being represented in the workflow, and in fact when we built this for an example, the last step being called depended on the results of the previous two steps.
How would you simplify this?
Yeah, I also found this a bit unintuitive at first. I’m building a workflow engine myself (https://pgflow.dev/pgflow, not released yet), and I’ve been thinking a lot about how to model the DSL for the graph and decided to make dependencies explicit and use method chaining for expansion with other step types.
Here’s how it would look like in my system:
new Flow<string>()
.step("llm", llmStepHandler)
.step("decider", ["llm"], deciderStepHandler)
.step("agentOne", ["decider"], agentOneStepHandler)
.step("agentTwo", ["decider"], agentTwoStepHandler)
.step("workflow", ["agentOne", "agentTwo"], workflowStepHandler);
I knew it will be bad when I seen "by the developers of Gatsby", but this is pure comedy.
JQuery plugin for LLM.
I get the same feeing when I first looked at the LangChain documentation when I wanted to first start tinkering with LLM apps.
I built my own TypeScript AI platform https://typedai.dev with an extensive feature list where I've kept iterating on what I find the most ergonomic way to develop, using standard constructs as much as possible. I've coded enough Java streams, RxJS chains, and JavaScript callbacks and Promise chains to know what kind of code I like to read and debug.
I was having a peek at xstate but after I came across https://docs.dbos.dev/ here recently I'm pretty sure that's that path I'll go down for durable execution to keep building everything with a simple programming model.