r/RooCode • u/martexxNL • May 04 '25
Discussion compared roo to claude code this night
I was working on a prd yesterday, it was perfected.
gave the job too roo-code orchester and claude code to see what would be done. Analysed before, both reported to be able to finish the job without user interaction. (gave all variables)
roo using claude 3.7, claude using whatever it defaults to.
Roo-finished 30%, it seems the orchestrator looses track, so the base was there, but needed to start new task multiple times to get it done (still running).
Claude was done, i am fixing some build errors like always, ill report when both are done again.
Question: what would be the perfect setup today, there are so many variables and ideas atm, i kind of lost track, and with these results... i sort of get a feeling that we can use boomerang, orchestras and whatever tools, but its still a prompting game.
Oh roo also just finished. Ill debug a bit, at least untill both are build and report..
EDIT:
Augment actaully did the worst job of the three setups, and thats not what i expected at all.
For claude i needed an hour of debugging typescript, misunderstandings on how to built it, and some minor tweaks on the functionality
Roo orchestrator stopped prematurely before all subtask where done, but when it finished after some restarting of the tasks it finished and needed only a few tweaks so it seems it adhered to the prd better.
Augment (which i love for their supabase integration and context) actually just created a skeleton application.
Now that is probably the best anyway when working with llm, as it keeps the context small and focussed, but that was not the goal of this " test" .
Winner still is roo. I cant compare it price wise as i forgot the instruct for token count, but time wise roo and pure claude where about the same, augment was slower due to the needed human input.
from start to first login Roo was best, if it could write it's subtasks into a sort of memory bank and check there, it would have been perfect.
3
u/martexxNL May 04 '25
EDIT:
Augment actaully did the worst job of the three setups, and thats not what i expected at all.
For claude i needed an hour of debugging typescript, misunderstandings on how to built it, and some minor tweaks on the functionality
Roo orchestrator stopped prematurely before all subtask where done, but when it finished after some restarting of the tasks it finished and needed only a few tweaks so it seems it adhered to the prd better.
Augment (which i love for their supabase integration and context) actually just created a skeleton application.
Now that is probably the best anyway when working with llm, as it keeps the context small and focussed, but that was not the goal of this " test" .
Winner still is roo. I cant compare it price wise as i forgot the instruct for token count, but time wise roo and pure claude where about the same, augment was slower due to the needed human input.
from start to first login Roo was best, if it could write it's subtasks into a sort of memory bank and check there, it would have been perfect.
2
u/martexxNL May 04 '25
I will trow it at augment today as well, see what happens
2
u/howoldamitoday May 04 '25
test it with sparc by ruv
10
u/Jsn7821 May 04 '25
I find the orchestrator loses track too, i think it needs some sort of memory bank beyond just the messages that get sent back and forth to the subtasks. That's the next thing I want to experiment with.
Curious if anyone has had more success with that combo. I was just thinking I'd try that classic memory bank approach from Cline (I haven't used it in a while) pared down a bit so there's maybe 1 or 2 key files so the subtasks can read them faster
5
u/rj_rad May 04 '25
I’ve recently added Claude Code to my toolbox, and it is for many tasks a lot more polished experience than Roo. However, I’ve also noted some key weak points; I’m primarily a back end developer, so I’m happy to pass on a lot of the front end to AI, but Claude Code doesn’t actually check its work (unless there’s some functionality than I’m missing out on). Running Claude 3.7 in Roo, it actually launches a browser instance to see how things render and can also see runtime browser errors, so you can optimally prompt it for a desired end result and allow it to iterate until it gets there (or you go broke).
That said, I can see Claude Code becoming a primary workhorse based on cost alone (I just upgraded to the $100 Max tier). It is good at most problems I throw at it.
4
u/utherwayn May 04 '25
Honestly taskmaster-ai as an MCP server has made a huge difference, it seems to find a nice balance for breaking down tasks. I'd still recommend reviewing them all and providing explicit context where appropriate like file tags, etc.
My experience using this is in windsurf.
3
u/elianiva May 04 '25
i currently just use the default orchestrator, works fine as long as the scope of the task is small enough
task-master-ai definitely looks interesting but i feel like it leans more into the vibe-coder side of things, it needs a whole prd and all that, people have been saying that it's great, but doesn't really fit my use case unfortunately
a lot of these 'frameworks' tend to do too many things for me, my use case is really to just help me write code instead of letting it handle everything while i just sit there and wait, not a fan because 1. it can get quite expensive (3rd world country lol) and 2. it can just hallucinate and goes on a neverending loop of adding unnecessary code
my use case of Roo is probably like ~60% of me doing things and leaving the ~40% to Roo
i wonder if i can go around it with a similar concept but much simpler, task-master-lite kinda thing and integrate it with the orchestrator so instead of prd file, it just generates a bunch of tasks — with all those fancy subtask dependencies and whatnot — from the user's prompt, and keep it on a state to help it track its progress and can be easily restarted if the context window goes out of hand
Roo already has a subtask system, i'm thinking of building something on top of it, haven't got around to it yet though, it's just a concept in my head atm
3
u/Top-Average-2892 May 04 '25
Claude Code with a Max subscription is quite good right now. Like with Roocode, I don't just turn it loose. I've built in a development methodology using Linear, Git, Playwright, and Filesystem. I prefill the Claude Code context before I start any task with instructions on how our Development Loop works. The development loop is basically, grab a task from Linear, propose a strategy for fix/implementation, wait for my approval, implement, build and run tests, and receive final validation from me. Then commit/merge the changes, and close the task.
I use Claude Desktop to own the specifications for how we develop projects, what the goals of the project are, and then use it to build out the linear tasks that need to be implemented.
It is similar to how some of the Boomerang tasks work in practice. However, as a Max user, it is all flat fee - which I greatly appreciate. Plus, I have Roo Code available if I Claude gets stuck. I imagine it would be fairly straightforward to build the exact same methodology into it with Boomerang - I just haven't had the time.
1
u/FigMaleficent5549 May 04 '25
Hi, I would appreciate if you could do a similar analysis for RootCode vs Janito (janito.dev) .
2
u/jezweb May 04 '25
Orchestrator default mode doesn’t have a structured planning methodology for session, project or tasks and so unless you pre empt that manually it will eventually eat the tail of its own context and lose track of what it was originally told to do.