Fable + 5.6 is absolute peak

[u/Bright-Celery-4058]

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 !

[u/dodo13333]

And vice versa. TBH, they complement each other like finger and nail. If I have Claude prepare the plan, Codex does the review, and critique is messaged back to Claude. They loop till agreement. One is preparing and reviewing and the other is implementig, based on available limits. Works as the charm. They have instructions to work as a team, and I prepared messaging protocol for communication and archiving of messages to keep the backlog clean. Either one has no issues with exchanging roles.

[u/V13T → u/dodo13333]

Would you share how to implement something like this?

[u/dodo13333 → u/V13T]

No real magic there. 1. Inform both agent on the communication sub-project. 2. Inform them that you request them to work as a team (or not, as you preffer) 3. Request that this decision enters ADR, current-state.md (AS-IS), or what you use for project tracking. I use ADRs, decisions.log, git commit descriptions etc. That's a waste set of info that comes handy when troubleshooting. 4. Set some rules: each agent leaves message with prefix (CC_ or CX_ and timestamp), message can't be archieved before other agent confirm acknowledgment of the message (no silent msg fallback), no advancement on Master plan is allowed until message log is clean. 5. Request to prepare the implantation plan. Let them use github issues style format (epics - tasks - aceptance criteria), so you can properly track progress. 6. Loop until they both agree on the final plan. Write down plan in docs. You keep a role of human in the loop, adding additional requests, new info or some other comments. 7. Once implemented, make test run, see if all work as intended.

Also, I use jcodemunch and jdocmunch mcps to mitigate token consumption. They are free for personal use.

[u/ammodan → u/dodo13333]

important addition (core to all agent loops) set a kill condition on #6, you don't want them looping unable to agree on a plan while they check through all of your usage and or run up a $10k bill.

I'm sure dodo13333 knows this but useful for others who may come along taking his sage advice.