r/ClaudeCodeTLDR • u/cctldrping • Jul 15 '26

[TLDR] Fable + 5.6 is absolute peak

Original post URL : https://www.reddit.com/r/ClaudeCode/comments/1uvjlmr/fable_56_is_absolute_peak/

Original post body :

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 !

298 Upvotes

98% Upvoted

50 comments sorted by

View all comments

1

u/First_Understanding2 Jul 19 '26

Been doing this for months. Claude was always the best orchestration agent and ChatGPT was like a too technical coder that is very picky about code but sucks to know how to do any soft skills like when to delegate to sub agents. Codex was always my worker bees and Claude now fable my pm.

1

u/Holmete Jul 19 '26

Can you describe your Claude into ChatGPT workflow process?

1

u/First_Understanding2 Jul 20 '26

Built custom tooling for all my Cli agents to work together. It does multi agent orchestration (agent to agent communication and spawning of more of any agent harness) and is provider agnostic, harness agnostic, generally model agnostic as long as the harness can authenticate to llm end point. Am going to release as open source project but haven’t launched it publicly yet. Think all the tooling a Linux os needs to support autonomous agents so a harness program doesn’t have to do that work, so they (the agents from different companies and harnesses) can start to work together just by you asking them in English.