Most of my workflows have slowly moved away from the chat interface with llms. Instead they look more like traditional Unix pipelines that just happen to call Unix tools that interact with llms.
This allows me to make more repeatable processes, not be tied down to vendor implementations of workflows and mix and match models for cost and efficacy.
There is nothing that ties you to talking with the text generator black box, and for most of my use cases it’s a negative.
Would you provide some examples? It sounds like you're feeding results from one LLM into another LLM invocation. Kind of like the loop thing everyone's talking about, but more like a workflow. Or programming with LLMs
In the simplest incarnation I’m just using the built into the agent cli parm’s that trigger non-tui behavior (for instance calling codex exec instead of just codex).
Comments
Most of my workflows have slowly moved away from the chat interface with llms. Instead they look more like traditional Unix pipelines that just happen to call Unix tools that interact with llms.
This allows me to make more repeatable processes, not be tied down to vendor implementations of workflows and mix and match models for cost and efficacy.
There is nothing that ties you to talking with the text generator black box, and for most of my use cases it’s a negative.
Would you provide some examples? It sounds like you're feeding results from one LLM into another LLM invocation. Kind of like the loop thing everyone's talking about, but more like a workflow. Or programming with LLMs
In the simplest incarnation I’m just using the built into the agent cli parm’s that trigger non-tui behavior (for instance calling codex exec instead of just codex).