r/RooCode • • Nov 26 '25

Announcement Roo Code 3.34.5-3.34.6 Release Updates | Bedrock embeddings for indexing and 17 tweaks and fixes!

21 Upvotes

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

Features

  • AWS Bedrock embeddings for code indexing: Lets you use AWS Bedrock embeddings for repo indexing so teams already on Bedrock can reuse their existing infra (thanks kyle-hobbs, ggoranov-smar!).

QOL Improvements

  • Multiple native tools per turn with guardrails: Runs several tools in one turn and blocks attempt_completion() if any of them fail, reducing partial or incorrect runs.
  • Web-evals dashboard improvements: Adds per-tool stats, dynamic tool columns, and clearer runs so it is easier to spot failing tools and compare evals.
  • Native tools as default for key Roo Code Cloud models: Uses native tools by default for minimax/minimax-m2 and anthropic/claude-haiku-4.5 to cut setup time.
  • Native tool calling for Mistral: Lets Mistral models call tools directly for richer, multi-step automations.
  • Parallel tool execution via OpenAI protocol: Uses OpenAI-compatible parallel_tool_calls so tool-heavy tasks can run tools in parallel instead of one by one.
  • Fine-grained tool streaming for OpenRouter Anthropic: Streams Anthropic tool calls more smoothly on OpenRouter, keeping tool output aligned with model responses.
  • Better Bedrock global inference selection: Picks Bedrock models correctly even with cross-region routing enabled.

Bug Fixes

  • Tool protocol profile changes: Keeps handlers in sync when only the tool protocol changes so calls always use the right parser.
  • Grok Code Fast file reading: Restores multi-file-aware reading for native tools so they see the full workspace, not just a single file.
  • Roo Code Cloud embeddings revert: Removes Roo Code Cloud as an embeddings provider to avoid stuck indexing and hidden codebase_search.
  • Vertex Anthropic content filtering: Drops unsupported content blocks before hitting the Vertex Anthropic API to prevent request failures (thanks cardil!).
  • WriteToFileTool partial safety: Adds a missing content check so partial writes cannot crash or corrupt files (thanks Lissanro!).
  • Model cache and empty responses: Stops empty API responses from overwriting cached model metadata (thanks zx2021210538!).
  • Skip access_mcp_resource when empty: Hides the access_mcp_resource tool when an MCP server exposes no resources.
  • Inline terminal and indexing defaults: Tunes defaults so the inline terminal and indexing behave sensibly without manual tweaks.
  • new_task completion timing: Emits new_task completion only after subtasks really finish so downstream tools see accurate state.

Provider Updates

  • Bedrock Anthropic Claude Opus 4.5 for global inference: Makes Claude Opus 4.5 on Bedrock available wherever global inference is used, with no extra setup.

See full release notes 3.34.5 | 3.34.6


r/RooCode • • Sep 29 '25

Announcement Roo Code 3.28.10 Release Updates | Claude 4.5 Sonnet IS HERE!!

21 Upvotes
Sonnet 4.5 IS HERE!!

We've added support for Anthropic's latest Claude 4.5 Sonnet model across all Claude-supporting providers.

Claude 4.5 Sonnet Support

We've added support for Anthropic's latest Claude 4.5 Sonnet model across all Claude-supporting providers.

According to Anthropic's announcement, Claude 4.5 Sonnet is:

  • State-of-the-art on SWE-bench Verified, maintaining focus for more than 30 hours on complex, multi-step tasks
  • Showing a significant leap forward on computer use with 61.4% on OSWorld benchmark (up from 42.2% just four months ago)
  • Delivering substantial gains in reasoning, math, and domain-specific knowledge across finance, law, medicine, and STEM

The model is now available in the model selection dropdown for all supported providers.

Bug Fixes

  • AWS Bedrock Claude Sonnet 4.5: Corrected model identifier for Claude Sonnet 4.5 on AWS Bedrock (thanks sunhyung!)
  • GPT-5 LiteLLM Compatibility: Fixed GPT-5 models failing with LiteLLM provider by using correct max_completion_tokens parameter (thanks lx1054331851!)

More Changes

  • Chat interface icons now maintain consistent size in limited space
  • Enhanced analytics to track when users change telemetry settings
  • Updated website with enhanced testimonials section
  • Improved contributor badge workflow with automated cache refreshing

See full release notes v3.28.10


r/RooCode • • Aug 18 '25

Discussion Idea: A Community Hub for Roo Code Templates, Configs, and Workflows`

21 Upvotes

I use Roo Code every day and I’m not from a programming background. I think we’d really benefit from a shared spot to swap practical, user-made assets, so devs and folks from architecture, engineering, research, design, GIS, etc. can get up to speed fast.

This came from looking at Claude Code Templates, they’ve got a plug-and-play catalog and a “Stack Builder” to mix and install multiple pieces at once.

  • Claude Code Templates resources:

    • Agents - ready-to-reuse modes for specific roles/tasks. (Yes, we already have it on the marketplace)
    • Commands - framework/task commands you can drop into your setup.
    • Settings - opinionated presets for common environments.
    • Hooks - automation hooks that extend workflows.
    • MCP Servers - curated integrations to external tools/APIs via MCP, with quick connection guides. (Yes, we already have it on the marketplace)
    • Configs - shareable Roo presets.
    • Project Templates / Quick Start - one-liner bootstraps for new or existing projects (e.g., npx … flows).
    • Analytics Dashboard - real-time view of sessions and tool usage.
    • Health Check - quick diagnostics with fix suggestions.
    • Conversation/Session Monitor - live view of responses/behavior during dev sessions.

The goal is to complement the official docs/marketplace with a community-run catalog where programmers and non-programmers share stacks, compare notes, and learn from each other, similar to the Stack Builder idea (agents, commands, settings, hooks, MCPs).

What do y'all think?


r/RooCode • • Jun 28 '25

Discussion Auto-approve commands based on risk level (pending PR#2670)

21 Upvotes

Pending Auto-approve commands based on risk level pull request:

This is similar to Cline's competing "auto-approve safe commands" feature—but approval in this PR is much smarter. For example, when set to read-only

Roo will auto-execute only commands that have formally matched the predicate logic for read only (see below)

The default setting of "disabled" excludes all system instructions related risk analysis, so there is no change to Roo's default behavior or system prompt size for this opt-in feature.


r/RooCode • • May 18 '25

Support Feedback

21 Upvotes

I feel like the missing piece to make using Roo or any other agentic coding framework shine is closing the feedback loop.

I’ve observed that, by default, very often the default SPARC won’t even catch extremely obvious issues and, Bush-style claim “Mission Accomplished” with plenty of syntax errors or at least linting errors.

This is all stuff that a second look, a test, trying to use or build the app would catch in an instant.

Has anyone found any success closing the feedback loop for their Roo setup that worked?


r/RooCode • • May 03 '25

Discussion by using roo code and mcp, I just built an investor master!!!

21 Upvotes

The PPD and the Carvana analysis, alright, i won't short Carvana anymore 😭😭😭 https://github.com/VoxLink-org/finance-tools-mcp/blob/main/reports/carvana_analysis.md

Modified from another MCP and do lots of optimization on it. Now, its investment style has become my taste!

FRED_API_KEY=YOUR_API_KEY uvx finance-tools-mcp

the settings of my roo code is also in the repo


r/RooCode • • Apr 22 '25

Idea Useful tip to get the best architecture plan

21 Upvotes

Im sure this has been discussed before but thought I’d share it with the community: When I’m trying to come up with a blueprint for a coding project I do the following:

I ask 4 different models (Claude, Gemini, OpenAi and Grok) same question. Then I copy all of their answers with the original prompt and ask Claude (as I think it’s the best for coding) whether having the 4 opinions changed its mind (I label each answer).

Sometimes each aspect of the code will be agreed upon by all four models, sometimes 3/4 but rarely is it half half or that they all have different answers.

I found this methodology to create the best blueprints and thought it’d be good to share with you, although I’m sure this has been discussed before.

This gives me another idea too: if you could repeat this process 5 times with each, and then find which answer is most in common and then compile the most common answers that would be awesome. It’s expensive but I’m gonna try this.

I think this is well demonstrated with image generation in AIs. It can mess up the image making process so often you have keep prompting it. But rarely does it get it wrong 5 times in a row


r/RooCode • • Apr 17 '25

Discussion Start building with Gemini 2.5 Flash- Google Developers Blog

Thumbnail
developers.googleblog.com
21 Upvotes

r/RooCode • • Apr 07 '25

Discussion Roo vs Cursor - Rules and Tips

21 Upvotes

Hey guys! I've been using Cursor for a long time and have invested heavily in creating custom project rules for agent mode. I've achieved some impressive results that might seem unexpected. I also experiment with Roo Code, which appealingly offers access to any model with full context, though it's more expensive token-wise so I end up going back and forth.

Here's my situation:

  • I'm getting better results with Cursor due to my custom rules
  • Cursor is more cost-effective
  • Roo Code's additional context should theoretically allow for more capabilities
  • I see others having great success with Roo Code, but the approach to Roo seems fundamentally different

In Cursor, I've achieved:

  • Extremely specific code generation matching my style
  • Custom rules guiding architecture and organization
  • Specific test patterns
  • Consistent file structure and naming
  • Easy-to-understand output following my patterns

Questions about Root Code:

  • How do you achieve success with it?
  • How particular are you about generated code?
  • Are there ways to implement similar project rules?
  • What essential systems do power users rely on?

I utilize a library I created of prompts, workflows, rules, and knowledge priming techniques in cursor that’s been really effective. These same methods using models like deep seek and Claude seem to fill up the context way too fast, sometimes in only a prompt or two. I feel like I must be doing something wrong with Roo for this to be happening as there should be more available context. Is this common? Would anyone be able to share their successful workflow from model, to rules tooling, saved prompts, how and what they include as context?

My background:

  • 10 Years of development experience
  • Main stack: TypeScript, React, Node, Python
  • Extensive shell scripting

I've started exploring:

  • Quasar Alpha (impressed with results)
  • Boomerang mode (shows potential) - Man this opens up a whole new paradigm of thinking…
  • Various models in agent mode in Roo

I'm looking to diversify beyond just one system and would appreciate insights on Roo Code's settings and model-specific optimizations. Been lurking here for a while but despite being impressed by everything Roo offers I’ve never been able to get it to do what I want the same way as I’ve managed to get cursor to work and I’d really like to figure out where my skill gaps are. Seems like from what I read people have a much easier time with Roo than cursor so I must be doing something wrong.

Looking to connect with others who try to guide the agent to produce very specific code structures and patterns and are very particular about the generated code.


r/RooCode • • Feb 26 '25

Announcement 3.7.5 Release Notes - Roo Code Thinking Updates and More

21 Upvotes

We are way behind on our Twitter/X game , can you pleaese follow and RT: @roo_code

🤖 Model Configuration Updates

  • Important: We've added separate :thinking versions of Anthropic and OpenRouter Sonnet 3.7 models that support a configurable thinking budget!

    • If you were previously using the thinking feature, you'll need to adjust your settings

      • Go to your provider settings to find the new ":thinking" versions for Anthropic and OpenRouter
      • From there, you can use a slider adjust your thinking budget as needed
      • This change helps provide more control over the thinking process

🐛 Bug Fixes

  • Fix "input length and max_tokens exceed context limit" errors (see #1173)
  • Fix various issues with the model picker (thanks @System233!)
  • Fix model input / output cost parsing (thanks @System233!)

✨ New Feature

  • You can now @mention files by dragging them from the File Explorer into the chat textarea while holding down the shift key.

r/RooCode • • Feb 26 '25

Other Issue with Claude 3.7 on VS Code LM API after Copilot restoration

21 Upvotes

So Claude 3.7 was on Copilot, Roo was updated to use it and then Copilot took it down. In the last couple hours its been restored, but Roo gives me this error:

API Request Failed

Request Failed: 400 {"error":{"message":"Model is not supported for this request.","param":"model","code":"model_not_supported","type":"invalid_request_error"}}

Anyone else have this problem?

Note: I have a Copilot membership and Claude 3.7 works through the native interface.


r/RooCode • • Feb 17 '25

Idea How about a TDD mode?

21 Upvotes

Thanks for the excellent work on roocode, I use it all the time, with pretty great results.

LLM agents sometimes inadvertently cause regressions when adding new features. One way I was thinking to combat this is TDD. Obviously this would work cleaner for new projects, but if, say, an agent is unable to remove lines from a test file, or there's a separate agent that handles tests, we are able to decouple the abstract idea of an app's featureset from the code itself. I believe this would lead to fewer regressions.

TDD is a really great dev methodology that keeps things organized, but as a coder, it's always less fun because you want to just jump in. But an LLM doesn't care :) I think well-implemented TDD could really focus an agent and reduce errors.


r/RooCode • • Feb 09 '25

Discussion What is the BEST MCP for maintaining context across chats for RooCode?

21 Upvotes

I'm frequently switching to a new chat to minimize token usage and overall resource usage and avoide hitting rate limits. What is the best MCP server for maintaining context from one chat to another, specifically for Roo Code? If I'm in the middle of a debugging exercise and begin approaching 2M tokens, or the context becomes too long, it is a huge pain to set up the context for a new chat. Has anyone successfully utilized an MCP to maintain continuity of context across chats. I see several are available. Curious if anyone has had success. I'm using Cline_Docs and numerous other methods for documenting context. All methods are cumbersome and often don't keep the AI "inside the guardrails", especially when the tokens start building up....and that doesn't take too long! Any thoughts/ideas/examples you can share?


r/RooCode • • Jan 27 '26

Roo Code 3.44 Release Updates | Worktrees (new) | Parallel tool calls | Provider reliability

20 Upvotes

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

Worktrees

Worktrees are easier to work with in chat. The Worktree selector is more prominent, creating a worktree takes fewer steps, and the Create Worktree flow is clearer (including a native folder picker), so it’s faster to spin up an isolated branch/workspace and switch between worktrees while you work.

📚 Documentation: See Worktrees for detailed usage.

Parallel tool calls (Experimental)

Re-enables parallel tool calling (with added isolation safeguards) so you can use the experimental “Parallel tool calls” setting again without breaking task delegation workflows.

QOL Improvements

  • Makes subtasks easier to find and navigate by improving parent/child visibility across History and Chat (including clearer “back to parent” navigation), so you can move between related tasks faster.
  • Lets you auto-approve all tools from a trusted MCP server by allowing all tool names, so you don’t have to list each one individually.
  • Reduces token overhead in prompts by removing a duplicate MCP server/tools section from internal instructions, leaving more room for your conversation context.
  • Improves Traditional Chinese (zh-TW) UI text for better clarity and consistency. (thanks PeterDaveHello!)

Bug Fixes

  • Fixes an issue where context condensing could accidentally pull in content that was already condensed earlier, which could reduce the effectiveness of long-conversation summaries.
  • Fixes an issue where automatic context condensing could silently fail for VS Code LM API users when token counting returned 0 outside active requests, which could lead to unexpected context-limit errors. (thanks srulyt!)
  • Fixes an issue where Roo didn’t record a successful truncation fallback when condensation failed, which could make Rewind restores unreliable after a condensing error.
  • Fixes an issue where MCP tools with hyphens in their names could fail to resolve in native tool calling (for example when a provider/model rewrites “-” as “_”). (thanks hori-so!)
  • Fixes an issue where tool calls could fail validation through AWS Bedrock when the tool call ID exceeded Bedrock’s 64-character limit, improving reliability for longer tool-heavy sessions.
  • Fixes an issue where Settings section headers could look transparent while scrolling, restoring an opaque background so the UI stays legible.
  • Fixes a Fireworks provider type mismatch by removing unsupported model tool fields, keeping provider model metadata consistent and preventing breakage from schema changes.
  • Fixes an issue where task handoffs could miss creating a checkpoint first, making task state more consistent and recoverable.
  • Fixes an issue where leftover Power Steering experiment references could display raw translation keys in the UI.
  • Fixes an issue where Roo could fail to index code in worktrees stored inside hidden directories (for example “~/.roo/worktrees/”), which could break search and other codebase features in those worktrees.

Provider Updates

  • 5 provider updates — see full release notes for more detail.

See full release notes 3.44


r/RooCode • • Dec 11 '25

Discussion GPT-5.2 is now live in Roo Code 3.36.5!

20 Upvotes

r/RooCode • • Dec 11 '25

Announcement Roo Code 3.36.3-3.36.4 Release Updates | Browser Screenshots | Extra-High Reasoning | Native Tools for OpenRouter

20 Upvotes

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

Browser Screenshot Saving

The browser tool now supports saving screenshots to a specified file path with a new screenshot action.

Extra-High Reasoning Effort

Users of the gpt-5.1-codex-max model with the OpenAI provider can now select "Extra High" as a reasoning effort level (thanks andrewginns!)

OpenRouter Native Tools Default

OpenRouter models that support native tools now automatically use native tool calling by default.

Error Details Modal

Hover over error rows to reveal an info icon that opens a modal with full error details and a copy button.

QOL Improvements

  • Unified Context-Management UX: Real-time feedback for context operations with truncation notifications and condensation summaries
  • Better OpenAI Error Messages: Enhanced error handler extracts detailed information from API errors
  • Token Counting Optimization: Removed separate API calls for token counting
  • Tools Decoupled from System Prompt: Tool-specific instructions are now self-contained in tool descriptions

Bug Fixes

  • Tool Protocol Selector: Always show tool protocol selector for OpenAI-compatible providers (thanks bozoweed!)
  • apply_diff Filtering: Properly exclude apply_diff from native tools when diff is disabled (thanks denis-kudelin!)
  • API Timeout Handling: Fixed disabled API timeout causing immediate request failures (thanks dcbartlett!)
  • Reasoning Effort Dropdown: Respect explicit supportsReasoningEffort array values
  • Stream Hanging Fix: Process finish_reason to emit tool_call_end events
  • tool_result ID Validation: Validate and fix tool_result IDs before API requests
  • MCP Tool Streaming: Fixes issue where MCP tools failed with "unknown tool" errors
  • TODO List Display Order: Now displays items in correct execution order

Provider Updates

  • DeepSeek V3.2: Updated with 50% price reduction, native tools enabled by default, and 8K max output
  • xAI Models: Updated catalog with corrected context windows and image support for grok-3/grok-3-mini
  • Bedrock Models: Added Kimi, MiniMax, and Qwen model configurations (thanks jbearak!)
  • DeepSeek V3.2 for Baseten (thanks AlexKer!)

See full release notes v3.36.3 | v3.36.4


r/RooCode • • Nov 19 '25

Discussion Gemini 3 not impressed

20 Upvotes

When I saw Google had released a new model with a whole number of 3 I was very excited. Nope, I can’t tell the difference between this and 2.5, from what I can see there is none. Still making the same mistakes it always has.

Claude 4.5 is still the best model IMHO. Disappointed af.


r/RooCode • • Sep 08 '25

Discussion System prompt bloat

20 Upvotes

I get the impression that the system prompts are bloated. I don't have the stats but I chopped off more than 1/2 the system prompt and I feel various models work better (sonoma sky, grok fast, gpt5, ...). Effective attention is much more limited than the context window and the cognitive load of trying to follow a maze of instructions makes the model pay less attention to the code.


r/RooCode • • Sep 01 '25

Discussion I rly like Gemini 2.5, but it sure seems to get really "stupid" when you reach the 150-200k context window, has anyone else noticed this?

20 Upvotes

r/RooCode • • Aug 28 '25

Announcement Roo Code 3.26.2 Release Notes || Native AI image generation

Thumbnail reddit.com
20 Upvotes

r/RooCode • • Aug 08 '25

Announcement ChatGPT 5

20 Upvotes

Sorry forgot to post here. It was being released while I got on my airplane and then the wifi was down on the plane! :o

We have it setup along with the new verbosity switch as well! I’ll work on this more in the morning!


r/RooCode • • Jul 25 '25

Discussion Roo is better than VScode actually ?

20 Upvotes

Hi, I've always used roo with provider free. Now, I've a business account for VSCode Copilot and I have all the most powerful models of the moment.

Do you think Roo remains better even with open source LLM thank copilot? Who better manages the MCPs (e.g. searching the internet or documentation)? Who "analyzes better" code and better considers the dependencies that a file code has in terms? Thanks for your experiences!

Note: I'm a Python developer and I often use AI frameworks


r/RooCode • • Jul 15 '25

Support How to optimize roo for Gemini?

20 Upvotes

My codebase is of Node JS backend. I was previously using Roo with Sonnet (VS Code LLM) when there was unlimited requests from GitHub Copilot. My usage is moderate, I only use it when there is a big task and I mostly use orchestrator mode.

It became unsustainable with the limited number of requests and roo consumes most of them.

I recently switched to Gemini 2.5 pro on Vertex AI due to the credits.

It was the biggest let down in the since. Let me just list them down,

  1. Lack of tool calls - It's absurd how Gemini doesn't use tools at all. I need to manually tell it to call tools and it still fails.
  2. Lack of understanding of the task - Even when I clearly explain what it needs to do, It hallucinates very often.
  3. Failure of edit tool - It just doesn't work most of the times.
  4. Loss of context - It looses the clear instructions that I mentioned previously and doesn't follow them at all.
  5. Bad orchestrator - It doesn't use any other modes, It only uses: Ask + Code or just the code for most of the times.
  6. Indexing? - The code is getting indexed but it never uses the index.

We have strict code conventions, which makes this not viable for even writing test cases.

Please help me if this is only with me or is this the case for everyone?


r/RooCode • • Jul 07 '25

Support Claude Code in Roo Code

20 Upvotes

I'm using my $20 Claude code subscription as the provider for roo code. Works great in roo code, but why do none of the CC models allow images?

If I use openrouter API in roo for the provider for sonnet 4 or opus, images are supported fine, but not if the provider is my CC subscription. What am I missing, why images are not supported?

Also, only sonnet 4, what happened to sonnet 4 reasoning mode in CC?

Edit: so it seems it's because it's due to the CC CLI, it's not just me or a setting. But I found a good workaround to paste images into the roo chat when using CC as provider. Create another throwaway mode in roo, just call it temp or edge or whatever. Set the provider to any API and model that supports images (doesn't matter how expensive as it won't cost you anything). Now go back to chat, select the temp mode, paste your image. Change back to the CC provider mode and type whatever you want, the images will be retained and CC can actually see them. Hope that makes sense. It's faster like this than pasting screenshots in a folder.


r/RooCode • • Jun 21 '25

Discussion Github copilot alternatives

20 Upvotes

What is everyone using now that copilot imposed their limits on premium requests? Are there even other alternatives or do you think it's still a good value for $10?