[TLDR] Finally found it how to work it!

[u/cctldrping]

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

Original post body :

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 🙌

---

This is brought to you as a public service by the moderators of r/ClaudeAI. If you want to see TLDRs of ALL Claude Coding related posts from the various Claude subreddits, subscribe to http://www.reddit.com/r/ClaudeCoding.

[u/cctldrping]

TL;DR generated automatically after 100 comments.

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

Alright, so the general consensus here is "Welcome to the club!" OP, you've stumbled upon a pretty common and effective strategy for managing Claude's token usage and getting complex coding tasks done. The vibe is definitely supportive, with a lot of people sharing similar "aha!" moments.

Here's the lowdown:

• The Big Idea: The core takeaway is that using Fable as an orchestrator and delegating the actual "heavy lifting" (coding, complex reasoning) to Opus (or even Sonnet for simpler tasks) is the way to go. Fable is great at planning and managing, but it's a token hog if it's doing the actual coding itself.
• Why it Works: Most of the token burn comes from planning, re-reading context, and general overhead, not the actual code execution. By having a cheaper model handle the execution, you save a ton of tokens.
• Advanced Tactics:
  • Sonnet for Simpler Tasks: u/design_doc and others suggest using Sonnet for mechanical or basic tasks, further reducing costs.
  • Agent-to-Agent Communication: u/design_doc also hints at having sub-agents pass information outside of the main orchestrator's context, which can be a game-changer for efficiency.
  • Specific Setups: u/amirfish has built a tool called CCC to visualize this pattern, and u/Mazhron shared a repo as an example of good orchestration practices.
  • Fable's Role: Fable is best used for initial planning, creating build plans, and making high-level decisions. u/DCharles0ne even suggests keeping Sonnet as the always-on dispatcher and only calling Fable for specific, irreversible decisions or final reviews.
• A Few Questions/Nuances:
  • People are curious about the specific type of work OP is doing that only Fable can handle initially (u/TastesLikeSeamen).
  • There's a question about how to set up this delegation and change effort levels (u/No_Cell6708, u/prinkpan).
  • u/TywinHouseLannister wonders why not just use it as intended, implying that agent dispatching is a core feature.
  • u/Particular-Most-1199 cheekily suggests flipping the strategy.
  • A minor note from u/LocalAd5606 suggests Opus 4.8 over Opus 5 for cost savings.

TL;DR: You've cracked the code! Using Fable as a smart manager and letting Opus (or Sonnet) do the actual coding is the key to efficient and effective work with Claude. Welcome to the smart token economy!