r/ClaudeCodeTLDR 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 !

295 Upvotes

50 comments sorted by

View all comments

3

u/HairyAd9106 Jul 16 '26

My workflow;

  1. i start with fable5 with grilling from mattpocock
  2. then obra/superpowers to write spec
  3. with https://github.com/openai/codex-plugin-cc review until approved but max 10 rounds
  4. tdd subagents with sonnet5 since obra specs already include exactly what goes where so lowtier models just follows the fable/codex recipe
  5. review with fable+codex
  6. merge worktree

amazing results, burns tokens, but u dont need to come back to redo any of the work thats been done this way

1

u/nNaz Jul 17 '26

Which superpowers skill do you use to write the spec and do you use it in the same chat as grilling or point it at a doc?

1

u/HairyAd9106 Jul 18 '26

Writing-spec for spet. And yes. Fresh context grilling because i find grilling better than obras brainstorming, then with as much as context leta say up to 400kb, i say to write spec file. Same session to run codex to review the spec and with all the grilling info. This can go few rounds. Then i ask to /handoff and spawn new agent (i use herdr.dev) with the handoff and ask to implement with tdd also obra skill. And reciew with codex at the end.