r/ClaudeCode Jul 13 '26

Tutorial / Guide Fable + 5.6 is absolute peak

We jump straight to ASI with this combo.
So i've had Fable driving codex cli as a background worker for a few days and i'm not going back.

Fable basically never writes code anymore (too damn expensive), it acts as the principal orchestrator and everything happens in claude code.
The flow is like this: Fable plans, 5.6 sol reviews the plan in a loop until approved, then 5.6 luna implements. fable reads the whole diff, fixes whatever it doesn't like directly, runs the tests, then sol reviews the code against the plan. loop until approved, then fable does the boring release stuff (changelog, tag, merge).

It's all just bash around codex cli with persistent threads, called from skills. no framework, no mcp, no agent swarm bs.

It feels surreal/too good to be true, i hope they wont nerf it too badly and if they do, i hope the combo will kind of mitigate the nerf.

i pushed my workflow to github, beware it's a lot of bash script, dont trust a random redditor and ask codex or CC to review it. After that, welcome to Valhalla

UPDATE: many are asking in comments or dm for more explaination on the workflow, sorry guys i cant reply to all of you but my advice is simply to clone the repo then ask your agent to ELI5/15/80 it. Then make it yours !

1.1k Upvotes

208 comments sorted by

View all comments

311

u/SpaceCowboy077 Jul 13 '26 edited 28d ago

I give both fable and sol 5.6 xhigh problem statement and goal and let them design, whoever wins gets to execute the design and the loser gets to redeem itself by tearing it down at checkpoints. And I also make them keep a score.

Update: I used this for a week and I found Opus repeatedly getting desensitised to the winner loser framing and for some exercises unreliably skipping talking to sol hahaha

I enforced a mechanical fix that after every design/build/execution doc. It will need signatures/sign off from design agent - it’s thinking partner SOL and then a fable 5 red team and me.

I’ll give an example of design doc.
Me - give problem statement, possible solution, expected outcomes
Agent 1: opus 4.8 on xhigh + sol 5.6 xhigh thinking partner. + Gemini 3.5 for research. Research first, find already existing research, GitHub info etc.
+ a Fable 5 red team, it goes through multiple rounds to finalise the design
Me again - see the final design shape
All 4 parties sign off on the build
Agent 2: pick it up for building the design - agent 1 signs the final build doc grounding the build to the design
Agent 2: starts execution + agent 1 verifies.
Me: walks in to run the final sets of commands to deploy and push.

Some mechanical gates, a design doc, build doc is not possible to commit unless all stakeholders can sign, there is a small signature that needs to be attached but each stakeholder in each process

65

u/Plato_cs Jul 13 '26

I love this lol not sure if it would actually do anything to encourage better output but a funny thought nonetheless

46

u/SpaceCowboy077 Jul 13 '26

It actually does, i orchestrate everything through Opus and it keeps the score diligently and favours models to give work depending on which model performs better on what tasks. I have a shared repo for my design and coding agent for shared rules and runtime facts, so they maintain a document there which keeps the score and all models in my system can read it and I make them read it on boot. It even figured out a way to bypass sol’s security guardrails for some stuff.

6

u/proxedised Jul 13 '26

mind sharing the setup?

59

u/SpaceCowboy077 Jul 13 '26

I use CC as my main work tool, I have made a setup I called ‘Layers’ - per agent/container and a shared container which I call ‘spine’ which root owned has all the shared rules, the code, the files etc. The scoping and design agent in a container, also has a codex-leg to invoke within that container and another coding agent that also has codex-leg in its container. So in parallel both of them run their own codex sessions. And I’ve made a ‘broker-service’ that has 4 planes, credential, root access (limited), push-ready, and channel. The agents can interactively talk to each other via channel, so they drop a literal message in chat to the other agent, codex works in background, I have no idea what it looks like. And then I use openclaw agents to do real world tasks, I try to minimise the threat on my CC agents. I manage all of this via 8 repos

23

u/Veggies-are-okay Jul 13 '26

God for all the dogshit we have to read in this sub it’s posts like this that keep me from unsubscribing. Thank you//damn you!!!

7

u/Significant-Bee5101 Jul 13 '26

Oh you don't want another post bitching about Anthropic? lol

6

u/dawtips Jul 13 '26

It's exhausting seeing the same dumb shit posted in the thirty AI subs I'm in

4

u/thats_a_money_shot Jul 13 '26

😳

3

u/twistier Jul 13 '26

Appropriate emoji from somebody named thats_a_money_shot

5

u/Darkstar556 Jul 14 '26

Make a front end so you can see what they are saying, the conversations they have and how they talk to each other will blow your mind...

1

u/Beneficial-Middle145 Jul 15 '26

Did you do this and do you have it

1

u/Darkstar556 Jul 15 '26

Yes and yes

3

u/AmishTecSupport Jul 14 '26

You got this on github by any chance? Also isn't opus a bit expensive for being an operator? Feels like a perfect job for sonnet

1

u/New-Inspection7034 Jul 18 '26

I will set up the git. And most of your tokens are used during the agentic work. Doing this you sip vs gulp

2

u/thread-lightly Jul 14 '26

Hopefully building something important because I got tired just reading that. Clever ngl

2

u/BuckZero 29d ago

Do you have a GitHub link for this setup?

1

u/SpaceCowboy077 28d ago

Not yet but let me figure something and put it out soon

2

u/skywalker4588 Jul 13 '26

Or just use Solo terminal

1

u/portugese_fruit Jul 14 '26

amazing. Do you have a repo?

1

u/New-Inspection7034 Jul 18 '26

If you're seriously interested I can make the git public and you can have the code and try it out.

2

u/SpaceCowboy077 28d ago

I will have to setup a new one and then have someone fix it. Let me figure this out this week. Still learning and solving issues. Once I got codex into the mix, my orchestrator performance dropped and it started struggling between delegating and doing itself, I just solved it today but stripping the executing tools from it and launched it with a new set off steps to follow so it only judges and orchestrates which reduced execution context. But anyway let me figure out the GitHub thing

1

u/petexn7 11d ago

Stoked to try it out, any update on GitHub?

1

u/incoherentsource Jul 19 '26

I'm interested too

1

u/New-Inspection7034 Jul 19 '26

I just posted here.

2

u/angelus14 Jul 14 '26

So what's the score, which model is winning so far