jwbron
Qwen comes close to opus for planning but fable is clearly superior. Results for kimi and deepseek are pretty much indistinguishable from opus for coding if opus writes the plan. The biggest difference is output cadence. Kimi for example thinks for a long time then quickly outputs a lot of text.
I'm now testing out fable for research and planning and deepseek v4 flash for coding. I'm guessing results will be pretty similar to opus + deepseek v4 pro and costs should be lower overall.
Qwen comes close to opus for planning but fable is clearly superior. Kimi and deepseek are pretty much indistinguishable from opus for coding if opus writes the plan.
I'm now testing out fable for research and planning and deepseek v4 flash for coding. I'm guessing results will be pretty similar to opus + deepseek v4 pro and costs should be lower overall.
I copied it for my own tooling to make it work a bit better for my workflows.
Egg: Intentional Agentic Developement
It's comprised of what I'm calling "agentic feedback loops" https://github.com/jwbron/egg/blob/main/docs/agentic-feedbac... and "human feedback loops". There are three phases of "agentic feedback loops", which do work, review the work, and repeat until consensus is gained: refine, plan, implement (this also has an automatic merge conflict fixer, can run checks like test and lint, and has an autofixer. The contract is enforced in this stage)
Each phase has a human checkpoint in between. The human reviews the work, makes manual changes or iterates with claude, then approves. The final check is a human PR review. I'm finding that if I focus energy on refining the initial task, I always approve the review on the first pass. If the requirements are properly defined, they are enforced in the contract. This is managed by phase-based access controls. Coders can't alter the contract, contract validators can't modify the code. Agents must gain consensus. I call this the "SDLC pipeline" https://github.com/jwbron/egg/blob/main/docs/guides/sdlc-pip....
There's a lot going on here around sandboxing and enforcement mechanisms. This is covered more here: https://github.com/jwbron/egg/blob/main/gateway/README.md, but the documentation is slightly out of date. I'm actively working on an automated documentation intelligence system that ensures everything is up to date and should have that working in an hour or to.
I'd love to talk about this with folks. A lot of startups are announcing millions of dollars in funding to build out this kind of tool, but the reality is anyone can do it right now. I want to keep this open source and provide it to everyone for free, so we're all enabled to move as fast as we want with AI tooling. Hope I can build this out in a way that a lot of people find useful. This is early stages now, but I'm stoked to see how it continues to come together.
I think your point is valid and I've been having the same thoughts. My tooling is still in the experimental phase, but I can move so quickly that I'm having trouble grasping how products like this will survive. If I can build this out in a week and copy an idea like this one (which is a great one, mind you) in an hour, what's the value of paying someone for a product like this vs just building it myself?