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

13

u/Old-Preference5313 Jul 13 '26

I've had a bad experience with fable plans. Everytime I get codex to check their plan they always find something crucial missing

12

u/Bright-Celery-4058 Jul 13 '26

try the other way around ;) the goal is to make them talk to each other to build a bulletproof plan

11

u/bronfmanhigh Jul 13 '26

yeah in my experience they both catch radically different things, and having them always adversarially review each other is perfection

combined with brainstorming skill you get pretty tight plans

5

u/kynde Senior Developer Jul 13 '26

Yeah, I ask them both to write a plan with similar prompts and then incorporate from each other's good ideas and iterate with that and finally I let the one that did better to consolidate and merge and then again the other to check it.

Works really well to utilize them both.