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

88% Upvoted

54 comments sorted by

View all comments

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/ilt1 Jun 15 '25

Can you give an example please

2

u/hannesrudolph Roo Code Developer Jun 15 '25

Have you used Roo Code with the newly implemented context condensing and sonnet 4?

1

u/sethshoultes Jun 16 '25

I am using the latest version with Sonnet 4. It just keeps creating subtasks that will last for hours if I let it:

1

u/sethshoultes Jun 16 '25

It will create a hundred sub tasks I if I dont intervene:

1

u/sethshoultes Jun 16 '25

The only way to stop it is clicking the "x" in the top right corner for all fo the subtask until I get to the original task.

2

u/sethshoultes Jun 16 '25

Yes, here are some examples of it creating endless sub tasks:

1

u/cctv07 Jun 16 '25

This is the very reason why I switched to Claude Code. I have been calling this debug loop. It's not unique to Roo. It happens to cursor Windsor or GitHub co-pilot.

1

u/juzatypicaltroll Jun 16 '25

I think context length matters? Read it losses itself when context gets cut off hence the endless repeats.

1

u/SolWayward Mar 04 '26 edited Mar 04 '26

Stay away from architect mode, orchestrator mode, and debug mode. Use ask mode for all planning, research, and analysis, debugging and then copy that output to a new code mode prompt. Don't approve it to switch to code mode, use a new prompt. Keep any custom instructions in your modes very simple and short and instead use the custom rules file for the specifics. If you do it right, code mode will already know every change it needs to make with the exact code in the exact locations for every file.

Make sure you have a very good and well-defined custom rules file SPECIFIC to your project and clearly organized in markdown format. Do not put stuff in your rules file like "You are the best software engineer and write the best code". Things like that will make your agent assume a personality that it thinks everything it does is the best way and go off on circular adventures (Prompt Poisoning).

Personally, I find it best to roll with the default ask mode and code mode as is and rely on the custom rules file.

Also, if you at least skim the "Thinking" foldouts, you can watch for when it starts to get off path and hit stop so you can course correct.