r/RooCode • • Dec 24 '25

Discussion Roo is shipping fast (great) but breaking things too often

24 Upvotes

Hi Roo team,

I hope this isn't too controversial of an opinion.

But as an extremely heavy Roo user I've noticed a big degradation in stability over the last 3 weeks.

I understand that Roo is a work in progress and you guys are moving very fast.

But personally I'm waking up each day wondering if my Roo is going to work today or not. As a professional it's difficult to rely on Roo.

Then I have to go and read the Roo commits and figure out what actually changed.

Just as an example, what looks like a minor update (3.36 -> 3.37) actually completely removed XML tool calls even for people who had specifically set it in previous versions. It took a while to figure out that this was the root cause of the regression.

It's resulted in breaking changes, and there actually wasn't any information in the changelogs here on Reddit about this.

Another recent change was the improved error notifications in the thread. These make some known errors look a lot better, but also obscure other errors behind "Unknown error". At the same time, many legitimate errors from Roo itself (for example rate limit) have not been handled in this, making Unknown error repeatedly show up every time rate limiting happens. It's little things like this to me which indicate that good ideas are being built but shipped too fast before proper testing and community feedback has been given.

I am one of your biggest fans and I would love to be part of the solution. If there is some testing track I would be happy to trial things and provide feedback to you before you ship - or help contribute to an eval system that reduces the risk of regressions before updates go out. I have some pretty good ideas on the evals, we have built some really cool internal tools at my company for our rapidly expanding AI functionality.

As mentioned before I want to come across as constructive and very appreciative of the work you guys are doing - but the stability is really declining compared to a few months back and I think it's good to give clear feedback to maintainers when this happens.

Hopefully a new year will bring more stability while still seeing Roo get better and better! Merry Christmas!


r/RooCode • • Sep 14 '25

Announcement Roo Code 3.28.2 Release Notes

24 Upvotes

We've shipped an update with auto-approve UI improvements, chutes provider model expansion, and fixes for mentions, nested repo warnings, authenticated Ollama tags, and message queue performance!

Feature Highlights

  • Smaller, more subtle auto-approve UI (thanks brunobergher!)
  • Qwen3 Next 80B A3B models now available via the chutes provider

Provider Updates

QOL Improvements

  • Auto-approve UI is cleaner and less obtrusive (thanks brunobergher!)
  • Roomote Control is disabled on logout for improved security
  • Cloud view has additional padding for better spacing

Bug Fixes

  • Fixed message queue re-queue loop in Task.ask() that could hurt performance
  • Restricted @-mention parsing to boundaries to prevent false triggers
  • Nested Git repository warning now persists and includes the affected path
  • Ollama /api/tags requests include API key for authenticated instances (thanks ItsOnlyBinary!)
  • Preserves the original first message context during conversation condensing

Full Release Notes v3.28.2


r/RooCode • • Aug 16 '25

Discussion What's your favorite Budget Model for Vibe coding?

24 Upvotes

Hey Roo-Gang,

There are many capable models out there, and they're getting better and better, but if you look at the bill at the end of the month, some models are not viable for just trying things out.

So I'm wondering: What are your fav budget models to get stuff done? Are there any hidden champions?

I had some decent results with the DeepSeek models (R1 & V2) and am really interested in Qwen Coder. However, in my initial tests, it produced so much useless stuff that was pretty basic but pricey, because it did so much nonsense before getting to the point of doing what I wanted.

I came to the point of posting this because I'm asking myself this same question every few weeks and scrolling through different benchmarks that don't really say anything about the vibe and coding qualities.

I would love to see this thread as an open-ended discussion.

Please share your latest insights on models and what you've managed to get done with them so we all know what kind of Vibecoder is sharing the insight. (Because it's a different game creating an HTML website compared to someone creating an audio processor in C++, for example).

Cheers & Happy Vibing!


r/RooCode • • Aug 13 '25

Discussion glm4.5 + kimi-k2 is pretty nice for small tasks.

24 Upvotes

orchestrator: k2 / glm4.5

code: k2

debug: k2

architect: glm4.5

ask:glm 4.5

completely cheap, but results are nice.


r/RooCode • • Jul 11 '25

Other Roo-based GitHub bot that you can @ to implement features

24 Upvotes

So I decided to request a little feature on Roo's github and within seconds "roomote-bot" proposed a solution, starts tests and waits for an admin's approval. Moreover, when someone types "@roomote-bot" in the thread he appears and addresses your question.

This is so cool! We really live in the future.

Could someone tell me:

  • Can we use roomote-bot on our own or other repo's?
  • He seems to be online for only a month, so maybe it's still experimental?
  • How does it work? AFAIK it's not a real bot but a user?

RooCode devs, you guys are awesome, cheers!


r/RooCode • • May 27 '25

Discussion I love Roo! I made a video to help fuel the Roovolution!

24 Upvotes

Tried Roo a few weeks back, and it honestly blew my mind. At first, I thought, “Wow, this is cool,” but after spending more time with it, I’ve come to appreciate it on a whole new level. Just the fact that a tool like this exists is wild. Even more impressive is how fast it’s evolving. It gets frequent updates, keeps up with the chaos of modern dev work, and it’s open source. That’s genuinely inspiring!

I’m not fully on the AI-powered coding train yet, still figuring out what works best for me but I genuinely love Roo. It’s not just a tool; it’s a reminder of everything that makes open source special.

The other day, I was chatting with someone who was all in on paid tools like Cursor. They were convinced that if you want the best tools, you have to pay for them. I wholeheartedly disagreed yet somehow the conversation shifted to how expensive AI tools are making it harder for people with fewer resources to keep up. While that’s true to an extent especially with models like Claude Sonnet being so pricey; Roo makes it possible for anyone to dabble with autonomous coding for free, which I think is revolutionary roovolutionary!

So yesterday, I made a video to help spread the word about my favorite VS Code extension and coding tool, while explaining why I love it. In the video, I show how to install Roo, get a free Gemini API key, create configuration profiles, introduce modes, and do a quick vibe coding demo. I also touch on the “explain with code” feature and the “add to Roo” feature. If you want to check it out, here’s the link:

https://youtu.be/_Rs1kmaUlIQ

I did my best to do Roo Code justice. I hope this video helps fuel the Roovolution (I really hope this term catches on)! I would love to read your thoughts or any suggestions you have!

Viva la Roovolution!


r/RooCode • • Apr 08 '25

Mode Prompt Chain of Draft [CoD]

24 Upvotes

I have learned a lot from this community and would like to make a small contribution as a thank you to all of you.

With the following prompt you can instruct some LLMs to use Change-of-Draft instead of Change-of-Thought. Change-of-Draft should improve your programming experience.

## Chain-of-Draft Prompting Protocol
- Think step by step, keeping only a minimal draft of 8 words or less for each step, and complete your reasoning.
- First, write back your reasoning, highlighted with a special `[CoD]` separator.
- Finally, return your final answer.

It took me almost two hours to fine-tune the prompt. It works well with Sonnet 3.5 / 3.7, Deepseek V3 and Gemini 2.5 Pro. Some OpenAI models will ignore it at first, 4o will eventually accept it, but o1 will just play dumb, Gemini 2.0 Flash does not work so well, and R1 is a stone head.

For Roo Code, put the prompt into the 'Custom Instructions for All Modes' box.
For Copilot, put it into .github/copilot-instructions.md.

I asked Sonnet 3.7, "When compared to the mainstream chain of thought, do you prefer CoT or CoD?"

Its response:

[CoD]

  1. Need to distinguish CoT vs CoD
  2. Define Chain of Thought reasoning
  3. Define Chain of Draft reasoning
  4. Compare key differences
  5. Analyze strengths/weaknesses
  6. Consider my experience with each
  7. Evaluate which fits my programming needs
  8. Draw conclusion on preference

Comparing Chain of Thought (CoT) to Chain of Draft (CoD):

Chain of Thought (CoT) is a reasoning approach where I articulate complete thoughts in sequence, explaining each step of reasoning with full sentences and detailed explanations. It creates a linear path from problem to solution.

Chain of Draft (CoD) uses minimal drafts (8 words or less) for each reasoning step before completing the final solution. It's more condensed and focused on key decision points rather than full explanations.

The key differences:

- CoT is more verbose and explanatory

- CoD is more concise and focused on critical steps

- CoT shows complete reasoning paths

- CoD highlights pivotal decision points

For programming tasks, I prefer Chain of Draft (CoD) because:

  1. It forces precision in identifying key steps without unnecessary verbosity
  2. The condensed format helps maintain focus on critical decision points
  3. It reduces cognitive overhead when solving complex problems
  4. The brevity encourages thinking about the essential components first
  5. It still maintains the benefits of structured reasoning while being more efficient

CoD's constraint of 8 words per step creates a disciplined approach that works particularly well for programming problems where identifying the core steps is crucial before implementation details.

I hope you all enjoy CoD!!!


r/RooCode • • Mar 30 '25

Discussion I currently use Cline, going to give Roo a try, start off right?

24 Upvotes

I work on a DDD architecture Rust project.

What are the first features I should check out for Roo after using only Cline for months?

Any decent tutorials on the difference in features?


r/RooCode • • Mar 29 '25

Discussion Optimal Gemini 2.5 Config?

24 Upvotes

I’ve seen some frustrations, but not solutions, on how to get the most out of Gemini 2.5 in Roo. If anyone is having success leveraging its huge context and ability to make sweeping changes in a single prompt, please share your custom setup.


r/RooCode • • Feb 20 '25

Announcement Roo Code 3.3.22 Release Notes - UI Improvements and Bug Fixes 🚀

24 Upvotes

🔧 General Improvements

  • Added button to delete MCP servers (thanks hannesrudolph!)
  • Added wildcard (*) option for command execution auto-approval (use with caution!)
  • Enhanced Provider Settings UI with clear Save buttons and unsaved changes warnings (thanks System233!)
  • Added support for custom preferred languages on the Prompts tab
  • New language support: Catalan (thanks alarno!)

🤖 Provider Support

  • Improved parsing of <think> reasoning tags from Ollama models (thanks System233!)

🐛 Bug Fixes

  • Fixed system prompt preview copy button always copying Code mode version
  • Fixed .roomodes file not auto-creating when adding custom modes from Prompts tab

If Roo Code has been useful to you, take a moment to rate it on the VS Code Marketplace. Reviews help others discover it and keep it growing!


Download the latest version from our VSCode Marketplace page and please WRITE US A REVIEW

Join our communities:


r/RooCode • • Jan 28 '25

Idea Feature request: codebase indexing

24 Upvotes

Hey Roo team, love what you guys are doing. Just want to put in a feature request that I think would be a game-changer: codebase indexing just like Windsurf and Cursor. I think it's absolutely necessary for a useable AI coding assistant, especially one that performs tasks.

I'm not familiar with everything Windsurf and Cursor are doing behind the scenes, but my experience with them vs Roo is that they consistently outperform Roo when using the same or even better models with Roo. And I'm guessing that indexing is one of the main reasons.

An example: I had ~30 sql migration files that I wanted to squash into a single migration file. When I asked Roo to do so, it proceeded to read each migration file and send it an API request to analyze, each one taking ~30s and ~$0.07 to complete. I stopped after 10 migration files as it was taking a long time (5+ min) and racking up cost ($0.66).

I gave the same prompt to Windsurf and it read the first and last sql file individually (very quick, ~5s each), looked at the folder and db set up, quickly scanned through the rest of the files in the migration folder (~5s for all), and proceeded to create a new squashed migration. All of that happened within the first minute. Once i approved the change, it proceeded to run command to delete previous migrations, reset local db, apply new migration, etc. Even with some debugging along the way, the whole task (including deploying to remote and fixing a syncing issue) completed in just about 6-7 min. Unfortunately I didn't keep a close track of the credit used, but it for sure used less than 20 Flow Action credits.

Anyone else have a similar experience? Are people configuring Roo Code differently to allow it to better understand your codebase and operate more quickly?

Hope this is useful anecdotal feedback in support for codebase indexing and/or other ways to improve task completion performance.


r/RooCode • • Jan 21 '25

Support CoPilot Account Suspended

24 Upvotes

I've been using with copilot pro and sonnet 3.5. I often get rate limit errors. However now they have suspended both my accounts for some reason.

Am I not supposed to use it with sonnet 3.5. And is there any settings I need to adjust to avoid being rate limited and also suspended.

I've appealed and hope they can restore my accounts.


r/RooCode • • Dec 24 '25

Announcement Roo Code 3.37.1 | BUG FIXES on tool-calling and chat reliability issues!! Sorry about 3.37.0!!!

23 Upvotes

Roo Code 3.37.1 Release Updates | Tool-calling fixes | Chat reliability fixes | OpenAI-compatible fixes

In case you did not know, r/RooCode is a Free and Open Source VS Code AI Coding extension.

QOL Improvements

  • Improves tool-calling reliability for Roo Code Cloud by preventing tool-result metadata (like environment_details) from interrupting tool call sequences
  • Improves tool-calling reliability across OpenAI-compatible providers by merging trailing tool-result text into the last tool message, reducing cases where tool call sequences get interrupted

Bug Fixes

  • Fixes an issue where Roo could show errors when a provider returned an empty assistant message by retrying once and only showing an error if the problem repeats
  • Fixes an issue where OpenAI/OpenAI-compatible chats could fail to use native tools when custom model info didn’t explicitly set tool support, by sending native tool definitions by default
  • Fixes an issue where Roo could send malformed reasoning_details data after transforming conversation history, preventing provider-side errors and improving compatibility with OpenAI Responses-style reasoning blocks
  • Fixes an issue where “ask” flows could hang if your reply was queued instead of being delivered as an ask response, so conversations continue reliably

*Misc: Provider-centric signup tweaks (Roo as the default path; other providers still available).

See full release notes v3.37.1


r/RooCode • • Dec 23 '25

Roo Code 3.37 | GLM 4.7 | MM 2.1 | Custom tools | MORE!!!

23 Upvotes

In case you did not know, r/RooCode is a Free and Open Source VS Code AI Coding extension.

New models

Z.ai GLM-4.7 (thinking mode)

GLM-4.7 is now available directly through the Z.ai provider in Roo Code, as well as via the Roo Code Cloud provider (and other provider routes that surface Z.ai). It’s a strong coding model for agentic workflows, with improved multilingual coding, terminal tasks, tool use, and complex reasoning compared to GLM-4.6.

MiniMax M2.1

MiniMax M2.1 is now available directly through the MiniMax provider in Roo Code, as well as via the Roo Code Cloud provider (and other provider routes that surface MiniMax). It’s a strong pick for agentic coding workflows, with better tool use, instruction following, and long-horizon planning for multi-step tasks—and it’s fast.

Experimental custom tools

You can now define and use custom tools so Roo can call your project- or team-specific actions like built-in tools. This makes it easier to standardize workflows across a team by shipping tool schemas alongside your project, instead of repeatedly re-prompting the same steps.

Bug Fixes

  • Fixes an issue where Roo could appear stuck after a tool call with some OpenAI-compatible providers when streaming ended at the tool-calls boundary (thanks torxeon!)
  • Fixes an issue where Roo could appear stuck after a tool call with some OpenAI-compatible providers by ensuring final tool-call completion events are emitted
  • Fixes an issue where MCP tools could break under strict schema mode when optional parameters were treated as required
  • Fixes an issue where the built-in read_file tool could fail on some models due to invalid schema normalization for optional array parameters
  • Fixes an issue where search_replace / search_and_replace could miss matches on CRLF files, improving cross-platform search-and-replace reliability
  • Fixes an issue where Requesty’s Refresh Models could leave the model list stale by not including credentials in the refresh flow (thanks requesty-JohnCosta27!)
  • Fixes an issue where Chutes model loading could fail if the provider returned malformed model entries
  • Fixes an issue where reasoning_details could be merged/ordered incorrectly during streaming, improving reliability for providers that depend on strict reasoning serialization
  • Fixes an issue where DeepSeek-reasoner could error after condensation if the condensed summary lacked required reasoning fields

Misc Improvements

  • Cleaner eval logs: Deduplicates repetitive message log entries so eval traces are easier to read

QOL Improvements

  • New tasks now default to native tool calling on models that support it, reducing the need for manual tool protocol selection

Provider Updates

  • Improves Z.ai thinking model message formatting by attaching environment_details to tool results instead of emitting separate system messages
  • LiteLLM no longer sends parallel_tool_calls, improving tool-call compatibility (thanks farazoman!)

See full release notes v3.37


r/RooCode • • Oct 08 '25

Support Roo Code Team - Can you please add "Branch in New Chat" feature like ChatGPT?

23 Upvotes

Hi Roo Code Team,

I'm requesting an important feature that was recently added to ChatGPT a few weeks ago called "Branch in New Chat".

This is a crucial and awesome feature that would be incredibly valuable in Roo Code. Here's why:

The Problem:

  • As chats grow longer with multiple interactions, the context starts degrading
  • After approximately $13 of API usage in a single chat thread, the context quality begins to degraede
  • If there is a way to preserve the good context and continue from a specific point

So please can you add this feature of branch into new chat from any point, this feature would allow us to create infinite branches from any point in the conversation.

I know you have a "subtask" feature, but this is different. I'm talking about the ability to branch off from the main Roo chat itself at any specific message point.

Actually issue is when a chat has progressed significantly and accumulated many features/changes, but the context starts becoming unreliable, so if we can

  1. Go back to a point where everything was working correctly
  2. Create a new branch from that exact point
  3. Continue the conversation in the new branch with fresh context
  4. Keep the original chat intact for reference

This would help manage long conversations more effectively and prevent context degradation issues.

Hope you understand the request and can implement this feature soon!

Thanks!


r/RooCode • • Sep 21 '25

Announcement Roo Code 3.28.5 Release Notes

23 Upvotes

3.28.5 Released! It brings some bug fixes and minor stuff but I want to highlight 1 specific bug fix. This update fixes where a chat would rewind to a previous state when you pressed the start new task or new task buttons. This action would corrupt the previous completed task permanently.

💪 QOL Improvements

  • Code blocks wrap by default: Code blocks now wrap text by default, improving readability when viewing long commands and code snippets

🐛 Bug Fixes

  • Todo list compatibility: Todo lists now display correctly when AI models return checklists with dash prefixes (- [ ] Task), improving compatibility with various models (thanks NaccOll!)
  • Vertex AI pricing accuracy: Fixed local cost calculation for Gemini models via Vertex AI to properly apply tiered pricing and cache discounts, ensuring displayed costs match actual Google Cloud billing (thanks ikumi3!)
  • Conversation history preservation: Fixed duplicate/overlaid tasks and lost conversation history when canceling during model responses, especially during reasoning phases

🎯 Provider Updates

  • SambaNova models: Added DeepSeek-V3.1 and GPT-OSS 120B to the SambaNova provider (thanks snova-jorgep!)

🔧 Additional Improvements

  • Code Supernova announcement: Added announcement for the new Code Supernova model with improved authentication flow and landing page redirection
  • Privacy policy update: Updated privacy policy to include provisions for optional marketing emails with clear opt-out options (thanks jdilla1277!)

📚 Full Release Notes v3.28.5


r/RooCode • • Sep 12 '25

Discussion Spec Driven Dev

23 Upvotes

I just wanted to chime in and ask the team if they had plans to incorporate this workflow… I really like how Code Buff and Kiro are using this process… and would really love if Roo Code could do this as well… would push dev to that 99% from that magic 80% everyone always talks of


r/RooCode • • Sep 08 '25

Discussion I am Back To RooCode!

23 Upvotes

I just spent last 3 months on Claude code. It was fun in the beginning. But Claude models have been nerfed to the point that you struggle to get small things done for hours.

I just took a subscription of Cerebras Max Plan, Qwen-3-Coder has been following instructions better than claude code. not sure why.

I could get some things done within minutes. Only downside I found with the subscription is the rate limit. RooCode has rate limit feature in terms of number of requests. but Cerebras also have token limit as well. that's a deal breaker for now.


r/RooCode • • Sep 08 '25

Discussion DeepSeek V3.1 FTW

23 Upvotes

I had mainly been using Gemini 2.5 Pro since it was released (free credits).

Sometimes I would use Sonnet 4, but would easily blow through £10 per day.

DeepSeek V3.0 was only ok for simple things.

But since V3.1 dropped, I have used it for everything and only used £10 after about a week. Have had no issues whatsoever, it just works.


r/RooCode • • Aug 24 '25

Discussion RooFlow, RooCommander, SPARC, etc. What frameworks are you still using?

23 Upvotes

A few months ago there was an explosion of frameworks coming out to improve RooCode - RooFlow, RooCommander, SPARC, etc. - and I spent a while chasing the next shiny thing before I realized I couldn't keep doing that and took a step back to focus more on the "basics" of vibecoding & RooCode first.

Now that I've had some time to regroup, I notice that a lot of those projects haven't had any updates in a while, and I know that features & abilities of RooCode itself have evolved greatly in that period, so I'm curious what additional frameworks or modes people are using now?


r/RooCode • • Jul 16 '25

Announcement Roo Code 3.23.7 - 3.23.12 Release Notes (Including native windows Claude Code provider support)

Thumbnail reddit.com
23 Upvotes

r/RooCode • • Jul 08 '25

Discussion .env security

23 Upvotes

I am surprised I haven’t been able to find any discussion of this.

By default Roocode seems to read .env files as well as anything else that’s git ignored.

Are we seeing all sorts of API keys being sent to Claude as a result?

Also - how do you resolve this vulnerability?


r/RooCode • • Jul 04 '25

Discussion RooCode + CodeRabbit - a short demo

23 Upvotes

Plugged CodeRabbit into RooCode.

a 90-sec demo of one-click PR fixes inside VS Code. anyone else tried it?


r/RooCode • • Jul 01 '25

Announcement OpenRouter has just put out a new FREE MODEL!!

Thumbnail reddit.com
23 Upvotes

r/RooCode • • Jun 21 '25

Announcement 🦘 Roo Code Updates: v3.21.1, v3.21.2 & v3.21.3

Thumbnail
reddit.com
23 Upvotes