Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
72 commits
Select commit Hold shift + click to select a range
c4c4780
fix: preserve original first message context during conversation cond…
daniel-lxs Sep 12, 2025
72bc790
Add a little padding to the cloudview (#7954)
mrubens Sep 13, 2025
80d82e6
fix: make nested git repository warning persistent with path info (#7…
roomote[bot] Sep 14, 2025
b576dd9
fix: include API key in Ollama /api/tags requests (#7903)
roomote[bot] Sep 14, 2025
d09689b
feat: add Qwen3 Next 80B A3B models to chutes provider (#7948)
daniel-lxs Sep 14, 2025
9ea7173
ux: Smaller and more subtle auto-approve UI (#7894)
brunobergher Sep 14, 2025
b309a6a
Disable Roomote Control on logout (#7976)
cte Sep 14, 2025
c79cb29
Remove chevrons from chat buttons (#7970)
mrubens Sep 14, 2025
3be0a96
chore: add changeset for v3.28.2 (#7979)
mrubens Sep 14, 2025
d54ff8a
Changeset version bump (#7980)
github-actions[bot] Sep 14, 2025
9d33c10
ux: Makes text area buttons appear only when there's text (#7987)
brunobergher Sep 15, 2025
1b4819c
fix: corrected C# tree-sitter query (#7813)
mubeen-zulfiqar Sep 15, 2025
94b4511
feat: Move slash commands to Settings tab with gear icon for discover…
roomote[bot] Sep 15, 2025
3fe2918
Add Z.ai coding plan support (#8003)
daniel-lxs Sep 15, 2025
68c5be8
chore(deps): bump axios from 1.9.0 to 1.12.0 (#7963)
dependabot[bot] Sep 15, 2025
358519d
Fix context menu is obscured when edit message. (#7951)
NaccOll Sep 16, 2025
beb0a59
feat: add keyboard shortcut for "Add to Context" action (#7908)
roomote[bot] Sep 16, 2025
759454b
fix: handle ByteString conversion errors in OpenAI embedders (#8008)
daniel-lxs Sep 16, 2025
ee58c5d
CONTRIBUTING.md tweaks and issue template rewrite (#8014)
hannesrudolph Sep 16, 2025
c987417
feat: Reposition Add Image button inside ChatTextArea (#7989)
roomote[bot] Sep 16, 2025
3d45d4a
feat: Bring back a way to temporarily and globally pause auto-approve…
brunobergher Sep 16, 2025
6fe9071
fix: filter out Claude Code built-in tools (ExitPlanMode, BashOutput,…
roomote[bot] Sep 16, 2025
cde738a
fix: handle square bracket HTML entities in Gemini responses (#7577)
roomote[bot] Sep 16, 2025
fc9c395
feat: Replace + icon with edit icon for New Task button (#7942)
roomote[bot] Sep 16, 2025
3c2fd1d
Release v3.28.3 (#8025)
mrubens Sep 16, 2025
4fe051f
Changeset version bump (#8026)
github-actions[bot] Sep 16, 2025
297c85f
feat: remove web-docs app (#8027)
roomote[bot] Sep 16, 2025
6d8de53
fix: skip flaky Windows test in custom-system-prompt.spec.ts (#8023)
roomote[bot] Sep 16, 2025
2819120
feat: add GDPR-compliant cookie consent banner (#8022)
roomote[bot] Sep 16, 2025
dd20af2
Release: v1.76.0 (#8030)
mrubens Sep 16, 2025
2263d86
Types 1.77.0 (#8031)
mrubens Sep 16, 2025
dcc6db0
feat(web): update homepage headline and tagline for remote control ca…
jdilla1277 Sep 17, 2025
6ac6a92
ux: Responsive Auto-Approve (#8032)
brunobergher Sep 17, 2025
7b1e3a0
feat(cloud): Add telemetry retry queue for network resilience (#7597)
daniel-lxs Sep 17, 2025
c837025
Docs: Overhaul README (#8005)
hannesrudolph Sep 17, 2025
961338e
Add organizationFeaturesSchema with roomoteControlEnabled (#8085)
roomote[bot] Sep 17, 2025
b1c104e
Release: v1.78.0 (#8089)
jr Sep 17, 2025
a255c95
Get the model id property for a given provider (#8009)
cte Sep 17, 2025
87b45de
Fix: Transform keybindings in nightly build to fix command+y shortcut…
roomote[bot] Sep 17, 2025
d1fca3b
add context item ctrl/cmd+click to open
j-east Sep 18, 2025
7a05a23
fix Memory leak risk in ChatTextArea.tsx
j-east Sep 18, 2025
1c778df
remove ctrl/cmd+enter key functionality as it isn't working consistently
j-east Sep 18, 2025
765e3a0
Add a list of sub-processors (#8163)
mrubens Sep 18, 2025
513fce3
Add cookie policy (#8165)
mrubens Sep 18, 2025
f934363
ux: Redesigned Message Feed (#7985)
brunobergher Sep 19, 2025
07684c0
bug: Incorrect copy for "Run" command when approving execution (#8179)
brunobergher Sep 19, 2025
ac4eda9
Supernova (#8175)
mrubens Sep 19, 2025
8214672
chore: add changeset for v3.28.4 (#8182)
mrubens Sep 19, 2025
b75ef1d
Changeset version bump (#8183)
github-actions[bot] Sep 19, 2025
f7a6589
fix: support dash prefix in parseMarkdownChecklist for todo lists (#8…
roomote[bot] Sep 20, 2025
c1e0cdc
Updating the privacy policy to allow us to send occasional emails (#8…
jdilla1277 Sep 20, 2025
c0e2c5e
fix: apply tiered pricing for Gemini models via Vertex AI (#8018)
roomote[bot] Sep 20, 2025
d6cb396
update sambanova models (#8186)
snova-jorgep Sep 20, 2025
d956cdb
Fix duplicate rehydrate during reasoning; centralize rehydrate and pr…
hannesrudolph Sep 20, 2025
1533efc
Wrap code blocks by default (#8194)
mrubens Sep 20, 2025
32d7e6f
Add an announcement for Supernova (#8197)
mrubens Sep 20, 2025
95e4235
Release v3.28.5 (#8198)
mrubens Sep 20, 2025
ceb9d2b
Changeset version bump (#8199)
github-actions[bot] Sep 20, 2025
6a4dab0
Remove language selection and word wrap toggle from CodeBlock (#8208)
mrubens Sep 22, 2025
6c2aa63
feat: Add keyboard shortcut for toggling auto-approve (Cmd/Ctrl+Alt+A…
brunobergher Sep 22, 2025
0e1b23d
Bare metal evals fixes (#8224)
cte Sep 22, 2025
9dabb85
Fix: Improve reasoning block formatting for better readability (#7868)
daniel-lxs Sep 23, 2025
60ba541
fix: prevent checkpoint text from wrapping in non-English languages (…
roomote[bot] Sep 23, 2025
12f94fc
fix: respect Ollama Modelfile num_ctx configuration (#7798)
roomote[bot] Sep 23, 2025
807cc99
feat: add package.nls.json checking to find-missing-translations scri…
roomote[bot] Sep 23, 2025
1a4fb7f
feat(types): add GPT-5-Codex model (#8260)
daniel-lxs Sep 23, 2025
8e9a266
chore: add changeset for v3.28.6 (#8261)
mrubens Sep 23, 2025
19c3606
Follow-up questions should trigger the "interactive" state (#8259)
cte Sep 23, 2025
6061672
chore: add changeset for v3.28.6 (#8263)
mrubens Sep 23, 2025
44cbee5
Changeset version bump (#8262)
github-actions[bot] Sep 23, 2025
8cc4bf0
Merge branch 'main' of https://github.com/RooCodeInc/Roo-Code into fe…
j-east Sep 23, 2025
bafbddf
fix failing platform-unit-test
j-east Sep 23, 2025
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
106 changes: 63 additions & 43 deletions .github/ISSUE_TEMPLATE/bug_report.yml
Original file line number Diff line number Diff line change
@@ -1,12 +1,66 @@
name: Bug Report
description: Clearly report a bug with detailed repro steps
description: Report a broken behavior in plain language with a minimal reproduction
labels: ["bug"]
title: "[BUG] "
body:
- type: markdown
attributes:
value: |
**Thanks for your report!** Please check existing issues first:
👉 https://github.com/RooCodeInc/Roo-Code/issues
Thank you for your report! Please search existing issues first:
https://github.com/RooCodeInc/Roo-Code/issues

- type: textarea
id: problem
attributes:
label: Problem (one or two sentences)
description: Describe what went wrong in plain language.
placeholder: 'Example: "Expected the task to start, but nothing happened and no message appeared."'
validations:
required: true

- type: textarea
id: context
attributes:
label: Context (who is affected and when)
description: Who sees this and in what situation? Keep it non-technical.
placeholder: 'Example: "Happens to new users when starting a run from the New Run page with dark theme enabled."'
validations:
required: true

- type: textarea
id: steps
attributes:
label: Reproduction steps
description: Provide clear, numbered steps so we can reproduce.
placeholder: |
1) Environment/setup (OS, extension version, relevant settings)
2) Exact actions (clicks, inputs, commands)
3) What you observed after each step
validations:
required: true

- type: input
id: expected
attributes:
label: Expected result
placeholder: e.g., "The task starts and shows progress."
validations:
required: true

- type: input
id: actual
attributes:
label: Actual result
placeholder: e.g., "The button appears disabled and no progress is shown."
validations:
required: true

- type: textarea
id: variations
attributes:
label: Variations tried (optional)
description: Different browsers, devices, providers, or settings you tried.
placeholder: e.g., "Tried Chrome/Firefox, disabling dark theme, switching providers."

- type: input
id: version
Expand All @@ -19,7 +73,7 @@ body:
- type: dropdown
id: provider
attributes:
label: API Provider
label: API Provider (optional)
options:
- Anthropic
- AWS Bedrock
Expand All @@ -45,57 +99,23 @@ body:
- VS Code Language Model API
- xAI (Grok)
- Not Applicable / Other
validations:
required: true

- type: input
id: model
attributes:
label: Model Used
label: Model Used (optional)
description: Exact model name (e.g., Claude 3.7 Sonnet). Use N/A if irrelevant.
validations:
required: true

- type: textarea
id: roo-code-tasks
attributes:
label: Roo Code Task Links (Optional)
description: |
If you have any publicly shared task links that demonstrate the issue, please paste them here.
This helps maintainers understand the context.
Example: https://app.roocode.com/share/task-id
label: Roo Code Task Links (optional)
description: If you have any publicly shared Roo Code task links that demonstrate the issue, paste them here.
placeholder: Paste your Roo Code share links here, one per line

- type: textarea
id: steps
attributes:
label: 🔁 Steps to Reproduce
description: |
Help us see what you saw. Give clear, numbered steps:

1. Setup (OS, extension version, settings)
2. Exact actions (clicks, input, files, commands)
3. What happened after each step

Think like you're writing a recipe. Without this, we can't reproduce the issue.
validations:
required: true

- type: textarea
id: what-happened
attributes:
label: 💥 Outcome Summary
description: |
Recap what went wrong in one or two lines.

Example: "Expected code to run, but got an empty response and no error."
placeholder: Expected ___, but got ___.
validations:
required: true

- type: textarea
id: logs
attributes:
label: 📄 Relevant Logs or Errors (Optional)
description: Paste API logs, terminal output, or errors here. Use triple backticks (```) for code formatting.
label: Relevant logs or errors (optional)
description: Paste relevant output or errors. Use triple backticks (```) for formatting.
render: shell
202 changes: 46 additions & 156 deletions .github/ISSUE_TEMPLATE/feature_request.yml
Original file line number Diff line number Diff line change
@@ -1,71 +1,47 @@
name: Detailed Feature Proposal
description: Report a specific problem that needs solving in Roo Code
labels: ["proposal", "enhancement"]
name: Enhancement Request
description: Propose an improvement in plain language focused on user benefit
labels: ["enhancement"]
title: "[ENHANCEMENT] "
body:
- type: markdown
attributes:
value: |
**Thank you for submitting a feature request for Roo Code!**

This template helps you describe problems that need solving. Focus on the problem - the Roo team will work to design solutions unless you want to contribute the implementation yourself.

**Quality over speed:** We prefer detailed, clear problem descriptions over quick ones. Vague requests often get closed or require multiple rounds of clarification, which wastes everyone's time.

**Before submitting:**
- Search existing [Issues](https://github.com/RooCodeInc/Roo-Code/issues) and [Discussions](https://github.com/RooCodeInc/Roo-Code/discussions) to avoid duplicates
- For general ideas, use [GitHub Discussions](https://github.com/RooCodeInc/Roo-Code/discussions/categories/feature-requests) instead of this template.
Thank you for helping improve Roo Code!
Please focus on the problem and the desired behavior in plain language.

- type: markdown
- type: textarea
id: problem
attributes:
value: |
## ❌ Common mistakes that lead to request rejection:
- **Vague problem descriptions:** "UI is bad" -> Should be: "Submit button is invisible on dark theme"
- **Missing user impact:** "This would be cool" -> Should explain who benefits and how
- **No specific context:** Describe exactly when and how the problem occurs

label: Problem (one or two sentences)
description: What problem are users facing?
placeholder: e.g., "Users often click Copy Run by mistake and duplicate runs unintentionally."
validations:
required: true

- type: textarea
id: problem-description
id: context
attributes:
label: What specific problem does this solve?
description: |
**Be concrete and detailed.** Explain the problem from a user's perspective.

✅ **Good examples (specific, clear impact):**
- "When running large tasks, users wait 5+ minutes because tasks execute sequentially instead of in parallel, blocking productivity"
- "AI can only read one file per request, forcing users to make multiple requests for multi-file projects, increasing wait time from 30s to 5+ minutes"
- "Dark theme users can't see the submit button because it uses white text on light grey background"

❌ **Poor examples (vague, unclear impact):**
- "The UI looks weird" -> What specifically looks weird? On which screen? What's the impact?
- "System prompt is not good" -> What's wrong with it? What behaviour does it cause? What should it do instead?
- "Performance could be better" -> Where? How slow is it currently? What's the user impact?

**Your problem description should answer:**
- Who is affected? (all users, specific user types, etc.)
- When does this happen? (specific scenarios/steps)
- What's the current behaviour vs expected behaviour?
- What's the impact? (time wasted, errors caused, etc.)
placeholder: Be specific about the problem, who it affects, and the impact. Avoid generic statements like "it's slow" or "it's confusing."
label: Context (who is affected and when)
description: Who encounters this and in what situation?
placeholder: e.g., "Happens when browsing the Runs list; most visible for new users."
validations:
required: true


- type: textarea
id: additional-context
id: desired
attributes:
label: Additional context (optional)
description: Mockups, screenshots, links, user quotes, or other relevant information that supports your proposal.
label: Desired behavior (conceptual, not technical)
description: Describe what should happen in simple terms.
placeholder: e.g., "Ask for confirmation before copying a run."
validations:
required: true

- type: textarea
id: roo-code-tasks
id: constraints
attributes:
label: Roo Code Task Links (Optional)
description: |
If you used Roo Code to explore this feature request or develop solutions, share the public task links here.
This helps maintainers understand the context and any exploration you've done.
Example: https://app.roocode.com/share/task-id
placeholder: Paste your Roo Code share links here, one per line
label: Constraints / preferences (optional)
description: Any considerations like performance, accessibility, or UX expectations.
placeholder: e.g., "Keep it quick and unobtrusive; keyboard accessible."

- type: checkboxes
id: checklist
Expand All @@ -74,128 +50,42 @@ body:
options:
- label: I've searched existing Issues and Discussions for duplicates
required: true
- label: This describes a specific problem with clear impact and context
- label: This describes a specific problem with clear context and impact
required: true

- type: textarea
id: roo-code-tasks
attributes:
label: Roo Code Task Links (optional)
description: If you explored this with Roo Code, share public task links for context.
placeholder: Paste your Roo Code share links here, one per line

- type: markdown
attributes:
value: |
---

## 🛠️ **Optional: Contributing & Technical Analysis**

**🎯 Just reporting a problem?** You can click "Submit new issue" right now! The sections below are only needed if you want to contribute a solution via pull request.

**⚠️ Only continue if you want to:**
- Propose a specific solution design
- Implement the feature yourself via pull request
- Provide technical analysis to help with implementation

**For contributors who continue:**
- A maintainer (especially @hannesrudolph) will review this proposal. **Do not start implementation until approved and assigned.** We're a small team with limited resources, so every code addition needs careful consideration. We're always happy to receive clear, actionable proposals though!
- Join [Discord](https://discord.gg/roocode) and DM **Hannes Rudolph** (`hrudolph`) for guidance on implementation
- Check our [Roadmap](https://github.com/orgs/RooCodeInc/projects/1/views/1?query=sort%3Aupdated-desc+is%3Aopen&filterQuery=is%3Aissue%2Copen%2Cclosed+label%3A%22feature+request%22+status%3A%22Issue+%5BUnassigned%5D%22%2C%22Issue+%5BIn+Progress%5D%22) to see open feature requests ready to be implemented or currently being worked on

- type: checkboxes
id: willingness-to-contribute
attributes:
label: Interested in implementing this?
description: |
**Important:** If you check "Yes" below, the technical sections become REQUIRED.
We need detailed technical analysis from contributors to ensure quality implementation.
options:
- label: Yes, I'd like to help implement this feature
required: false

- type: checkboxes
id: implementation-approval
attributes:
label: Implementation requirements
options:
- label: I understand this needs approval before implementation begins
required: false

- type: textarea
id: proposed-solution
attributes:
label: How should this be solved? (REQUIRED if contributing, optional otherwise)
description: |
**If you want to implement this feature, this section is REQUIRED.**

**Describe your solution in detail.** Explain not just what to build, but how it should work.

✅ **Good examples:**
- "Add parallel task execution: Allow up to 3 tasks to run simultaneously with a queue system for additional tasks. Show progress for each active task in the UI."
- "Enable multi-file AI processing: Modify the request handler to accept multiple files in a single request and process them together, reducing round trips."
- "Fix button contrast: Change submit button to use primary colour on dark theme (white text on blue background) instead of current grey."

❌ **Poor examples:**
- "Make it faster" -> How? What specific changes?
- "Improve the UI" -> Which part? What specific improvements?
- "Fix the prompt" -> What should the new prompt do differently?

**Your solution should explain:**
- What exactly will change?
- How will users interact with it?
- What will the new behaviour look like?
placeholder: Describe the specific changes and how they will work. Include user interaction details if relevant.
Optional (for contributors): You can stop here if you're just proposing the improvement.

- type: textarea
id: acceptance-criteria
attributes:
label: How will we know it works? (Acceptance Criteria - REQUIRED if contributing, optional otherwise)
description: |
**If you want to implement this feature, this section is REQUIRED.**

**This is crucial - don't skip it.** Define what "working" looks like with specific, testable criteria.

**Format suggestion:**
```
Given [context/situation]
label: Acceptance criteria (optional)
description: Define what “working” looks like with specific, testable outcomes.
placeholder: |
Given [context]
When [user action]
Then [expected result]
And [additional expectations]
But [what should NOT happen]
```

**Example:**
```
Given I have 5 large tasks to run
When I start all of them
Then they execute in parallel (max 3 at once, can be configured)
And I see progress for each active task
And queued tasks show "waiting" status
But the UI doesn't freeze or become unresponsive
```
placeholder: |
Define specific, testable criteria. What should users be able to do? What should happen? What should NOT happen?
Use the Given/When/Then format above or your own clear structure.

- type: textarea
id: technical-considerations
id: proposed-solution
attributes:
label: Technical considerations (REQUIRED if contributing, optional otherwise)
description: |
**If you want to implement this feature, this section is REQUIRED.**

Share technical insights that could help planning:
- Implementation approach or architecture changes
- Performance implications
- Compatibility concerns
- Systems that might be affected
- Potential blockers you can foresee
placeholder: e.g., "Will need to refactor task manager", "Could impact memory usage on large files", "Requires a large portion of code to be rewritten"
label: Proposed approach (optional)
description: If you have an idea, describe it briefly in plain language.

- type: textarea
id: trade-offs-and-risks
id: risks
attributes:
label: Trade-offs and risks (REQUIRED if contributing, optional otherwise)
description: |
**If you want to implement this feature, this section is REQUIRED.**

What could go wrong or what alternatives did you consider?
- Alternative approaches and why you chose this one
- Potential negative impacts (performance, UX, etc.)
- Breaking changes or migration concerns
- Edge cases that need careful handling
placeholder: 'e.g., "Alternative: use library X but it is 500KB larger", "Risk: might slow older devices", "Breaking: changes API response format"'
label: Trade-offs / risks (optional)
description: Potential downsides or alternatives considered.
Loading