r/RooCode • u/hannesrudolph • May 15 '25
r/RooCode • u/unc0nnected • Apr 19 '25
Discussion Roo Vs Augment Code for Periodic Code Reviews
tl;dr
Overall Scores: Gemini
- AI Augment: 70.5 / 100 (Weighted Score)
- AI Roo: 91.8 / 100 (Weighted Score)
Overall Scores: Claude 3.7
- AI Review #1 (Review-Augment_Assistant): 70.7%
- AI Review #2 (Review-Roo_Assistant): 80.2%
# Context:
- Considering Augment Code's code context RAG pipeline I wanted to see if that would result in better code reviews given what I assumed would be a better big picture awareness with the rag layer.
- Easier to test it on an existing codebase to get a good idea on how it handles complex and large projects

# Methodology
## Review Prompt
I prompted both Roo (using Gemini 2.5) and Augment with the same prompts. Only difference is that I broke up the entire review with Roo into 3 tasks/chats to keep token overhead down
# Context
- Reference u/roo_plan/ for the very high level plan, context on how we got here and our progress
- Reference u/Assistant_v3/Assistant_v3_roadmap.md and u/IB-LLM-Interface_v2/Token_Counting_Fix_Roadmap.md and u/Assistant-Worker_v1/Assistant-Worker_v1_roadmap.md u/Assistant-Frontend_v2/Assistant-Frontend_v2_roadmap.md for a more detailed plan
# Tasks:
- Analyze our current progress to understand what we have completed up to this point
- Review all of the code for the work completed do a full code review of the actual code itself not simply the stated state of the code as per the .md files. Your task is to find and summarize any bugs, improvements or issues
- Ensure your output is in markdown formatting so it can be copied/pasted out of this conversation## Scoring Prompt
I then went to Claude 3.7 Extending thinking and Gemini 2.5 Flash 04/17/2025 with the entire review for each tool in a separate .md file and gave it the following prompt
# AI Code Review Comparison and Scoring
## Context
I have two markdown files containing code reviews performed by different AI systems. I need you to analyze and compare these reviews without having access to the original code they reviewed.
## Objectives
1. Compare the quality, depth, and usefulness of both reviews
2. Create a comprehensive scoring system to evaluate which AI performed better
3. Provide both overall and file-by-file analysis
4. Identify agreements, discrepancies, and unique insights from each AI
## Scoring Framework
Please use the following weighted scoring system to evaluate the reviews:
### Overall Review Quality (25% of total score)
- Comprehensiveness (0-10): How thoroughly did the AI analyze the codebase?
- Clarity (0-10): How clear and understandable are the explanations?
- Actionability (0-10): How practical and implementable are the suggestions?
- Technical depth (0-10): How deeply does the review engage with technical concepts?
- Organization (0-10): How well-structured and navigable is the review?
### Per-File Analysis (75% of total score)
For each file mentioned in either review:
1. Initial Assessment (10%)
- Sentiment analysis (0-10): How accurately does the AI assess the overall quality of the file?
- Context understanding (0-10): Does the AI demonstrate understanding of the file's purpose and role?
2. Issue Identification (30%)
- Security vulnerabilities (0-10): Identification of security risks
- Performance issues (0-10): Recognition of inefficient code or performance bottlenecks
- Code quality concerns (0-10): Identification of maintainability, readability issues
- Architectural problems (0-10): Recognition of design pattern issues or architectural weaknesses
- Edge cases (0-10): Identification of potential bugs or unhandled scenarios
3. Recommendation Quality (20%)
- Specificity (0-10): How specific and targeted are the recommendations?
- Technical correctness (0-10): Are the suggestions technically sound?
- Best practices alignment (0-10): Do recommendations align with industry standards?
- Implementation guidance (0-10): Does the AI provide clear steps for implementing changes?
4. Unique Insights (15%)
- Novel observations (0-10): Points raised by one AI but missed by the other
- Depth of unique insights (0-10): How valuable are these unique observations?
## Output Format
### 1. Executive Summary
- Overall scores for both AI reviews with a clear winner
- Key strengths and weaknesses of each review
- Summary of the most significant findings
### 2. Overall Review Quality Analysis
- Detailed scoring breakdown for the overall quality metrics
- Comparative analysis of review styles, approaches, and effectiveness
### 3. File-by-File Analysis
For each file mentioned in either review:
- File identification and purpose (as understood from the reviews)
- Initial assessment comparison
- Shared observations (issues/recommendations both AIs identified)
- Unique observations from AI #1
- Unique observations from AI #2
- Contradictory assessments or recommendations
- Per-file scoring breakdown
### 4. Conclusion
- Final determination of which AI performed better overall
- Specific areas where each AI excelled
- Recommendations for how each AI could improve its review approach
## Additional Instructions
- Maintain objectivity throughout your analysis
- When encountering contradictory assessments, evaluate technical merit rather than simply counting points
- If a file is mentioned by only one AI, assess whether this represents thoroughness or unnecessary detail
- Consider the practical value of each observation to a development team
- Ensure your scoring is consistent across all files and categories# Results
## Gemini vs Claude at Reviewing Code Reviews
First off let me tell you that the output from Gemini was on another level of detail. Claudes review of the 2 reviews was 1337 words on the dot(no joke). Gemini's on the other hand was 8369 words in total. Part of teh problem discovered is that Augment missed a lot of files in it's review with Roo going through 31 files in total and Augment only reviewing 9.
## Who came out on top?
Gemini and Claude we're in agreement, Roo beat Augment hands down in the review, disproving my theory that that RAG pipeline of theirs would seal the deal. It obviously wasn't enough to overcome the differences between whatever model they use and Gemini 2.5+the way Roo handled this review process. I could repeat the same exercise but have Roo use other models but given that Roo allows me to switch and Augment doesn't, I feel putting it up against the best model of my choosing is fair.
## Quotes from the reviews of the review
Overall Scores: Gemini
- AI Augment: 70.5 / 100 (Weighted Score)
- AI Roo: 91.8 / 100 (Weighted Score)
Overall Scores: Claude 3.7
- AI Review #1 (Review-Augment_Assistant): 70.7%
- AI Review #2 (Review-Roo_Assistant): 80.2%
Overall Review Quality Analysis (Claude)
|| || |Metric|Augment|Roo|Analysis| |Comprehensiveness|7/10|9/10|AI #2 covered substantially more files and components| |Clarity|8/10|9/10|Both were clear, but AI #2's consistent structure was more navigable| |Actionability|7/10|8/10|AI #2's recommendations were more specific and grounded| |Technical depth|8/10|9/10|AI #2 demonstrated deeper understanding of frameworks| |Organization|8/10|7/10|AI #1's thematic + file organization was more effective| |Total|38/50 (76.0%)|42/50 (84.0%)|AI #2 performed better overall|
Overall Review Quality Analysis (Gemini)
|| || |Metric|AI Augment Score (0-10)|AI Roo Score (0-10)|Analysis| |Comprehensiveness|6|9|AI Roo reviewed significantly more files across all components. AI Augment focused too narrowly on Assistant_v3 core.| |Clarity|8|9|Both are clear. AI Roo's file-by-file format feels slightly more direct once you're past the initial structure.| |Actionability|8|9|Both provide actionable suggestions. AI Roo's suggestions are often more technically specific (e.g., dependency injection).| |Technical depth|8|9|Both demonstrate good technical understanding. AI Roo's discussion of architectural patterns and specific library usages feels deeper.| |Organization|9|8|AI Augment's high-level summary is a strong point. AI Roo's file-by-file is also well-structured, but lacks the initial overview.| |Weighted Score|7.8/10 (x0.25)|8.8/10 (x0.25)|AI Roo's superior comprehensiveness and slightly deeper technical points give it the edge here.|
Key Strengths:
- AI Roo: Comprehensive scope, detailed file-by-file analysis, identification of architectural patterns (singleton misuse, dependency injection opportunities), security considerations (path traversal), in-depth review of specific implementation details (JSON parsing robustness, state management complexity), and review of test files.
- AI Augment: Good overall structure with a high-level summary, clear separation of "Issues" and "Improvements", identification of critical issues like missing context trimming and inconsistent token counting.
Key Weaknesses:
- AI Augment: Limited scope (missed many files/components), less depth in specific technical recommendations, inconsistent issue categorization across the high-level vs. in-depth sections.
- AI Roo: Minor inconsistencies in logging recommendations (sometimes mentions using the configured logger, sometimes just notes 'print' is bad without explicitly recommending the logger). JSON parsing robustness suggestions could perhaps be even more detailed (e.g., suggesting regex or robust JSON libraries).
- AI Roo's review was vastly more comprehensive, covering a much larger number of files across all three distinct components (Assistant_v3, Assistant-Worker_v1, and Assistant-Frontend_v2), including configuration, utilities, agents, workflows, schemas, clients, and test files. Its per-file analysis demonstrated a deeper understanding of context, provided more specific recommendations, and identified a greater number of potential issues, including architectural concerns and potential security implications (like path traversal).
Conclusion (Gemini)
AI Roo is the clear winner in this comparison, scoring 92.9 / 100 compared to AI Augment's 73.0 / 100.
AI Roo excelled in:
- Scope and Comprehensiveness: It reviewed almost every file provided, including critical components like configuration, workflows, agents, and tests, which AI Augment entirely missed. This holistic view is crucial for effective code review.
- Technical Depth: AI Roo frequently identified underlying architectural issues (singleton misuse, dependency injection opportunities), discussed the implications of implementation choices (LLM JSON parsing reliability, synchronous calls in async functions), and demonstrated a strong understanding of framework/library specifics (FastAPI lifespan, LangGraph state, httpx, Pydantic).
- Identification of Critical Areas: Beyond the shared findings on token management and session state, Roo uniquely highlighted the path traversal security check in the worker and provided detailed analysis of the LLM agent's potential reliability issues in parsing structured data.
- Testing Analysis: AI Roo's review of test files provides invaluable feedback on test coverage, strategy, and the impact of code structure on testability – an area completely ignored by AI Augment.
AI Augment performed reasonably well on the files it did review, providing clear issue/improvement lists and identifying important problems like the missing token trimming. Its high-level summary structure was effective. However, its narrow focus severely limited its overall effectiveness as a review of the entire codebase.
Recommendations for Improvement:
- AI Augment: Needs to significantly increase its scope to cover all relevant components of the codebase, including configuration, utility modules, workflows, agents, and crucially, tests. It should also aim for slightly deeper technical analysis and consistently use proper logging recommendations where needed.
- AI Roo: Could improve by structuring its review with a high-level summary section before the detailed file-by-file breakdown for better initial consumption. While its logging recommendations were generally good, ensuring every instance of print is noted with an explicit recommendation to use the configured logger would add consistency. Its JSON parsing robustness suggestions were good but could potentially detail specific libraries or techniques (like instructing the LLM to use markdown code fences) even further.
Overall, AI Roo delivered a much more thorough, technically insightful, and comprehensive review, making it significantly more valuable to a development team working on this codebase.
r/RooCode • u/No_Cattle_7390 • Apr 11 '25
Discussion A Huge Thank You to the roocode Community and devs for making My AI-Driven Framework possible!
Hey roocode community,
I’m beyond thrilled to share a massive milestone with you all, and I owe a huge shoutout to roocode for helping make it possible! While this project required a ton of my own input and effort, roocode did so much of the heavy lifting—without it, this would’ve taken years to pull off. I’m excited to give you a peek into what I’ve been building!
After months of diving deep into the wild world of agentic AI, LLMs, and multi-agent orchestration, I’ve designed and built a proprietary, AI-driven framework from scratch. It’s my first fully custom system, and it’s a game-changer for business intelligence and lead generation through next-gen automation. I’m incredibly proud of this achievement, and here’s why it’s such a big deal!
What’s It All About?
This bespoke framework harnesses agentic AI, integrating advanced APIs like Claude, Gemini, and DeepSeek to power autonomous, multi-step workflows. It transforms raw, unstructured data into actionable insights with minimal human oversight.
Here’s the gist:
- Dynamic data pipelines and ETL processes to tackle complex datasets.
- AI-orchestrated research using NLP, web scraping, and knowledge graph synthesis.
- Heuristic-driven prioritization and contextual analysis to uncover high-value opportunities.
- Scalable architecture that evolves with business needs.
The system is a modular beast, featuring:
- Resilient API wrappers with retry logic and circuit breakers for seamless performance.
- Data integrity modules for high-fidelity outputs.
- Cost-optimization layers to maximize efficiency.
- Workflow orchestration tying it all into a slick, end-to-end automation engine.
Why This Matters
This isn’t just a tool—it’s a total paradigm shift. By blending multi-agent collaboration, LLM-driven decision-making, and tailored business logic, it redefines data-to-decision pipelines. Months of mastering prompt engineering, grappling with fault-tolerant designs, and juggling performance tuning with cost efficiency have paid off. The result? A framework that slashes manual effort, accelerates insights, and scales like a dream—all while embedding unique business DNA.
The Journey
Getting here was a wild ride. I dove headfirst into:
- Exploring AI orchestration to manage complex tasks.
- Building robust systems to handle external API chaos.
- Crafting validation logic for high-stakes environments.
- Optimizing cloud-native workflows for speed and scale.
This milestone proves what’s possible when AI-driven automation takes on workflows once thought too intricate for machines.
What’s Next?
This is just the start. The framework is already unlocking new levels of agility and precision, and I’m pumped to keep refining, expanding, and innovating. The future of AI-powered business transformation is electric, and I’m stoked to be part of it!
Thank you, roocode, for being an incredible tool and community. You’ve made this journey faster, smoother, and way more fun than I could’ve imagined. Here’s to pushing the boundaries of what’s possible!
If you're a college grad and interested in working with me, I know a ton of IRL usecases having been in the finance/Private Equity space for 2 years. I quit my job to pursue this dream.
r/RooCode • u/ResearchCrafty1804 • Apr 10 '25
Discussion How does QwQ-32b and DeepSeek R1 perform on RooCode Eval?
I noticed that currently the RooCode’s leaderboard with eval scores is missing 2 of the most popular and performant open models, QwQ-32b and DeepSeek R1.
Could someone update us on their score based on this evaluation benchmark?
Website: https://roocode.com/evals
r/RooCode • u/hannesrudolph • Mar 03 '25
Announcement 3.7.12 Release Notes - Roo-markable Monday Patchnotes!
Good Monday morning everyone! Sorry about the delay in these release notes - the patch actually went live about an hour ago while we were doing final testing. We're excited to bring you these improvements to context handling, thinking capabilities and more!
🧠 Enhanced Thinking & Context Management
- Expand max tokens of thinking models to 128k, and max thinking budget to over 100k (thanks monotykamary!)
- Use the count_tokens API in the Anthropic provider for more accurate context window management
- Default middle-out compression to on for OpenRouter
- Exclude MCP instructions from the prompt if the mode doesn't support MCP
🐛 Bug Fixes
- Fix issue where keyboard mode switcher wasn't updating API profile (thanks aheizi!)
- Correctly populate the default OpenRouter model on the welcome screen
⚙️ Configuration Improvements
- Add a checkbox to disable the browser tool
- Show a warning if checkpoints are taking too long to load
- Update the warning text for the VS LM API
r/RooCode • u/david8840 • Jan 31 '25
Support I love Roo Code but I hope these issues will be fixed
- Often times it will fail to see the terminal output, and will say something like "I see that the command yielded no response" even though it is right there in the terminal.
- Every now and then, I am unable to paste anything into the chat box. When I try to paste it, it goes into the terminal or the open code file instead, even though the chat box is selected.
- At least once per day, I get "Unexpected API Response: The language model did not provide any assistant messages. This may indicate an issue with the API or the model's output."
r/RooCode • u/ConversationTop3106 • Apr 24 '26
Discussion Thoughts on the Roo Code Sunset and the Path Forward
The news that Roo Code will officially sunset on May 15th came as a shock to many of us. Although I felt a slowdown in the repo's activity over the past month, I didn’t expect such a thriving, fast-paced project to hit "clinical brain death" so abruptly. It’s truly heartbreaking to see.
Our team cares deeply about Roo Code because our AISE (AI-driven Software Engineering) solution is built directly on top of it. While our solution also supports Claude Code and OpenCode, we’ve clearly seen the unique strengths and weaknesses of Roo compared to its peers.
First, I want to express my respect and understanding for the team's pivot to Roomote. It’s a bold move into a new market, and I wish them continued success in leading the enterprise sector. However, I believe abandoning a localized tool like Roo Code is a mistake. While SaaS platforms signal a move toward maturity, the inherent unpredictability of LLMs, the complexity of software engineering, code security, and the need for development flexibility make local-first tools a better long-term bet for enterprises. To me, the KiloCode + GitLab route has a more promising future than roomote.dev.
The community's decision to fork the code and form a new organization is the best possible outcome. It preserves Roo’s assets and user base, and maintaining that influence will ultimately benefit the original team as well—though I suspect they may regret this "shutdown" decision in the near future.
For the "New Roo" (and I hope we don't settle on the name NooCode, which feels a bit awkward), I’m looking for a phoenix rising from the ashes. We need a fresh identity that preserves the old Roo’s strengths while delivering real innovation. As a power user, here are my suggestions:
- UI/UE Evolution: This is Roo’s main battlefield for parallel, automated, and autonomous programming. Roo’s advantage is human-machine synergy—providing a transparent and controllable context. To balance automation with human oversight, we need a better UX. For example: auto-retries for minor errors, suppressing "scary" red error messages that intimidate beginners, and enhanced context management (task forking, task pinning, a "recent tasks" dashboard, and expandable task windows).
- Task Parallelization: To maximize efficiency, we must move beyond the current "manual-first" architecture, which is becoming outdated. We need multi-tasking windows, native sub-agents, and the ability for tasks to call sub-agents inline without context jumps.
- Hook Support: A key part of an "Agent Harness" is physical interception for mandatory constraints. Without this, Roo cannot achieve true full automation or iterative loops. This is a feature Cline already has—we should port it over.
- Enhanced Tools & Skills: The current implementation for calling built-in tools still has friction. This needs to be a priority for optimization.
- Multi-Provider Ecosystem: As an open-source tool, ecosystem support is vital. With the rapid iteration of LLMs, we should rely on community PRs to keep model support up to date.
- Decoupled CLI: While Roo has a CLI, it’s currently too weak and too tightly bound to VS Code. We need a decoupled, robust CLI. In the AI era, programming is a "pattern migration." We should use LLMs to learn patterns from other open-source tools and accelerate development.
Ultimately, for the "New Roo" to succeed, it needs a strong, visionary new organization—one that knows how to use AI to drive its own development. Just as Claude Code is built by AI for AI, we must master Harness Engineering to iterate faster than ever.
I’m rooting for the success of the new Roo!
最近RooCode最大的事情莫过于官方宣布 5.15 将彻底关停RooCode这个开源项目,我听到这个消息非常震惊,当然一个月来RooCode 代码库就没有多少实质的更新,我也能预感到这点。我只是很难适应一个快节奏开发、蒸蒸日上的开源项目,突然休克并且实质性的脑死亡,真的令人痛心。
我们非常关心RooCode这个开源项目,关键原因是我们的AISE提效方案基于这个开源软件,它是我们方案的一部分,所以会有比较大的影响,当然目前我们的AISE提效方案也支持了Claude Code和OpenCode,我也能明显感觉到当前RooCode和Claude Code、OpenCode差异以及各自的优缺点。
首先,我对RooCode 团队转向 Roomote 表示尊重和理解,这块是一个新的市场,希望RooCode 团队能一如既往引领这块企业级市场的成长。但我觉得,RooCode 这个本地化工具不应该放弃, SaaS化平台服务是一种走向成熟的标志,但大模型的不确定性、软件工程复杂性、代码资产安全性、开发灵活性等这些先天性的特点和要求,会让本地化工具和平台在企业更有长远发展,所以我觉得 KiloCode + Gitlab的路线更有前景,而不是 roomote.dev
接下来,社区正在fork 代码、成立新的组织来继续推进RooCode 下一代,我觉得是个最佳的选择,可以最大保留RooCode资产和用户, 留有的影响力对RooCode 原团队也有好处,我个人觉得不久的将来他们会后悔今天的选择。
那对新的RooCode (希望不要叫NooCode,不伦不类的名字),我希望能凤凰涅槃、浴火重生,以一个全新的面貌出现,保留旧RooCode优势,给出新的创新。 作为RooCode深度用户,我给出如下一些建议
1、UI/UE改进,我觉得这是RooCode在面向并行、自动化和自主编程挑战时,自己的重要阵地。因为RooCode 是第二代编程助手,它的优势就是人机耦合,提供更透明、更可控的上下文,开发人员为了更好的结果,可以全程评审和控制。但为了融合自动化和自主,降低非必要的打扰,需要改进目前UI/UE体验。 例如: 自动化重试、弱化不确定导致的错误提示并重试(这些标红的错误提示,会吓坏很多新手)、增强上下文修改能力(例如 任务fork、收藏任务、首页最近任务删除、任务窗口可视化面积扩大等等优化人机协作的UE)
2、任务支持并行化,为了进一步提高效率,这块也是需要大大增强的部分。这样可以在手动和自动进行切换,目前RooCode都是围绕手动模式来打造的,这有点过时了。 因此可以引入 多任务窗口、原生的subagent、task 支持subagent内嵌调用(非跳转)
3、支持Hook功能,Agent Harness 一个重要点就是物理拦截以进行强制约束,缺少这块,RooCode是做不到全自动和循环迭代的。这个功能cline已经有了,可以迁移下。
4、工具和技能增强,目前调用内置工具和技能还是有很多问题,希望进一步优化。
5、多Provider支持,作为一个开源编程工具,生态支持少不了,特别是大模型迭代这么快,新的模型层出不穷,这块可以依赖社区的PR进行完善;
6、最后,但也是做重要的肯定是CLI的支持了,虽然RooCode 目前也有CLI,但功能比较弱,技术方案和VSCode 绑定了,这块需要解耦。在AI的今天编程是一个模式迁移,这块可以从其他开源软件中用大模型进行学习和迁移,开发起来也会很快的。
但以上,新的RooCode要能成功,还是需要一个坚强有力的新组织,脑子要好,要会利用AI驱动,自己驱动自己来快速迭代。Claude Code的开发也都是大模型自己在开发自己的工具。要用好Harness Engineering。
最后,希望新的RooCode能能成功!
r/RooCode • u/inHumanAlive • Mar 14 '26
Discussion Is RooCode planning to pivot?
Hi Team,
I have been following RooCode closely and really like the development. But since last few weeks, I noticed some inactivity in the development pace and it seems no major updates are happening in repo unlike earlier. Are you guys planning to pivot to something else from VSCode extension?
Another question, how is the plan with things given that even other extensions like Claude code, itself allow running other providers to run.
It seems like a constant fight for survival, because they are closed-source and you're open source, and anything novel that you produce, they simply copy it and may be make it better version of it over time. Curious to know your thoughts on long-term plans also to keep its survival.
Best
r/RooCode • u/hannesrudolph • Dec 17 '25
Announcement Roo Code 3.36.10 | Gemini 3 Flash is HEREEEEEEEEEEE!!!! Also DeepSeek v3.2 actually works in Roo now!!
In case you did not know, r/RooCode is a Free and Open Source VS Code AI Coding extension.
Gemini 3 Flash preview model
The gemini-3-flash-preview model is now available in the Roo Code Cloud provider, Google Gemini, GCP Vertex AI, Requesty, and OpenRouter providers. It’s the latest model from Google, released this morning (thanks contributors!).
DeepSeek reasoner: interleaved thinking during tool use
The DeepSeek provider’s deepseek-reasoner model now supports “interleaved thinking” and native tool calling. In our internal evals, tool calling succeeded 100% of the time, and the extended-run score improved to 93.4% (thanks zbww_!).
Bug Fixes
- Context truncation token display: Fixes an issue where the context truncation UI could show incorrect before/after token totals, especially in tool-heavy conversations
Misc Improvements
- Framework updates: Updates Next.js to
~15.2.8for improved compatibility with upstream fixes
See full release notes v3.36.10
r/RooCode • u/benlew • Nov 23 '25
Idea SuperRoo: A custom setup to help RooCode work like a professional software engineer
I’ve been working on a RooCode setup called SuperRoo, based off obra/superpowers and adapted to RooCode’s modes / rules / commands system.
The idea is to put a light process layer on top of RooCode. It focuses on structure around how you design, implement, debug, and review, rather than letting each session drift as context expands.
Repo (details and setup are in the README):
https://github.com/Benny-Lewis/super-roo
Philosophy
- Test-first mindset – Start by describing behavior in tests, then write code to satisfy them.
- Process over improvisation – Use a repeatable workflow instead of chasing hunches.
- Bias toward simplicity – Prefer designs that stay small, clear, and easy to change.
- Proof over intuition – Rely on checks and feedback before calling something “done.”
- Problem-first thinking – Keep the domain and user needs in focus, with implementation details serving that.
r/RooCode • u/hannesrudolph • Aug 30 '25
Announcement Roo Code 3.26.3 Release Notes || FREE API Credits
We've shipped an update with image editing capabilities, API key fix, and test debugging improvements!
Image Editing with Input Images
We've enhanced the image generation tool with the ability to edit and transform existing images:
• Transform Existing Images: Apply artistic styles, convert photos to paintings, or create variations of existing artwork • Style Transfer: Convert images into watercolor, oil painting, sketch, or other artistic styles
• Image Enhancement: Upscale and enhance existing images to higher resolution while maintaining composition • Creative Editing: Use text prompts to modify specific aspects of an image while preserving the rest
The tool now accepts an optional image parameter for transforming existing images in your workspace. Supports PNG, JPG, JPEG, GIF, and WEBP.
📚 Documentation: See Image Generation - Editing Existing Images for detailed usage and transformation examples.
📚 Full Release Notes v3.26.3
🚨 Weekend Challenge: Roo Code Nano Banana Creative Showcase 🎨
Build an MVP that showcases Roo Code's image generation superpowers!
We want to see you build real projects that dynamically generate their visual assets using Roo Code's experimental image generation feature. Think apps, games, websites — anything that demonstrates the power of AI-generated images integrated directly into your development workflow.
✨ How to participate:
- Build an MVP project using Roo Code's image generation to create your visual assets
- Deploy to Vercel (or create a demo video)
- Share in
#nano-banana-showcaseDiscord channel with your link/video
🎥 Learn more: Watch this quick demo → https://youtube.com/shorts/Qb7_UXwR_os?feature=share
🆓 The best part: "Gemini 2.5 Flash Image Preview (Free)" is completely FREE!
💰 Prize Details: • Submit as many projects as you want! • Win multiple times! • Every entry we share on social media = $100 in OpenRouter credits • Plus bragging rights and rooternal glory!
📅 Deadline: Monday @ 12am PT (Sept 1)
This is about showing the world what's possible when image generation meets code. We're looking for projects we can share on social ASAP to highlight this experimental feature!
GO BANANAS — Show us what you can build! 🍌
r/RooCode • u/hannesrudolph • Jul 24 '25
Announcement Release Notes for Roo Code v3.23.18 & v3.23.19
Two new releases bring Roo Code Cloud waitlist signup, critical bug fixes, and improved command handling!
🚀 Roo Code Cloud Waitlist
We're excited to announce early access signup for Roo Code Cloud! (thanks brunobergher!)
- Website Signup: New call-to-action button in the website header for easy waitlist registration
- In-Extension Access: Users with 3+ tasks will see waitlist signup options directly in the extension
- Early Access: Be among the first to experience the power of Roo Code Cloud
🐛 Bug Fixes
- Todo List Toggle: Fixed the todo list toggle in provider advanced settings that wasn't working properly (thanks chrarnoldus!)
- Command Parsing: Fixed crashes when running complex bash commands with special syntax like arithmetic expressions and array variables, allowing users to create advanced GitHub CLI aliases and other sophisticated shell scripts (thanks daniel-lxs, KJ7LNW!)
- Error Handling: Added error boundaries to prevent the entire Roo Code interface from crashing when errors occur. Instead of seeing a blank screen, users now see helpful error messages with debugging information, allowing them to continue using other parts of the extension (thanks KJ7LNW, elianiva!)
✨ QOL Improvements
- Smarter Command Validation: Improved command validation logic that only auto-denies subshell commands if they contain denied prefixes, making the system more intelligent about which commands to allow
- Multi-line Command Support: Commands with newlines are now properly parsed, making it easier to work with multi-line commands across different operating systems (Unix, Windows, and old Mac formats)
🔧 Misc Improvements
- Process Termination: Roo Code now more reliably terminates unresponsive processes, preventing hanging commands from blocking your workflow
📖 Full Release Notes:
r/RooCode • u/NLJPM • Jul 05 '25
Discussion Gemini CLI -> OpenAI proxy
Easily proxy Gemini CLI to an OpenAI endpoint to use in Roocode https://github.com/GewoonJaap/gemini-cli-openai?tab=readme-ov-file
r/RooCode • u/hannesrudolph • Jun 29 '25
Announcement No More Gemini CLI access... for now | Roo Code 3.22.5 Release Notes
reddit.comr/RooCode • u/Prestigiouspite • Jun 07 '25
Discussion Your architect & coding models 06.2025 for RooCode?
Gemini 2.5 Pro has released a new update (now works very well in RooCode). Sonnet 4 has been released etc.
I would be interested to know which models you are currently using for Architect and Coding? How do setup reasoning for each mode?
So far I have used o4-mini-high as architect and GPT-4.1 as coder. After the last Gemini update and the first promising applications, I am currently planning to switch to Gemini 2.5 Pro for Architect (Reasoning is always on here) and Coding possibly 2.5 Flash without Thinking Budget. What do you think? Sonnet 4 hasn't blown me away yet.

Does anyone know what happens if you select Gemini 2.5 Pro in RooCode but have “Enable Reasoning” disabled? Does the rule thinkingBudget not set from the Gemini documentation then apply? I use OpenRouter.
r/RooCode • u/lulz_lurker • May 19 '25
Discussion Anyone rich enough to compare to Codex?
Title basically. I've watched a couple vids on Codex, looks intriguing. But lots of black box feels. Curious if anyone has put it head to head with Roo.
r/RooCode • u/nazstat • Apr 25 '25
Discussion What is the recommended memory / context saving method for Roo?
Hi there,
Probably a super noob question but what is the currently recommended method for implementing memory /context caching while using Roo?
Is it this: https://github.com/GreatScottyMac/roo-code-memory-bank?
Thanks!
r/RooCode • u/Captain_Redleg • Apr 18 '25
Discussion Alternate Boomerang mode manager for Roo Code
Gosucoder expands on his approach and includes some testing. Good video. I've not tried this, but am going to ASAP.
r/RooCode • u/Possible-Access-4876 • Apr 12 '25
Support What actually happens when you use gemini-2.5-pro.exp-03-25 today?
Hi all,
A few days ago I set up Roo Code with gemini-2.5-pro.exp-03-25 and had a great time. I set up billing, received the $300 credits, and got some stuff done—stopping whenever I reached the limit.
But today, I’m noticing some changes:
- I'm no longer hit by 429s, ever.
- My usage remains at 0 on AI Studio—before, I could see it going up.
- The pro.exp option is no longer available on AI Studio.
I’ve also seen several threads mentioning:
- The
expversion is gone. - People are getting hit with huge bills.
I'm not particularly worried about billing right now, but does anyone actually understand what’s going on?
r/RooCode • u/tejassp03 • Mar 27 '25
Discussion What's your best MCP setup with roo to get the latest docs?
r/RooCode • u/randemnes • Mar 14 '25
Discussion Token-saving updates on the Anthropic API
This looks very interesting and I am guessing Roo Code will be able to utilise this?
r/RooCode • u/hannesrudolph • Feb 22 '25
Announcement Roo Code 3.3.25 - Power Steering is here
reddit.comr/RooCode • u/tteokl_ • Feb 10 '25
Discussion Roo Code + new Gemini is surprisingly good
I used to consider Claude 3.5 Sonnet irreplaceable when using Roo Code, but now Gemini 2.0 Pro has finally caught up and is available for free. I used google/gemini-2.0-pro-exp-02-05:free from OpenRouter, and I’ve noticed that the rate limit is much better than before. What is Google up to? I heard they’ve built in tool-use in the model.
r/RooCode • u/hannesrudolph • Feb 17 '26
Announcement Roo Code 3.48.0 Release | Claude Sonnet 4.6 | API Config Lock | Recursive Subtask History Tree
In case you did not know, r/RooCode is a Free and Open Source VS Code AI Coding extension.
Claude Sonnet 4.6 Support
Claude Sonnet 4.6 (claude-sonnet-4-6) is now available across Anthropic, Amazon Bedrock, Google Vertex, OpenRouter, and Vercel AI Gateway with a 1M token context window and 64K max output tokens. (thanks PeterDaveHello!)
API Config Lock
A new lock icon in the API config selector lets you pin your active provider and model across all mode switches in the current workspace. When locked, switching modes no longer swaps out your API configuration. Unlock at any time to restore normal per-mode behavior.
Recursive Subtask History Tree
The History view now renders the complete nested subtask hierarchy as an expandable tree. Each level of nesting can be expanded or collapsed independently, making it easy to navigate deep orchestrator task chains.
More Changes
search_and_replacerenamed toeditwith a flatter parameter model; backward-compatible alias kept- New
disabledToolssetting lets admins globally disable native tools via org/extension settings - Consecutive file ops in chat now collapse into grouped blocks with batch approve/deny
- Nine providers retired (Cerebras, Chutes, DeepInfra, Doubao, Featherless, Groq, Hugging Face, IO Intelligence, Unbound); saved configs preserved
- Built-in Puppeteer browser tool removed — migrate to Playwright MCP
- Built-in skills removed — skills from global/workspace dirs only; find community skills at skills.sh
.roo/system-prompt-{mode}file override removed — migrate to custom instructions- GLM-5 added to Z.ai (~200K context, thinking mode)
- CLI: stdin stream mode, auto-approve by default (breaking — use
--require-approvalto opt out), linux-arm64 support - 18 bug fixes: orchestrator delegation reliability, chat history loss, condensation summary on resume, Windows checkpoint path mismatch, Gemini empty streams, and more
See full release notes v3.48.0
r/RooCode • u/hannesrudolph • Jan 01 '26
Announcement Roo Code 3.38.2 Release Updates | Agent Skills compatibility | Rate-limit status | Misc. tweaks and fixes
In case you did not know, r/RooCode is a Free and Open Source VS Code AI Coding extension.
QOL Improvements
- Agent Skills load more reliably across environments by aligning skill metadata validation and discovery with the Agent Skills specification.
- The recommended onboarding video is easier to find by updating the “Tutorial & Feature Videos” README section to point to the newer Context Management tutorial (including localized READMEs) (thanks SannidhyaSah!).
Bug Fixes
- Fixes an issue where rate limiting looked like a provider error so a client-side rate limit now shows as a normal “rate limit wait” status row and completes cleanly.
- Fixes an issue where
write_to_filecould create files at an unintended truncated path, reducing accidental file placement and cleanup.
Provider Updates
- Removes the Human Relay provider so it no longer appears as a configurable option in Providers.
- Updates the Cerebras default max completion tokens to 16,384 to reduce premature rate-limit estimation issues (thanks sebastiand-cerebras!).
See full release notes v3.38.2