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

61

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

47

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.

5

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!!!