I have a pretty large project with a UI, WebSocket server, SDK, CDP automation using Playwright, tests, examples and documentation. Everything is in one repo, so whenever I change the API, I usually have to update most of these parts together. I work with SDD, and before Fable I spent quite a lot of time just preparing the specification. Usually I would discuss the task with Opus 4.x several times, get criticism and suggestions from GPT-5.x, and then combine everything into one document. Only after that I could give the spec to the model for implementation. The design part usually took around 2-4 hours. Implementation with Opus took another hour or two. With Fable 5, my workflow changed a lot. I can describe a task more like a product requirement or a high-level architecture idea, and most of the time I get what I actually had in mind. I don’t need to prepare every small implementation detail in advance. For me, this saves around 2-3 hours of design work. I honestly expected Opus 5 to have at least the same level of code quality and decision making, especially based on the benchmark charts. But during these four days I kept finding things that needed fixing. At first it was just some small changes here and there, so I didn’t think much about it. Then I started noticing more unnecessary code and functionality I never asked for or approved. Some decisions also looked reasonable at first, but didn’t really fit the rest of the system. And honestly, I noticed this pretty late. You get used to good results very quickly, and I probably trusted the output more than I should have. So now I’m rolling back 4 days of changes and going back to Fable. Redoing the work is annoying, but it feels better than constantly wondering what else I might have missed in the code from Opus 5. Anyone else in the same boat? submitted by /u/datuname
Originally posted by u/datuname on r/ClaudeCode
You must log in or # to comment.