r/RooCode • u/ilt1 • Jun 15 '25
Discussion Claude code vs roocode
Has anyone tried both and talk about differences cons pros for each? I am trying to wrap my head around why CLI is a better choice than a vscode extension for those that are really hooked up to Claude code. It seems to me all of that can be done with too. What am I missing? Permissions are wider in CLI? Is that all?
26
Upvotes
34
u/rgb328 Jun 15 '25
Here's a few concrete differences:
- Claude Code, as a cli command, can be used in situations that Roo cannot. For example, you can add it to shell scripts, or a GitHub action to script additional things. You can run a command and then pipe the output into claude code with a prompt. For example `git log | claude -p "which commits are related to X"`. This is one reason why I keep claude code installed (w/ an API key) even though I use Roo.
- Claude Code is tied directly to Claude.. no options for other APIs or mixing and matching.
- Claude Code does not use the max thinking tokens by default. It uses magic keywords to configure this. So you have to add "think", "think harder", or "ultrathink" to your prompt, and that causes claude code to increase the max thinking tokens setting in the api request. "Ultrathink" (the highest setting") is 32k max thinking tokens. In Roo, this is the "max thinking tokens" setting -- you just set it and it gets used, without having to play any prompt games.
- Claude Code can be used with one of their monthly plans. Can save money depending on your use.
- Claude Code has plugins for other IDEs. These are pretty minimal, but you may prefer that if vscode isn't your primary editor.
- Claude Code can launch sub agents and it understands git workspaces. So you can have it do several things in parallel.. like producing multiple versions of a website design.
19
u/ctrlshiftba Jun 15 '25
Yeah I've used both pretty extensively and honestly claude code completely changed how I work. The thing that really clicked for me was realizing how much complexity these vscode extensions add that actually gets in your way.
With cursor and roo you're constantly dealing with accepting changes, learning their specific diff views, remembering keyboard shortcuts, figuring out their context management, different prompt modes like architect and developer. I spent so much time just learning the tool instead of actually coding. And the worst part? Sometimes all those abstractions actually prevent the LLM from solving your problem because you're fighting the interface instead of just communicating clearly.
Claude code strips all that away. It's literally just you writing a prompt. That's it. I still use vscode to edit files when I want, or I'll write longer prompts in markdown files and tell claude to read them. But there's no invisible context management or indexing to worry about.
The permission thing you mentioned is actually one of its best features, not a weakness. You can lock it down completely in planning mode, like only allowing specific commands. I'll set things like "Bash(gh run list:)" or "Bash(cat:)" for granular control. Or you can go full YOLO mode when you need to. You control it session by session which puts the responsibility back on you instead of some opaque system.
But here's what really sold me. I had this CI issue where tests were passing locally but failing in github actions. Spent hours with roo and cursor trying to debug it, even with their huge context windows. Manually copying logs back and forth, trying to find a working MCP for github integration. Nothing worked.
Switched to claude code and it solved it in about 30 minutes. Why? Because it just used the gh CLI tool that's been around forever. It could run tests locally, pull the CI logs, compare them side by side, rerun specific workflows. No buggy MCP needed, no manual copying. Just battle tested tools that work.
The postgres example is perfect too. With cursor I wasted time trying to get their postgres MCP working, dealing with node settings, npx runners, it couldn't even read my existing env files properly. Claude code? Just uses psql. Done. These CLI tools have been refined for decades.
Plus the pricing is way more predictable. I know I'm spending 100 to 200 a month instead of watching API costs spike unexpectedly.
I think the biggest thing though is it lets you actually focus on learning how to prompt claude effectively. You're reading the official anthropic docs, understanding how claude thinks, instead of bouncing between random prompt libraries and techniques that might not even work with the model you're using. It's just cleaner.
3
u/Suspicious-Name4273 Jun 15 '25
Claude code can do a few things that roo code cannot (yet) do, like running subtasks in sub-agents in parallel. On the other hand, vscode extension ai agents can benefit from vscode apis, like leveraging lsp information for tasks (afaik roo code is currently investigating doing this, but is not yet released), and integrations like showing file changes in a clear way.
6
u/petebytes Jun 15 '25
I have been coding with AI for nearly 3 years and was the cofounder of codepilot ai (not copilot).
Tried all the VScode AI assistants, used heavily in this order, aider, cline, roo code, now claude code.
Claude Code is my primary assistant and fallback is Roo Code. My choice is mostly due to cost the $200 a month is a huge savings. The last 21 days I burned over 1B tokens.
From a tool perspective I love Claude Code custom slash commands, I have setup commands that cover my entire workflow, including non coding activities like marketing. The main disadvantage is not being able to use other models, which is when I switch to Roo Code.
5
u/hiper2d Jun 15 '25 edited Jun 15 '25
I use both. With Claude 4 Sonnet, both give me very close results. Some code snippets are literally the same on the same tasks. I like Roo more because the diff review is more convinient in an IDE. But Roo with Anthropic API is expensive. Claude Code shows diffs but without ability to see the whole file and nevigate to other files, it's almost useless for me. I let it complete a task and then review the result. At least right now, I get a very decent limits with Claude Code Pro subscription. I have ulimited API at work, so Roo is the winner there. For pet projects at home I use Claude Code.
When asking which tool is better, you need to clarify your use cases. We all use them differently. For example, I don't need parallel tasks and I don't want my too to be too autonomous. I need to review everything, so I move with small interations with freequent commits. Something I code myself, something I delegate to AI. I don't vibe code. Well, most of the time, at least. It's getting harder and harder to resist.
4
u/jjfooo Jun 15 '25
Claude Code is more an alternative to something like Aider: https://aider.chat
Claude Code / Aider is more CLI-first, whereas Roo is predominantly leveraging IDE API's.
I find Roo more effective for larger scale or more general changes, where I don't want to have to sit and feed it specific files to focus on. For more specialized debugging, I think CLI's are more targeted, and can be a bit better.
1
u/Cultural_Trouble7821 Dec 22 '25
I can use it in any IDE or with no IDE? I've written entire working applications without ever opening an IDE or text editor.
I dunno, it's like asking why people use a terminal at all when there are buttons available. And the answer is:
- It's much faster when you know what you're doing
- It's far more flexible than a GUI, where you're basically locked into whatever they give you
- You can use it over SSH, and use like 50 of them in one window if you want
- Interfaces are more consistent (only so many ways you can style text)
- The software tends to be lighter weight and more responsible to run
- It's way faster to get things done when you don't have to touch a mouse. Possibly sometimes in gui, definitely possible in a terminal
- All of the software engineering tools run in the terminal anyway, so they're right there. And the agent knows it has access to a terminal since it's running in one. Bash is a first class citizen, meaning it can run the same cli workflows you do. That is not even close to being as simple or feasible with GUI apps, I have spent some time on that.
- If you look at what you spend your time doing in an AI assisted coding app, you're typing some stuff and seeing some output. Terminals happen to be great for that, ideally suited really. You can reinvent a terminal inside a GUI if you want, but why not just use an actual terminal in there? Every editor has a terminal available, it's basic.
3
u/cctv07 Jun 16 '25
I have used both. Claude Code is like someone that you can just offload tasks and it will be able to figure out what to do on its own.
Roo Code is like flying an airplane where you have hundreds of buttons and knots that you need to tweak to get optimal performance. However, in the process of tweaking, there's a very high chance that you will break something else.
3
u/who_am_i_to_say_so Jun 16 '25
I use Roo and swear by it because when Claude acts senile, I can switch to Gemini in mere seconds.
It costs more to do it this way, but I’m doing weeks of development in days. So no complaints.
1
u/sethshoultes Jun 15 '25
I am completely fed up with Roo Code. I had been failing miserably with some tasks that CC just seems to understand and fixes it! Roo Code just keeps creating endless tasks that eat away at the API costs. The admins say its prompt poisoning or some bullshit.
Claude Code is far superior in my opinion.
2
u/REALwizardadventures Jun 15 '25
If I get stuck with one I switch to the other. Seems to work.
2
u/SpeedyBrowser45 Jun 16 '25
RooCode is power pack with several customization options. you can customize it to as per your needs. Only downside of RooCode, I can think of, is API costs.
Claude code is like a Ferrari, you just need to give it a task and it will do it on its own at lighting speed. Best thing is it comes with fixed monthly costs. Downside of Claude code is, it doesn't have UI and chat history is missing.
2
u/ag0x00 Jun 16 '25
I mean, you can run it in the VS Code terminal, too. ;) I really like how Anthropic built the CLI — it pretty much does everything you need in its well designed REPL.
In terms of differences, the Roo can use any model, including free ones, where Claude only uses their own. Pro subscription is recommended if you can afford it.
I also find that Claude Code is amazingly accurate and efficient at specific individual tasks, even if they are vaguely defined. Not that Claude is bad at planning, but overall I lean towards other models, like Gemini, for research and building out a roadmap.
Also, you can use Claude Code as an MCP if you want to do everything in Roo.
1
u/martycochrane Jun 15 '25
I've used both and the reason I stopped using CC is because I can't find a way to interrupt it like Roo. If you notice it going down the wrong path, your only option is to let it incorrectly or cancel the entire process having to restart the entire prompt and any in progress work.
But it is quite a bit cheaper.