Tmux + Fable = Cut 35% less token
In a Nutshell
Use a Fable 5 orchestrator to plan and delegate execution to persistent Sonnet 5 sidekicks instead of spinning up fresh sub-agents. Persistent sessions let the executor inherit full context at cached-token prices, cutting cost 35% versus one-shot sub-agents. Wrap any agent (Cloud Code, Codex, Gemini CLI, etc.) behind Tmux-orchestrated “Open Agent Teams” so you can run the same coordinator-worker pattern across every harness.
These notes were generated by AI and may contain inaccuracies.
Cloud quota burns out quickly when Fable 5 or GPT-5.6 So Max is used directly for all tasks. These frontier models are powerful but expensive and slow. The recommended practice is to use Fable 5 as the advisor or planner while using smaller models like Sonnet 5 as the executor. Sonnet 5 costs only 20% of Fable 5 but delivers performance nearly equivalent to Opus 4.8, the strongest model from a few months ago.
Cloud Code officially demonstrates two methods. The first approach uses Sonnet 5 as the main executor agent and only calls Fable 5 as an advisor to review plans and provide advice. The second approach uses Fable 5 as the main agent that creates a plan and spins up worker agents using smaller models for execution.
Devin introduced a new harness called Devin Fusion that achieves similar or better performance than Fable 5 with 35% lower cost. Devin Fusion is fundamentally Cloud Code's Fable 5 orchestrator plus Sonnet 5 worker model. Devin compared the two Cloud Code methods and found that the Fable 5 orchestrator model works significantly better because advisor models require reading the full conversation history from the main agent rather than triggering cached context. Cached tokens cost only 10% of new input tokens, making the orchestrator approach more cost-efficient.
Devin refers to persistent sub-agents as sidekicks. Traditional sub-agents in Cloud Code or Code X create new sessions on the fly, and when the main agent needs to make edits, a new task tool spins up a fresh sub-agent with no prior context. This wastes tokens by rewriting the same information repeatedly. Sidekick sessions are persistent, so follow-up messages from the main agent inherit all past context. Since cached tokens are extremely cheap yet powerful, this approach provides full context at minimal cost.
Sign in to read the full notes
Get access to AI-generated notes, topic timestamps, and more.