Reduce Fable tokens by 80%, simply by not using it!

> I am fairly convinced this is the shape serious agent work keeps converging toward.

"this" being "plan with expensive model, implement with cheap model".

Anyone who follows HN would be hard-pressed to disagree; this architecture is re-invented twice monthly.

https://www.facebook.com/groups/vibecodinglife/posts/1946207... https://github.com/openai/codex/discussions/10628 https://build5nines.com/stop-burning-premium-requests-how-to...

> Not because it is aesthetically pleasing. Because every other shape eventually runs into the same boring failures: context rot, self-grading, goalpost drift, and merge chaos.

Actual failure isn't boring. But struggling through a generated software project that celebrates its own genius and doesn't have a single self-critical or genuinely reflective thing to say...at least watching paint dry I might get giddy off the fumes.

I'm not interested in critiquing the project itself, either, you'll just run that through a model, too.

>https://www.facebook.com/groups/vibecodinglife/posts/1946207...

wow linking a facebook groups post might actually be worse than x, is there an xcancel alternative for facebook?

I don't disagree with any of this. It is generated software, and it's not a novel idea. I didn't mean for it to come off like that. It's just solving an itch that I couldn't find a solution to and I'm getting a lot of personal utility out of it. I do have a lot of experience with agentic memory, multi-agent systems and harnesses and wasn't super impressed by the workflow of Fable calling opus subagents so I figured I'd apply best practices to what already exists to make it a teensy bit better and easier to use.