Original Reddit post

I'm generally happy with the workflow approach of interacting directly with Fable, and using Fable as planner, orchestrator and for acceptance, while having it delegate implementation and grunt work to Opus sub-agents. However my main frustration is that these Opus workers feel like they're running in molasses - compared e.g. to Sol workers. Even the most straight-forward mechanical task can end up being a multi-hour adventure. The workers are not sitting around waiting for slow tests or extensive validation runs, they are mostly actively working, actually reading references, existing code and API documentation and producing output. I will say that I am running Opus/xhigh effort - and while not all tasks would require that, many of the harder ones do actually need to for output results to be acceptable, and I'd rather not risk having to re-do or getting sub-par work by defaulting to a cheaper/faster model. Is this just what it is right now? I would like to start experimenting a bit more with fast mode, but it's not clear to me how that interacts with the whole workflow system. I don't think my quota would survive for long running multiple Opus/xhigh workers at fast, and selectively switching them to fast after they've been started is supposedly not great for token usage. Is it feasible to ask Fable to 'juggle' worker effort and fast mode as appropriate for each task? Or do I just need to remember to specifically call this out every time I approve a new milestone start? Are there any other techniques to get more speed except lowering the model/effort? submitted by /u/SnuffleBag

Originally posted by u/SnuffleBag on r/ClaudeCode