For the time being, nothing comes close, at least for me.
I use Github copilot and often tend to be frustrated. It messes up old things while making new. I use Claude 4 model in GH CP.
Then I'll look through the changes and decide if it is correct. Sometimes can just run the code to decide if it is correct. Any compilation errors are pasted right back in to the chat in agent mode.
Once the feature is done, commit the changes. Repeat for features.
Here are some nice copilot resources: https://github.com/github/awesome-copilot
Also, I am using tons of markdown documents for planning, results, research.... This makes it easy to get new agent sessions or yourself up to context.
Do you also get it to add to it's to-do list?
I also find that having the o3 model review the plan helps catch gaps. Do you do the same?
I'm not the original poster, but regarding workflow, I've found it works better to let the LLM create one instead of imposing my own. My current approach is to have 10 instances generate 10 different plans, then I average them out.
Sometimes one model would get stuck in their thinking and submitting the same question to a different model would resolve the problem
It allows you to have CC shoot out requests to o3, 2.5 pro and more. I was previously bouncing around between different windows to achieve the same thing. With this I can pretty much live in CC with just an editor open to inspect / manually edit files.
User experience is definitely worth something, and I think Cursor had the first great code integration, but then there is very little stopping the foundation model companies from coming in and deciding they want to cut out the middleman if so desired.
I watch the changes on Kilo Code as well (https://github.com/Kilo-Org/kilocode). Their goal is to merge the best from Cline & Roo Code then sprinkle their own improvements on top.
I spend $200/month by using Sonnet 4. Could be higher if you want to use Opus.
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.
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.
I stopped writing code by hand almost entirely and my output (measured in landed PRs) has been 10x
And when I write code myself then it’s gnarly stuff and I want AI to get out of my way…so I just use Webstorm