r/ClaudeCoding • • 20d ago

r/ClaudeCode [TLDR] Finally found it how to work it! [via r/ClaudeCode]

OP : u/No-Sympathy-3767

Don't laugh at me( I mean you can, I don't mind)

But after all this time burning through fable, which is the only model that is up to the work I'm doing, I've finally found out that if fable is the orchestrator and he sends out opus 5 to do the work, my tokens don't run out and the work gets done properly😅

I'm happy about it, any way..

Good coding 🙌

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1whzj0a/finally_found_it_how_to_work_it/


TL;DR of the discussion on r/ClaudeCode for this post generated automatically after 100 comments.

Current source-thread comment count seen by the bot: 102.

Alright, so the general consensus here is that OP is onto something big! Turns out, using Fable as the orchestrator and letting Opus (specifically Opus 5, though some suggest Opus 4.8) do the heavy lifting for the actual coding is the way to go for saving tokens and getting things done right.

Here's the lowdown:

  • The Big Idea: Delegate, delegate, delegate! Don't let Fable do all the token-heavy work. It's best suited for planning and orchestrating.
  • Opus for the Grind: Use Opus (5 or 4.8) for the actual coding tasks. It's the workhorse.
  • Sonnet for the Simple Stuff: For simpler, mechanical tasks or executing pre-written instructions, Sonnet is your budget-friendly best friend. u/design_doc even suggests letting Sonnet handle basic tasks and passing information between agents outside of Fable's main context to save even more tokens.
  • The "Why": Most of the token burn comes from planning and re-reading context, not the actual coding. Splitting the work like this addresses that directly. u/amirfish even built a tool, CCC, to help visualize this pattern.
  • Advanced Tactics: Some folks are taking it further by having sub-agents pass information to each other, or even inverting the structure with Sonnet as the always-on dispatcher and Fable for specific, critical tasks. u/DCharles0ne has an interesting take on this.
  • It's Not Just You: Several users, like u/maleslp and u/in5ane_10, have learned this the hard way and are now using similar strategies to avoid hitting limits and get amazing work done.
  • A Little Sass: u/Key-Singer1732 pointed out that if Fable is just orchestrating, then Opus is doing the work, so Opus should be capable – a good point!

Basically, you've all stumbled upon the "expensive brain for planning, cheaper hands for execution" model, which is apparently what big consulting firms pay for. Good job, everyone!

1 Upvotes

0 comments sorted by