1/ Smithers is the best Orchestrator and you should try it What is Smithers Smithers is an Orchestration framework where you declaratively create a DAG of Durable Tasks as xml and reactively regenerate parts of that DAG as Tasks complete How do you use it You use it as a CLI or a agent skill. Your agent then writes, updates, and monitors those scripts What special features does it have - MDX for prompts - Library of prebuilt 0-config workflows - All workflows represented as code that is easy to modify, customize, or compose into larger workflows - Built in observability with SQLLite and pormetheus - Supports Claude code, Codex, Gemini, and Kimi subscriptions - Supports all harnesses including Claude Code, Codex, Pi, and Opencode - Supports Agent SDK Why is it so good? The main reasons Smithers is so good is 1. Agents are great at writing complex workflows because Agent's are great at React 2. It is thoughtfully built with @EffectTS_ Durable execution primitives enabling more reliability for very long running agentic tasks 3. Powerful CLI for watching and interacting with wrokflows 4. MDX is a really great existing standard for expressing prompts 5. The declarative nature of Smithers and it's great observability makes it very easy to read and quickly reason about What is best way to get started? bunx smithers init in an existing project and try it out Alternatively check out the docs smithers.sh

I have cancelled 90% of my codex subscriptions and half of my claude subscriptions because of the relative savings opus is giving me

Smithers 2 has it's own Agent implementation. It makes chat gpt powered agents cheaper while being a tad bit smarter and faster too These benchmarks are with all Jev functionality disabled. Excited to see what the final benchmark numbers come out to with Jev