I use Roo Code (Cline fork) and spend roughly $15-30/mo by subscribing to Github Copilot Pro for $10/mo for unlimited use of GPT-4.1 via the VS Code LM API, and a handful of premium credits a month (I use Gemini 2.5 Pro for the most part).
Once I max out the premium credits I pay-as-you-go for Gemini 2.5 Pro via OpenRouter, but always try to one shot with GPT 4.1 first for regular tasks, or if I am certain it's asking too much, use 2.5 Pro to create a Plan.md and then switch to 4.1 to implement it which works 90% of the time for me (web dev, nothing too demanding).
With the different configurable modes Roo Code adds to Cline I've set up the model defaults so it's zero effort switching between them, and have been playing around with custom rules so Roo could best guess whether it should one shot with 4.1 or create a plan with 2.5 Pro first but haven't nailed it down yet.
Looking at Cline, wondering what the real selling points for Roo Code are. Any chance you can say what exactly made you go with Roo Code instead of Cline?
Cline has two modes (Plan and Act) which work pretty well but Roo Code has 5 modes by default. (Code, Ask, Architect, Orchestrator, Debug) and it's designed so that users can add custom modes. e.g. I added a Code (simple) mode with instructions about the scale/complexity of tasks it can handle or decide to pass it to Code for a better model. I also changed the Architect mode to evaluate whether to redirect the user to Code or Code (simple) after generating a plan.
Roo Code just has a lot more config exposed to the user which I really appreciate. When I was using Cline I would run into minor irritating quirks that I wished I can change but couldn't vs. Roo where the odds are pretty good there are some knobs you could turn to modify that part of your workflow.
Once I max out the premium credits I pay-as-you-go for Gemini 2.5 Pro via OpenRouter, but always try to one shot with GPT 4.1 first for regular tasks, or if I am certain it's asking too much, use 2.5 Pro to create a Plan.md and then switch to 4.1 to implement it which works 90% of the time for me (web dev, nothing too demanding).
With the different configurable modes Roo Code adds to Cline I've set up the model defaults so it's zero effort switching between them, and have been playing around with custom rules so Roo could best guess whether it should one shot with 4.1 or create a plan with 2.5 Pro first but haven't nailed it down yet.