Roo Code ignores mode permissions if concurrent file edits are enabled

[dsent]

App Version

3.20.3

API Provider

VS Code Language Model API

Model Used

Claude 4

🔁 Steps to Reproduce

I've worked on something with Architect, and at some point, it just started editing PowerShell scripts despite not having permission to do so.

💥 Outcome Summary

I have a modified version of Architect on the project level, but its edition scope is limited:

    groups:
      - read
      - - edit
        - fileRegex: \.(md|yaml|json|toml|.+ignore|roomodes)$
          description: Documentation and configs
      - browser
      - command
      - mcp

The relevant task screenshot:

📄 Relevant Logs or Errors (Optional)

[dosubot]

It looks like auto-approve settings in Roo Code can bypass mode permissions and allow file edits without confirmation, even for file types that should be restricted. If "Edit files" is enabled in the auto-approve toolbar, Roo can modify any file—including PowerShell scripts—without asking, regardless of your mode or YAML restrictions. The master toggle in the auto-approve toolbar can also override all permissions at once, so it's worth double-checking that it's off when you want strict enforcement of mode limits. For more details, see the auto-approve documentation.

Architect Mode itself should only allow editing markdown files, and attempts to edit other types should trigger a FileRestrictionError, unless something in your custom mode or auto-approve settings is overriding this behavior. If you want to enforce file restrictions more strictly, make sure auto-approve for editing is disabled and review your custom mode config for any overrides.

I couldn't find any existing tickets or discussions about this specific issue in the docs. If you have more details about your custom Architect config or logs, that might help narrow down the cause.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}   

[dsent]

I was able to reproduce the issue immediately. See the attached task export.
roo_task_jun-16-2025_2-24-54-am.md

Here's from my project's .roomodes:

  - slug: architect
    name: 🏗️ Architect
    roleDefinition: You are Roo, an experienced technical leader who is inquisitive
      and an excellent planner. Your goal is to gather information and get
      context to create a detailed plan for accomplishing the user's task, which
      the user will review and approve. Update the documentation yourself, but
      don't make code changes.
    customInstructions: >-
      1. Do some information gathering (for example using read_file or
      search_files) to get more context about the task.

      2. You should also ask the user clarifying questions to get a better
      understanding of the task.

      3. Once you've gained more context about the user's request, you should
      create a detailed plan for how to accomplish the task. Include Mermaid
      diagrams if they help make your plan clearer.

      4. Ask the user if they are pleased with this plan, or if they would like
      to make any changes. Think of this as a brainstorming session where you
      can discuss the task and plan the best way to accomplish it.

      5. Once the user confirms the plan, update the relevant project
      documentation. For complex changes, also consider writing the plan itself
      to a temporary file in Markdown format.

      6. If the change requires modifying code, use the switch_mode tool to
      request switching to the most appropriate mode for implementation.

      IMPORTANT: Respect the Repository Schema in all your operations!
    groups:
      - read
      - - edit
        - fileRegex: \.(md|yaml|json|toml|.+ignore|roomodes)$
          description: Documentation and configs
      - browser
      - command
      - mcp
    source: project