We have been using a lot of CLI Code Agents, and wanted a way to both standardize their configurations across providers & create sequential workflows throughout providers. Thus, Opun was born.
Realized I didn't give a great description, been traveling too much - here's a better shot:
Opun is a Terminal Development Kit - a wrapper for Terminal Development Environments (TDEs), providing a standardized configuration across environments through a unified MCP, Promptgarden, Tool / Action interface & more. This is enhanced via a community-driven remote manifest configuration architecture.
Additionally, Sequential Workflow Automation means you can save repeated multi-instance workflows you might use consistently (across providers). One command, multiple agents run in sequence, passing context between each other to achieve a consistent goal.
These are all configured via YAML templates that are incredibly easy to understand.
PS. I recorded a video to better demo the workflow orchestration. Find it here.
Realized I didn't give a great description, been traveling too much - here's a better shot:
Opun is a Terminal Development Kit - a wrapper for Terminal Development Environments (TDEs), providing a standardized configuration across environments through a unified MCP, Promptgarden, Tool / Action interface & more. This is enhanced via a community-driven remote manifest configuration architecture.
Additionally, Sequential Workflow Automation means you can save repeated multi-instance workflows you might use consistently (across providers). One command, multiple agents run in sequence, passing context between each other to achieve a consistent goal.
These are all configured via YAML templates that are incredibly easy to understand.
PS. I recorded a video to better demo the workflow orchestration. Find it here.
Smoopit
The context passing between agents is intriguing. How do you handle error handling when one step in the sequence fails? @sam_rizome