Customizing Modes

Roo Code allows you to create custom modes to tailor Roo's behavior to specific tasks or workflows. Custom modes can be either global (available across all projects) or project-specific (defined within a single project).

Sticky Models for Efficient Workflow

Each mode—including custom ones—features Sticky Models. This means Roo Code automatically remembers and selects the last model you used with a particular mode. This lets you assign different preferred models to different tasks without constant reconfiguration, as Roo switches between models when you change modes.

---

Why Use Custom Modes?

• Specialization: Create modes optimized for specific tasks, like "Documentation Writer," "Test Engineer," or "Refactoring Expert."
• Safety: Restrict a mode's access to sensitive files or commands. For example, a "Review Mode" could be limited to read-only operations.
• Experimentation: Safely experiment with different prompts and configurations without affecting other modes.
• Team Collaboration: Share custom modes with your team to standardize workflows.

Roo Code's interface for creating and managing custom modes.

---

What's Included in a Custom Mode?

Custom modes are defined by several key properties. Understanding these concepts will help you tailor Roo's behavior effectively.

UI Field / YAML Property	Conceptual Description
Slug (slug)	A unique internal identifier for the mode. It's used by Roo Code to reference the mode, especially for associating mode-specific instruction files.
Name (name)	The display name for the mode as it appears in the Roo Code user interface. This should be human-readable and descriptive.
Role Definition (roleDefinition)	Defines the core identity and expertise of the mode. This text is placed at the beginning of the system prompt. - Its primary function is to define Roo's personality and behavior when this mode is active. - The first sentence (up to the first period .) serves as a default concise summary for Roo to understand the mode's general purpose. - However, if the whenToUse property is defined, whenToUse takes precedence for summarizing the mode's function, especially in contexts like task orchestration or mode switching. In such cases, the first sentence of roleDefinition is less critical for this specific summarization task, though the entire roleDefinition is still used when the mode is active to guide its overall behavior.
Available Tools (groups)	Defines the allowed toolsets and file access permissions for the mode. - In the UI, this corresponds to selecting which general categories of tools (like reading files, editing files, browsing, or executing commands) the mode can use. - The UI shows which files can be edited in the 'Allowed files' section under each mode. - File type restrictions for the "edit" group are typically managed via manual YAML/JSON configuration or by asking Roo to set them up, as detailed in the Property Details for groups.
When to Use (optional) (whenToUse)	(Optional) Provides guidance for Roo to understand the mode's purpose, especially for automated decisions. - This text is used by Roo, particularly the 🪃 Orchestrator mode, for orchestrating tasks (e.g., via the new_task tool). - It also helps Roo decide which mode is appropriate when switching modes (e.g., via the switch_mode tool). - If populated, this description is used by Roo to understand the mode's function; otherwise, the first sentence of the roleDefinition is used by default.
Custom Instructions (optional) (customInstructions)	Specific behavioral guidelines or rules for the mode. - These instructions are added near the end of the system prompt to further refine Roo's behavior beyond the roleDefinition. - This can be provided directly in the configuration or via separate instruction files.

---

Methods for Creating and Configuring Custom Modes

You can create and configure custom modes in several ways:

1. Ask Roo! (Recommended)

You can quickly create a basic custom mode by asking Roo Code to do it for you. For example:

Create a new mode called "Documentation Writer". It should only be able to read files and write Markdown files.

Roo Code will guide you through the process, prompting for necessary information for the properties described in the What's Included in a Custom Mode? table. Roo will create the mode using the preferred YAML format. For fine-tuning or making specific adjustments later, you can use the Prompts tab or manual configuration.

2. Using the Prompts Tab

1. Open Prompts Tab: Click the icon in the Roo Code top menu bar.
2. Create New Mode: Click the button to the right of the Modes heading.
3. Fill in Fields:

The custom mode creation interface showing fields for name, slug, save location, role definition, available tools, custom instructions.

The interface provides fields for Name, Slug, Save Location, Role Definition, When to Use (optional), Available Tools, and Custom Instructions. After filling these, click the "Create Mode" button. Roo Code will save the new mode in YAML format.

Refer to the What's Included in a Custom Mode? table for conceptual explanations of each property. File type restrictions for the "edit" tool group can be added by asking Roo or through manual YAML/JSON configuration.

3. Manual Configuration (YAML & JSON)

You can directly edit the configuration files to create or modify custom modes. This method offers the most control over all properties. Roo Code now supports both YAML (preferred) and JSON formats.

• Global Modes: Edit the custom_modes.yaml (preferred) or custom_modes.json file. Access it via Prompts Tab > (Settings Menu icon next to "Global Prompts") > "Edit Global Modes".
• Project Modes: Edit the .roomodes file (which can be YAML or JSON) in your project root. Access it via Prompts Tab > (Settings Menu icon next to "Project Prompts") > "Edit Project Modes".

These files define an array/list of custom modes.

YAML Example (custom_modes.yaml or .roomodes):

customModes:
  - slug: docs-writer
    name: 📝 Documentation Writer
    roleDefinition: You are a technical writer specializing in clear documentation.
    whenToUse: Use this mode for writing and editing documentation.
    customInstructions: Focus on clarity and completeness in documentation.
    groups:
      - read
      - - edit # This group allows editing specific files
        - fileRegex: \.(md|mdx)$ # Regex for Markdown files
          description: Markdown files only
      - browser
  - slug: another-mode
    name: Another Mode
    # ... other properties

JSON Alternative (custom_modes.json or .roomodes):

{
  "customModes": [
    {
      "slug": "docs-writer",
      "name": "📝 Documentation Writer",
      "roleDefinition": "You are a technical writer specializing in clear documentation.",
      "whenToUse": "Use this mode for writing and editing documentation.",
      "customInstructions": "Focus on clarity and completeness in documentation.",
      "groups": [
        "read",
        ["edit", { "fileRegex": "\\.(md|mdx)$", "description": "Markdown files only" }],
        "browser"
      ]
    },
    {
      "slug": "another-mode",
      "name": "Another Mode"
    }
  ]
}

YAML/JSON Property Details

slug

• Purpose: A unique identifier for the mode.
• Format: Use lowercase letters, numbers, and hyphens.
• Usage: Used internally and in file/directory names for mode-specific rules (e.g., .roo/rules-{slug}/).
• Recommendation: Keep it short and descriptive.
• YAML Example: slug: docs-writer
• JSON Example: "slug": "docs-writer"

name

• Purpose: The display name shown in the Roo Code UI.
• Format: Can include spaces and proper capitalization.
• YAML Example: name: 📝 Documentation Writer
• JSON Example: "name": "Documentation Writer"

roleDefinition

• Purpose: Detailed description of the mode's role, expertise, and personality.
• Placement: This text is placed at the beginning of the system prompt when the mode is active.
• Important First Sentence: The first sentence (up to the first period .) serves as a default concise summary for Roo to understand the mode's general purpose. However, if the whenToUse property is defined, whenToUse takes precedence for summarizing the mode's function, especially in contexts like task orchestration or mode selection.
• YAML Example (multi-line):

  roleDefinition: >-
    You are a test engineer with expertise in:
    - Writing comprehensive test suites
    - Test-driven development

• JSON Example: "roleDefinition": "You are a technical writer specializing in clear documentation."

groups

• Purpose: Array/list defining which tool groups the mode can access and any file restrictions.
• Available Tool Groups (Strings): "read", "edit", "browser", "command", "mcp".
• File Restrictions for "edit" group:
  • To apply file restrictions, the "edit" entry becomes a list (YAML) or array (JSON) where the first element is "edit" and the second is a map/object defining the restrictions.
  • fileRegex: A regular expression string to control which files the mode can edit.
    • In YAML, typically use single backslashes for regex special characters (e.g., \.md$).
    • In JSON, backslashes must be double-escaped (e.g., \\.md$).
  • description: An optional string describing the restriction.
  • For more complex patterns, see Understanding Regex in Custom Modes.
• YAML Example:

  groups:
    - read
    - - edit # Start of "edit" tool with restrictions
      - fileRegex: \.(js|ts)$ # Restriction map for JS/TS files
        description: JS/TS files only
    - command

• JSON Example:

  "groups": [
    "read",
    ["edit", { "fileRegex": "\\.(js|ts)$", "description": "JS/TS files only" }],
    "command"
  ]

whenToUse

• Purpose: (Optional) Provides guidance for Roo to understand what this mode does. Used by the Orchestrator mode and for mode switching.
• Format: A string describing ideal scenarios or task types for this mode.
• Usage: If populated, Roo uses this description. Otherwise, the first sentence of roleDefinition is used.
• YAML Example: whenToUse: This mode is best for refactoring Python code.
• JSON Example: "whenToUse": "This mode is best for refactoring Python code."

customInstructions

• Purpose: A string containing additional behavioral guidelines for the mode.
• Placement: This text is added near the end of the system prompt.
• Supplementing: Can be supplemented by Mode-Specific Instructions via Files/Directories.
• YAML Example (multi-line):

  customInstructions: |-
    When writing tests:
    - Use describe/it blocks
    - Include meaningful descriptions

• JSON Example: "customInstructions": "Focus on explaining concepts and providing examples."

Benefits of YAML Format

YAML is now the preferred format for defining custom modes due to several advantages over JSON:

• Readability: YAML's indentation-based structure is often easier for humans to read and understand complex configurations.
• Comments: YAML allows for comments (lines starting with #), making it possible to annotate your mode definitions.

  customModes:
    - slug: security-review
      name: 🔒 Security Reviewer
      # This mode is restricted to read-only access
      roleDefinition: You are a security specialist reviewing code for vulnerabilities.
      whenToUse: Use for security reviews and vulnerability assessments.
      # Only allow reading files, no editing permissions
      groups:
        - read
        - browser

• Multi-line Strings: YAML provides cleaner syntax for multi-line strings (e.g., for roleDefinition or customInstructions) using | (literal block) or > (folded block).

  customModes:
    - slug: test-engineer
      name: 🧪 Test Engineer
      roleDefinition: >-
        You are a test engineer with expertise in:
        - Writing comprehensive test suites
        - Test-driven development
        - Integration testing
        - Performance testing
      customInstructions: |-
        When writing tests:
        - Use describe/it blocks
        - Include meaningful descriptions
        - Test edge cases
        - Ensure proper coverage
      # ... other properties

• Less Punctuation: YAML generally requires less punctuation (like commas and braces) compared to JSON, reducing syntax errors.
• Editor Support: Most modern code editors provide excellent syntax highlighting and validation for YAML files, further enhancing readability and reducing errors.

While JSON is still fully supported, new modes created via the UI or by asking Roo will default to YAML.

Tips for Working with YAML

When editing YAML manually, keep these points in mind:

• Indentation is Key: YAML uses indentation (spaces, not tabs) to define structure. Incorrect indentation is the most common source of errors. Ensure consistent spacing for nested elements.
• Colons for Key-Value Pairs: Keys must be followed by a colon and a space (e.g., slug: my-mode).
• Hyphens for List Items: List items start with a hyphen and a space (e.g., - read).
• Validate Your YAML: If you encounter issues, use an online YAML validator or your editor's built-in validation to check for syntax errors.

Migration to YAML Format

• Global Modes: The migration from custom_modes.json to custom_modes.yaml happens automatically for global modes when Roo Code starts up, under these conditions:

  1. Roo Code starts up.
  2. A custom_modes.json file exists.
  3. No custom_modes.yaml file exists yet. The migration process reads the existing JSON file, converts it to YAML format, creates a new custom_modes.yaml file, and preserves the original JSON file (e.g., by renaming it) for rollback purposes. If custom_modes.yaml already exists, it will be used, and no automatic migration of custom_modes.json will occur.

• Project Modes (.roomodes):

  • No automatic startup migration: Unlike global modes, project-specific .roomodes files are not automatically converted from JSON to YAML simply when Roo Code starts.
  • Format Detection: Roo Code can read .roomodes files in either YAML or JSON format. Roo Code automatically detects the format of .roomodes files by attempting to parse them as YAML first.
  • Conversion on UI Edit: If you edit a project-specific mode through the Roo Code UI (e.g., via the Prompts Tab), and the existing .roomodes file is in JSON format, Roo Code will save the changes in YAML format. This effectively converts the file to YAML. The original JSON content will be overwritten with YAML.
  • Manual Conversion: If you want to convert an existing .roomodes JSON file to YAML without making UI edits, you'll need to do this manually. You can:
    1. Open your existing JSON .roomodes file.
    2. Convert its content to YAML (you can ask Roo to help with this, or use an online converter).
    3. Replace the content of your .roomodes file with the new YAML content, or rename the old file (e.g., .roomodes.json.bak) and save the new content into a file named .roomodes. Ensure the resulting YAML is valid.

tip

For manual conversions of .roomodes files, you can use online JSON to YAML converters or ask Roo to help reformat a specific mode configuration from JSON to YAML. Always validate your YAML before saving.

---

Mode-Specific Instructions via Files/Directories

Mode-Specific Instruction File Locations

You can provide instructions for custom modes using dedicated files or directories within your workspace. This allows for better organization and version control compared to only using the customInstructions property.

Preferred Method: Directory (.roo/rules-{mode-slug}/)

.
├── .roo/
│   └── rules-docs-writer/  # Example for mode slug "docs-writer"
│       ├── 01-style-guide.md
│       └── 02-formatting.txt
└── ... (other project files)

Fallback Method: Single File (.roorules-{mode-slug})

.
├── .roorules-docs-writer  # Example for mode slug "docs-writer"
└── ... (other project files)

The directory method takes precedence if it exists and contains files.

In addition to the customInstructions property, you can provide mode-specific instructions via files in your workspace. This is particularly useful for:

• Organizing lengthy or complex instructions into multiple, manageable files.
• Managing instructions easily with version control.
• Allowing non-technical team members to modify instructions without editing YAML/JSON.

There are two ways Roo Code loads these instructions, with a clear preference for the newer directory-based method:

1. Preferred Method: Directory-Based Instructions (.roo/rules-{mode-slug}/)

• Structure: Create a directory named .roo/rules-{mode-slug}/ in your workspace root. Replace {mode-slug} with your mode's slug (e.g., .roo/rules-docs-writer/).
• Content: Place one or more files (e.g., .md, .txt) containing your instructions inside this directory. You can organize instructions further using subdirectories. Files within the .roo/rules-{mode-slug}/ directory are read recursively and appended in alphabetical order based on filename.
• Loading: All instruction files found within this directory structure will be loaded and applied to the specified mode.

2. Fallback (Backward Compatibility): File-Based Instructions (.roorules-{mode-slug})

• Structure: If the .roo/rules-{mode-slug}/ directory does not exist or is empty, Roo Code will look for a single file named .roorules-{mode-slug} in your workspace root (e.g., .roorules-docs-writer).
• Loading: If found, the content of this single file will be loaded as instructions for the mode.

Precedence:

• The directory-based method (.roo/rules-{mode-slug}/) takes precedence. If this directory exists and contains files, any corresponding root-level .roorules-{mode-slug} file will be ignored for that mode.
• This ensures that projects migrated to the new directory structure behave predictably, while older projects using the single-file method remain compatible.

Combining with customInstructions:

• Instructions loaded from either the directory or the fallback file are combined with the customInstructions property defined in the mode's configuration.
• Typically, the content from the files/directories is appended after the content from the customInstructions property.

---

Configuration Precedence

Mode configurations are applied in this order:

1. Project-level mode configurations (from .roomodes - YAML or JSON)
2. Global mode configurations (from custom_modes.yaml, then custom_modes.json if YAML not found)
3. Default mode configurations

This means that project-specific configurations will override global configurations, which in turn override default configurations. For instance, if you have a global 'code' mode and a project-specific 'code' mode in .roomodes, the project version will be used when working in that project. You can override any default mode by including a mode with the same slug in your global or project-specific configuration.

• Note on Instruction Files: Within the loading of mode-specific instructions from the filesystem, the directory .roo/rules-{mode-slug}/ takes precedence over the single file .roorules-{mode-slug} found in the workspace root.

---

Overriding Default Modes

You can override Roo Code's built-in modes (like 💻 Code, 🪲 Debug, ❓ Ask, 🏗️ Architect, 🪃 Orchestrator) with customized versions. This is done by creating a custom mode with the same slug as a default mode (e.g., code, debug).

Overriding Modes Globally

To customize a default mode across all your projects:

1. Open Prompts Tab: Click the icon.
2. Access Settings Menu: Click the icon next to "Global Prompts".
3. Edit Global Modes: Select "Edit Global Modes" to edit custom_modes.yaml (or custom_modes.json).
4. Add Your Override:

YAML Example:

customModes:
  - slug: code # Matches the default 'code' mode slug
    name: 💻 Code (Global Override) # Custom display name
    roleDefinition: You are a software engineer with global-specific constraints.
    whenToUse: This globally overridden code mode is for JS/TS tasks.
    customInstructions: Focus on project-specific JS/TS development.
    groups:
      - read
      - - edit
        - fileRegex: \.(js|ts)$
          description: JS/TS files only

JSON Alternative:

{
  "customModes": [{
    "slug": "code",
    "name": "💻 Code (Global Override)",
    "roleDefinition": "You are a software engineer with global-specific constraints",
    "whenToUse": "This globally overridden code mode is for JS/TS tasks.",
    "customInstructions": "Focus on project-specific JS/TS development",
    "groups": [
      "read",
      ["edit", { "fileRegex": "\\.(js|ts)$", "description": "JS/TS files only" }]
    ]
  }]
}

This example replaces the default 💻 Code mode with a version restricted to JavaScript and TypeScript files.

Project-Specific Mode Override

To override a default mode for just one project:

1. Open Prompts Tab: Click the icon.
2. Access Settings Menu: Click the icon next to "Project Prompts".
3. Edit Project Modes: Select "Edit Project Modes" to edit the .roomodes file (YAML or JSON).
4. Add Your Override:

YAML Example:

customModes:
  - slug: code # Matches the default 'code' mode slug
    name: 💻 Code (Project-Specific) # Custom display name
    roleDefinition: You are a software engineer with project-specific constraints for this project.
    whenToUse: This project-specific code mode is for Python tasks within this project.
    customInstructions: Adhere to PEP8 and use type hints.
    groups:
      - read
      - - edit
        - fileRegex: \.py$
          description: Python files only
      - command

JSON Alternative:

{
  "customModes": [{
    "slug": "code",
    "name": "💻 Code (Project-Specific)",
    "roleDefinition": "You are a software engineer with project-specific constraints for this project.",
    "whenToUse": "This project-specific code mode is for Python tasks within this project.",
    "customInstructions": "Adhere to PEP8 and use type hints.",
    "groups": [
      "read",
      ["edit", { "fileRegex": "\\.py$", "description": "Python files only" }],
      "command"
    ]
  }]
}

Project-specific overrides take precedence over global overrides.

Common Use Cases for Overriding Default Modes

• Restricting file access: Limit a mode to specific file types.
• Specializing behavior: Customize expertise for your tech stack.
• Adding custom instructions: Integrate project standards.
• Changing available tools: Remove tools to prevent unwanted operations.

tip

When overriding default modes, test carefully. Consider backing up configurations before major changes.

---

Understanding Regex in Custom Modes

Regular expressions (fileRegex) offer fine-grained control over file editing permissions.

tip

Let Roo Build Your Regex Patterns

Instead of writing complex regex manually, ask Roo:

Create a regex pattern that matches JavaScript files but excludes test files

Roo will generate the pattern. Remember to adapt it for YAML (usually single backslashes) or JSON (double backslashes).

When you specify fileRegex, you're creating a pattern that file paths must match.

Important Rules for fileRegex:

• Escaping in JSON: In JSON strings, backslashes (\) must be double-escaped (e.g., \\.md$).
• Escaping in YAML: In unquoted or single-quoted YAML strings, a single backslash is usually sufficient for regex special characters (e.g., \.md$).
• Path Matching: Patterns match against the full relative file path from your workspace root (e.g., src/components/button.js).
• Case Sensitivity: Regex patterns are case-sensitive by default.

Common Pattern Examples: In the table below, the 'Pattern (Conceptual / YAML-like)' column shows patterns as they would appear in YAML. For JSON, remember to double-escape backslashes.

Pattern (Conceptual / YAML-like)	JSON fileRegex Value	Matches	Doesn't Match
\.md$	"\\.md$"	readme.md, docs/guide.md	script.js, readme.md.bak
^src/.*	"^src/.*"	src/app.js, src/components/button.tsx	lib/utils.js, test/src/mock.js
`.(css	scss)$`	"\.(css	scss)$"
docs/.*\.md$	"docs/.*\\.md$"	docs/guide.md, docs/api/reference.md	guide.md, src/docs/notes.md
^(?!.*(test|spec))\.(js|ts)$	"^(?!.*(test|spec))\\.(js|ts)$"	app.js, utils.ts	app.test.js, utils.spec.js, app.jsx

Key Regex Building Blocks:

• \.: Matches a literal dot. (YAML: \., JSON: \\.)
• $: Matches the end of the string.
• ^: Matches the beginning of the string.
• .*: Matches any character (except newline) zero or more times.
• (a|b): Matches either "a" or "b". (e.g., \.(js|ts)$)
• (?!...): Negative lookahead.

Testing Your Patterns:

1. Test on sample file paths. Online regex testers are helpful.
2. Remember the escaping rules for JSON vs. YAML.
3. Start simple and build complexity.

Error Handling

When a mode attempts to edit a file that doesn't match its fileRegex pattern, you'll see a FileRestrictionError with details about which patterns are allowed.

---

Community Gallery

Ready to explore more? Check out the Custom Modes Gallery section on the main community page to discover and share custom modes created by the community!