Hacker News new | ask | show | jobs
by all2 13 days ago
What you are describing is precisely my goal with my agent framework.

One of the meta-processes designed in is pushing automated processes, both defined and discovered, down as far as possible. "Down" here means as far towards the metal as reasonable. So automate the automatable stuff, and leave the LLMs to do stuff LLMs are actually good at.

A trivial example is 'handle this bugfix ticket'. Many actions in a bugfix are pre-defined, for example a git commit at the end of the ticket. So Maelstrom will, at the end of a bugfix workflow, will force a git commit from the LLM that did the implementation. The LLM never even sees the git command, it just fills in a JSON field with a commit summary, and the workflow handles the commit.

1 comments

Yes, this is how I am building my agent as well. A chain of mostly deterministic steps for every incoming prompt. Run as many tools without help of LLMs, gather errors - feed to LLMs, then go back to deterministic steps as soon as possible.