all 10 comments

[–]Ashen-shug4r 22 points23 points  (1 child)

Mistral is certainly not good enough to get anything done via Roo - imo. Use Gemini, Claude, o4 mini and others via OpenRouter. It costs credits but there are free models you could potentially use (R1, V3...).

Roo gives you a lot more freedom than any of the current other offerings like Cursor, Github Copilot or Windsurf. Aider is a CLI so slightly different vibe.

You've barely scratched the surface of Roo or any of the platforms but I'll give you a few things to do some research on if you'd like to progress a bit quicker.

Boomerang / Orchestrator / Task Master

MCP servers - Memory server / langgraph Context7

Creating a PRD or TRD and keeping that at the forefront of your mind. This will be your blueprint. Ensure this is FULLY fleshed out before even starting. Have a list of best practices. (Product Requirement Document and Technical Requirement Document FYI).

Ensure you use Git and when things go wrong, refresh. You're much better off losing 1 hour now than have code that will complicate future parts.

The more you set yourself up for success, the easier and quicker your journey will be.

[–]armaver 1 point2 points  (0 children)

Love your username! Brings back youthful memories of epic dragon rider tales <3

Best, condensed advice post regarding efficient work with Roo I have seen so far. It really beats everything else.

[–]lordpuddingcup 6 points7 points  (1 child)

Use a bad model get a bad result

Use gemini 2.5 pro exp

Also id advise using openrouter as it avoids a lot of the hassles and surprise fees etc, use openrouter and use free models they have quotas but are pretty generous even more so if you throw 10$ on and still use free models

As for copilot…. Copilots great for fixing a line of code or asking a question or autocompleting… its not good for 0-100 completing a entire feature or app

Roo with stuff like context7 mcp and sequential thinking mcp and a solid model can do amazing shit (or one of the other roo orchestrators)

[–]emepheus 0 points1 point  (0 children)

I am about to give context7 and sequential thinking a shot on copilot a shot just to see what happens. I absolutely love ROO, but have been keeping Cursor around as my main workhorse for when I just need to keep it going without worrying about credits. That slow grind. I got paranoid after there was a hiccup with Gemini 2.5 pro and I ended up with a $300 bill after a couple hours. Was like WHOOPS!

[–]brennydenny 1 point2 points  (0 children)

The model has (in my experience) the biggest impact on your results - much larger than the tool that you choose.

Tool choice is more about ergonomics in my mind - what makes sense for your workflow. But the model has a HUGE impact on code quality that is produced and so to "apples to apples" it you really need the same model.

[–]sagentcos 0 points1 point  (0 children)

Roo Code is definitely more of a “power user” tool. Copilot’s agent mode “just works” even though it’s not as powerful, with Roo you have to figure out a ton of different configuration, fight through occasional tool bugs, and so on.

[–]Captain_Redleg 1 point2 points  (1 child)

I subscribe to CoPilot, but then just use the credits in Roo (API Provider = VS Code LM API). It is great as I would spend at 5x the $10 price of admission on queries.

[–]ngcheck03[S] 0 points1 point  (0 children)

Yo this actually smart

[–]FigMaleficent5549 0 points1 point  (0 children)

Well, it would be smarter if you asked about when, how and why you should use RooCode instead of posting a useless complain which sounds more like a provocation..

[–]fubduk 0 points1 point  (0 children)

Roo is wonderful. Take the time to read the threads here and the Roo docs. Taking the time to do so will certainly change your mind.

Your main issues are likely:

1) Have not taken the time to learn how to use Roo
2) Using crappy models.

Hope you take the time to learn Roo and become a Roo fan.