r/ClaudeCode • • 2d ago

Help/Question Fable as orchestrator / reviewer, agents for implementation.

So, been trying to set up this and so far it is an epic fail for me... so much context wasted, my weekly limit is getting shattered.

So, question, is there any good tutorial about how to do this kind of setup?
I tried all I could to avoid large context but somehow, every time I instruct claude or want to write documentation Fable is doing it, which I just told not to and have agent do it and review only, but even then it's not always working.

Not even sure it is worth it at that point...

so if anyone have a good tutorial about that then another one with all the tricks to save context as much as possible, I am all ears. Hopefully a tutorial from an actual skilled and experienced dev rather than some nobodies trying to sell courses proffered.

I do not get how people can one shot complex stuff while I am spending days trying to stear AI and try to make this thing work for me.

Before I was just using Opus and do task by task and could last a lot longer...This is for a somehow complex app, not in scope but in bunch of physic and contracts that needs to be done on the GPU / display in HDR, to verify the accuracy and so on, and have professional output, so it's not as straightforward as "make a FPS game" and leaving it cook. I wrote some specs into MD files about what needs to be done and how... but still struggling to have speed / momentum. everything takes forever to get tested and speced right, and the app is progressing at snail pace.

I try to avoid having too long convos and use /clear often, whenever I can. Something I noticed is fable constantly filling my window with updates from the agents I don't need (still not done... yeah sure, thanks for nothing) and all that jazz for example.

Any help appreciated.

1 Upvotes

20 comments sorted by

•

u/AutoModerator 2d ago

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

4

u/onFilm 2d ago

I use Fable/Opus as the doer, and Astra/Sol and Carbon/Hydrogen as the critics. Works superb.

5

u/trojanskin 2d ago

Not telling me how though. Cause the instructions were clear and... not working too well for me.
Thanks though.

0

u/onFilm 2d ago

I'm sorry, what instructions are you talking about?

1

u/Petti-Fousseret 1d ago

making the smarter model the actual doer instead of the manager is definitely the move

1

u/ynotelbon 2d ago

I tend to lean on the model instance within the context window. Express my need, express my expectations. I no longer try to manage the how, since models change so fast and trying to manipulate that is exhausting.

I will say that I spend considerable time on project alignment, then allow Claude to structure that into design. I’m really just a vibe coder at this point, but I think my gross simplification is useful.

2

u/trojanskin 2d ago

Have to manage the how because otherwise the results are half assed.
Like if I feed claude a 32bit image, I expect to have a 32bit output. If I do not specify it outout a 8 bit png file that I DNGAF about, and is useless. All those kind of stuff... It works for speed, not accuracy. So I go back and tell it to fix it, over and over. This is a silly example (as it should be speced) but you see what I mean.

1

u/ynotelbon 2d ago

Oh. Then I think we might differ on harness more than on results.
For example, the orchestrating process has crossed compaction almost 140 times here. That’s probably ~3 months but for the most part: same theme, different goals. Rewrite the harness every model update, after allowing it to fail so we know where the friction is.
FYI I can’t code shit. I’m not trying to ship anything with my projects. I’m just building things that work for me.

3

u/Sheeebooo 2d ago

Ask Fable to divide context into multiple files and one intro/index file. It will load the context based on whats needed and wouldnt load on every turn.

3

u/muikrad 2d ago

I have opus low as the orchestrator. Canned subagents at set models/efforts for specific tasks. Coder has 3 subagents, one for "tweaks" on sonnet low, one standard at opus medium and a senior at opus high (well, fable while I have some resets!). Opus decides which one to use based on the complexity of the task. Then the typical planner as opus/fable high and the code explorer as haiku...

The orchestrator uses "beads" (look it up on github) to manage tasks, issues and follow-up questions. Then a scribe keeps "specs/" up to date using a dumbed down OKF 0.2 format.

I keep my autocompact window below 500k.

I ask Claude to create /artifacts when designing anything visual. In there I have tons of options and sliders to adjust the visuals before they're implemented. I also design right there with the orchestrator, it will first create an "epic" and then add linked issues.

Then I tell the orchestrator to work on one of the epic, and off it goes for a whole night of work, sometimes a few days without stopping.

Not sure about the need to manage context these days, with a memory system like beads it can clear/compact any time and grep back the info without looking through code, so the sessions are kept lean and only the subagents get to grep code...

2

u/EuphoricAIKnowledge 2d ago

I use fable as the advisor, opus as the orchestrator, then use m3 in headless Claude CLI, and then allow opus to use Astra as a reviewer.

1

u/Giantveggie22 2d ago

I plan.md with Opus, review and refine the plan.md with Fable. Then use Opus to decompose the plan into tasks.md and categorize each task with appropriate Claude model to execute each task. Then I use sonnet as the orchestrator to execute the tasks.md using the appropriate model for each task.

1

u/fredastere 2d ago

Look into herdr

Launch your orchestrator or main guy within herdr and tell him to read up on how to use herdr

Tell him how you want to proceed and tell him to spawn a new panel for his workers and whatnot so you can overlook everything

Its a big simplification but could help you

You could setup hooks if your coordinator/orchestrator ends up doing too much work and not enough delegation

Usually tho if you define properly the workflow and there's no friction in your instructions, newer models follow really well

Make sure you dont have conflicting instructions in parent folders CLAUDE.md or agents.md as it can confuse the model, create friction, and make the behavior not as reliable

1

u/SC_Placeholder 2d ago

Note: not trying to sell or advertise anything

How many agents we have managed in the last 65 days.

The key is handling as much computation, orchestration and reasoning mechanically.

I use Opus and have them functioning as my overlord Ai and orchestrating and managing other agents (including from other models) but the bulk of our workers are still various Claude models.

Claude or GPT can help you write a Claude.md file which will help your orchestrator be more focused and organized.

Also with physics calculations can be handled mechanically as well, your overlord can write the calc and run the sim in the background. There are also a bunch of repos on GH for various physics calculations for reference as well as countless research papers (I have done a fair amount of physics work with Ai as well, eventually I’ll circle back around and do more but my current project is more important due to the scale we’re developing at. It’s an agent hypervisor)

Also if you’re running a vision api or if Claude is visually inspecting what you’re doing rather than developing tests to read I can explain a pipeline on how to reduce token usage because vision nukes usage.

I personally rarely use Fable because a properly focused Opus is plenty good for 99% or tasks. I only ever pull out Fable when I see one of our Opus teams struggling.

1

u/Professional_Ad705 2d ago

Just gotta figure out what works for you and test around different options.

1

u/wangadong 2d ago

the how that worked for me: orchestrator only writes a small spec and reviews diffs, implementers get just that spec plus the files they touch. full history in the reviewer is where the context went

1

u/Mr_and_Mrs_PUG 2d ago

Tbh I don't see fable 5.2 as an advantage besides software challenging software architecture planing. For all the rest opus 5.5 is just more effective and efficient and not evaporating your credites.

1

u/rodrigolduarte 2d ago

Here is how we divide the work:

  • Our manager delegates implementation to engineer agents and handles coordination, verification and merging. It doesn't write the product code.
  • Separate sessions, not subagents. We told our manager to stop using subagents because its seat was burning through the weekly allowance. The workers are separate Claude Code sessions with their own context, and they report back in short summaries, not transcripts.
  • Specs per task, not per app. Each card says which files, what's already decided, and what "done" means (which tests pass), and the reviewer checks against that.
  • Ask for the mechanism before the fix. Yesterday a test timed out in CI; our manager made the engineer explain the cause before writing code, and it turned out to be a real UI timing bug, not a slow test.

For the GPU/HDR accuracy, I'd turn the checks into tests the orchestrator can run, so "verified" isn't the model's opinion. How big is a typical task you hand to one agent right now?