Merge branch 'main' into use_sbc_doc

Author: shaybc

.gitignore

@@ -20,3 +20,5 @@
 npm-debug.log*
 yarn-debug.log*
 yarn-error.log*
+
+.devcontainer

docs/advanced-usage/auto-approving-actions.md

@@ -27,7 +27,7 @@ At the top of the Auto-Approve Toolbar is a toggle to enable/disable auto-approv
 
 ## Advanced Configuration (Settings)
 
-You can also find these auto-approval options in the Roo Code settings panel (gear icon ⚙️ in the top right corner).  The settings panel provides the same functionality as the auto-approve menu, but in a different location.  The auto-approve menu is generally the quickest way to change these settings.
+You can also find these auto-approval options in the Roo Code settings panel (<Codicon name="gear" /> in the top right corner).  The settings panel provides the same functionality as the auto-approve menu, but in a different location.  The auto-approve menu is generally the quickest way to change these settings.
 
 ## Security Considerations
 

docs/advanced-usage/code-actions.md

@@ -61,7 +61,7 @@ Each code action gives you two options:
 
 You can customize the prompts used for each Code Action by modifying the "Support Prompts" in the **Prompts** tab.  This allows you to fine-tune the instructions given to the AI model and tailor the responses to your specific needs.
 
-1.  **Open the Prompts Tab:** Click the notebook icon in the Roo Code top menu bar.
+1.  **Open the Prompts Tab:** Click the <Codicon name="notebook" /> icon in the Roo Code top menu bar.
 2. **Find "Support Prompts":** You will see the support prompts, including "Enhance Prompt", "Explain Code", "Fix Code", and "Improve Code".
 3. **Edit the Prompts:**  Modify the text in the text area for the prompt you want to customize. You can use placeholders like `${filePath}` and `${selectedText}` to include information about the current file and selection.
 4. **Click "Done":** Save your changes.

docs/advanced-usage/custom-instructions.md

@@ -12,7 +12,7 @@ These instructions are added to every prompt, regardless of the active mode.  Th
 
 **How to set them:**
 
-1.  Open the Roo Code panel (rocket icon 🚀).
+1.  Open the Roo Code panel (<Codicon name="rocket" />).
 2.  Click the "Prompts" button in the top menu bar.
 3.  Find the "Custom Instructions for All Modes" section.
 4.  Enter your instructions in the text area.
@@ -24,7 +24,7 @@ These instructions are added only when a specific mode is active.  They allow yo
 
 **How to set them:**
 
-1.  Open the Roo Code panel (rocket icon 🚀).
+1.  Open the Roo Code panel (<Codicon name="rocket" />).
 2.  Click the "Prompts" button in the top menu bar.
 3.  Select the mode you want to customize from the dropdown.
 4.  Find the "Mode-specific Custom Instructions" section.

docs/advanced-usage/custom-modes.md

@@ -1,6 +1,6 @@
 # Custom Modes
 
-Roo Code allows you to create **custom modes** that can be either global (available across all projects) or project-specific (defined within a single project). These modes let you tailor Roo's behavior to specific tasks or workflows by defining:
+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).  They allow you to define:
 
 *   **A unique name and slug:** For easy identification.
 *   **A role definition:** A description of the mode's purpose and expertise.
@@ -15,7 +15,7 @@ Roo Code allows you to create **custom modes** that can be either global (availa
 *   **Experimentation:** Safely experiment with different prompts and configurations without affecting other modes.
 *   **Team Collaboration:** Share custom modes with your team to standardize workflows.
 
-## Creating a Custom Mode
+## Creating Custom Modes
 
 You have three options for creating custom modes:
 
@@ -33,36 +33,54 @@ Roo Code will guide you through the process.
 
 ### 2. Using the Prompts Tab
 
-1.  **Open the Prompts Tab:** Click the notebook icon in the Roo Code top menu bar.
-2.  **Click "Create New Mode":**  Use the "+" button to add a new mode.
+1.  **Open the Prompts Tab:** Click the <Codicon name="notebook" /> icon in the Roo Code top menu bar.
+2.  **Click "Create New Mode":**  Use the <Codicon name="add" /> button to add a new mode.
 3.  **Fill in the Fields:**  Enter the mode's name, role definition, custom instructions, and select the allowed tool groups.
 4.  **Click "Create Mode":**  Save your new mode.
 
 Note: Adding/editing file type restrictions is not yet supported in the prompts tab UI.
 
-### 3. Manual Configuration (Advanced)
+### 3. Manual Configuration
 
-Custom modes can be configured in two locations:
+Custom modes can be configured by directly editing JSON files. There are two locations for custom mode configurations:
 
-1. **Global Configuration:**
-   - Located at `~/Library/Application Support/Cursor/User/globalStorage/rooveterinaryinc.roo-cline/settings/cline_custom_modes.json`
-   - These modes are available across all projects
+1.  **Global Configuration:**
+    *   Located at `[path to global extension storage]/rooveterinaryinc.roo-cline/settings/cline_custom_modes.json`
+    *   These modes are available across all projects.
 
-2. **Project-Specific Configuration:**
-   - Located in `.roomodes` file in your project's root directory
-   - These modes are only available within that specific project
-   - Project-specific modes take precedence over global modes with the same slug
+2.  **Project-Specific Configuration:**
+    *   Located in a `.roomodes` file in your project's root directory.
+    *   These modes are only available within that specific project.
+    *   **Project-specific modes take precedence over global modes with the same slug.**  This means if you define a mode with the slug "code" in your `.roomodes` file, it will override the global "code" mode when you're working in that project.
 
 To edit either configuration:
 
-1.  **Open the Prompts Tab:** Click the notebook icon in the Roo Code top menu bar.
-2.  **Open the Settings File:** Click the code icon (`<>`) in the top right corner of the "Prompts" tab.
+1.  **Open the Prompts Tab:** Click the <Codicon name="notebook" /> icon in the Roo Code top menu bar.
+2.  **Open the Settings File:** Click the <Codicon name="code" /> icon in the top right corner of the "Prompts" tab.  (This will allow you to edit either the Global or project-specific configuration file. You can also edit the project-specific configuration by manually creating/opening the `.roomodes` file in your project's root directory.)
 3.  **Edit the JSON:** Add or modify mode configurations within the `customModes` array, following the format described below.
 4.  **Save the File:** Roo Code will automatically detect the changes.
 
 ## Custom Mode Configuration (JSON Format)
 
-Both global and project-specific configuration files use the same JSON format. Here's an example:
+Both global and project-specific configuration files use the same JSON format.  The configuration is a JSON object with a `customModes` key, which contains an array of mode definitions. Each mode definition is a JSON object with the following properties:
+
+*   `slug`: (Required) A unique identifier for the mode (lowercase letters, numbers, and hyphens).  Shorter is better.
+*   `name`: (Required) The display name for the mode.
+*   `roleDefinition`: (Required) A detailed description of the mode's role and capabilities.
+*   `groups`: (Required) An array of allowed tool groups. Each group can be specified either as a string (e.g., `"edit"` to allow editing any file) or with file restrictions (e.g., `["edit", { "fileRegex": "\\.md$", "description": "Markdown files only" }]` to only allow editing markdown files).
+    *   Available tool groups are: `"read"`, `"edit"`, `"browser"`, `"command"`, `"mcp"`.
+    *   **Understanding `fileRegex`:** The `fileRegex` property uses a *regular expression* (or *regex*) to define which files the mode is allowed to edit. A regular expression is a sequence of characters that specifies a search pattern. Here's a breakdown of some common regex components used in the examples:
+        *   `\.`: Matches a literal dot (`.`).  The backslash is used to "escape" the dot, since a dot has a special meaning in regular expressions (matching any character).
+        *   `(test|spec)`: Matches either "test" or "spec". The parentheses create a *capturing group*, and the pipe (`|`) acts as an "or".
+        *   `(js|ts|jsx|tsx)`: Matches "js", "ts", "jsx", or "tsx".
+        *   `$`: Matches the end of the string. This ensures that the entire filename matches the pattern, not just a part of it.
+        *   For example, `\\.md$` matches any filename that ends with ".md".  `\\.(test|spec)\\.(js|ts|jsx|tsx)$` matches filenames like "myComponent.test.js", "utils.spec.ts", etc.
+        *   You can learn more about regular expressions on websites like [MDN Web Docs](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_Expressions).
+*   `customInstructions`: (Optional) Additional instructions for the mode.
+
+Here are some examples:
+
+**Example 1: A simple documentation writer mode (could be global or project-specific):**
 
 ```json
 {
@@ -76,7 +94,16 @@ Both global and project-specific configuration files use the same JSON format. H
         "read",
         ["edit", { "fileRegex": "\\.md$", "description": "Markdown files only" }]
       ]
-    },
+    }
+  ]
+}
+```
+
+**Example 2: A test engineer mode (could be global or project-specific):**
+
+```json
+{
+  "customModes": [
     {
       "slug": "test-engineer",
       "name": "Test Engineer",
@@ -90,6 +117,65 @@ Both global and project-specific configuration files use the same JSON format. H
 }
 ```
 
+**Example 3:  Adding a new mode in a `.roomodes` file (project-specific):**
+
+```json
+{
+  "customModes": [
+    {
+      "slug": "data-scientist",
+      "name": "Data Scientist",
+      "roleDefinition": "You are Roo, a data scientist with expertise in data analysis, machine learning, and statistical modeling.",
+      "groups": [
+        "read",
+        "edit",
+        "command"
+      ],
+      "customInstructions": "Focus on data analysis and machine learning tasks."
+    }
+  ]
+}
+```
+
+**Example 4: Overriding an existing mode in a `.roomodes` file (project-specific):**
+
+```json
+{
+  "customModes": [
+    {
+      "slug": "code"
+      "name": "Code (Project-Specific)",
+      "roleDefinition": "You are Roo, a highly skilled software engineer.  In this project, you have limited file access.",
+      "groups": [
+        "read",
+        ["edit", { "fileRegex": "\\.(js|ts)$", "description": "JavaScript and TypeScript files only" }]
+      ],
+      "customInstructions": "Focus on JS and TS files in this project."
+    }
+  ]
+}
+```
+
+**Example 5: Mode with File Restrictions (can be used in global or .roomodes)**
+```json
+{
+  "customModes": [
+    {
+      "slug": "markdown-editor",
+      "name": "Markdown Editor",
+      "roleDefinition": "You are Roo, a markdown editor with expertise in editing and formatting markdown files.",
+      "groups": [
+        "read",
+        ["edit", { "fileRegex": "\\.md$", "description": "Markdown files only" }],
+        "browser"
+      ],
+      "customInstructions": "Focus on editing and formatting markdown files."
+    }
+  ]
+}
+```
+By following these instructions, you can create and manage custom modes to enhance your workflow with Roo-Code.
+
 ## Community Gallery
 
-Ready to explore more? Check out the [Custom Modes Gallery](../community#custom-modes-gallery) to discover and share custom modes created by the community!
+Ready to explore more? Check out the [Custom Modes Gallery](/community#custom-modes-gallery) to discover and share custom modes created by the community!

docs/advanced-usage/enhance-prompt.md

@@ -13,15 +13,15 @@ The "Enhance Prompt" feature in Roo Code helps you improve the quality and effec
 ## How to Use Enhance Prompt
 
 1.  **Type your initial prompt:**  Enter your request in the Roo Code chat input box as you normally would.  This can be a simple question, a complex task description, or anything in between.
-2.  **Click the ✨ (Sparkle) Icon:**  Instead of pressing Enter, click the sparkle icon located to the left of the chat input box.
+2.  **Click the <Codicon name="sparkle" /> Icon:**  Instead of pressing Enter, click the <Codicon name="sparkle" /> icon located to the left of the chat input box.
 3.  **Review the Enhanced Prompt:**  Roo Code will replace your original prompt with an enhanced version.  Review the enhanced prompt to make sure it accurately reflects your intent. You can further refine the enhanced prompt before sending.
-4.  **Send the Enhanced Prompt:**  Press Enter or click the Send icon (paper plane) to send the enhanced prompt to Roo Code.
+4.  **Send the Enhanced Prompt:**  Press Enter or click the Send icon (<Codicon name="send" />) to send the enhanced prompt to Roo Code.
 
 ## Customizing the Enhancement Process
 
 The "Enhance Prompt" feature uses a customizable prompt template.  You can modify this template to tailor the enhancement process to your specific needs.
 
-1.  **Open the Prompts Tab:** Click the notebook icon in the Roo Code top menu bar.
+1.  **Open the Prompts Tab:** Click the <Codicon name="notebook" /> icon in the Roo Code top menu bar.
 2.  **Select "ENHANCE" Tab:** You should see listed out support prompts, including "ENHANCE". Click on this tab.
 3.  **Edit the Prompt Template:** Modify the text in the "Prompt" field.
 
@@ -32,7 +32,7 @@ The default prompt template includes the placeholder `${userInput}`, which will
 The API configuration used for Enhance Prompt is, by default, the same one that is selected for Roo Code tasks,
 but it can be changed:
 
-1.  **Open the Prompts Tab:** Click the notebook icon in the Roo Code top menu bar.
+1.  **Open the Prompts Tab:** Click the <Codicon name="notebook" /> icon in the Roo Code top menu bar.
 2.  **Select "ENHANCE" Tab:** You should see an "API Configuration" dropdown
 3.  **Select an API Configuration:** Choose an existing configuration, and future Enhance Prompt requests will be sent to that configured provider/model.
 

docs/advanced-usage/experimental-features.md

@@ -8,7 +8,7 @@ Roo Code includes experimental features that are still under development.  These
 
 To enable or disable experimental features:
 
-1.  Open the Roo Code settings (gear icon ⚙️ in the top right corner).
+1.  Open the Roo Code settings (<Codicon name="gear" /> icon in the top right corner).
 2.  Go to the "Advanced Settings" section.
 3.  Find the "Experimental Features" section.
 4.  Check or uncheck the boxes for the features you want to enable or disable.

docs/advanced-usage/local-models.md

@@ -73,8 +73,8 @@ Roo Code currently supports two main local model providers:
 
 
 4.  **Configure Roo Code:**
-    *   Open the Roo Code sidebar (🚀 icon).
-    *   Click the settings gear icon (⚙️).
+    *   Open the Roo Code sidebar (<Codicon name="rocket" /> icon).
+    *   Click the settings gear icon (<Codicon name="gear" />).
     *   Select "ollama" as the API Provider.
     *   Enter the Model name from the previous step (e.g., `your_model_name`).
     *   (Optional) You can configure the base URL if you're running Ollama on a different machine. The default is `http://localhost:11434`.
@@ -89,8 +89,8 @@ Roo Code currently supports two main local model providers:
     *   Select your downloaded model.
     *   Click **"Start Server"**.
 4.  **Configure Roo Code:**
-    *   Open the Roo Code sidebar (🚀 icon).
-    *   Click the settings gear icon (⚙️).
+    *   Open the Roo Code sidebar (<Codicon name="rocket" /> icon).
+    *   Click the settings gear icon (<Codicon name="gear" />).
     *   Select "lmstudio" as the API Provider.
     *   Enter the Model ID.  This should be the name of the model file you loaded in LM Studio (e.g., `codellama-7b.Q4_0.gguf`).  LM Studio shows a list of "Currently loaded models" in its UI.
     *   (Optional) You can configure the base URL if you're running LM Studio on a different machine. The default is `http://localhost:1234`.

docs/advanced-usage/mcp.md

@@ -11,7 +11,7 @@ The Model Context Protocol (MCP) is a standard for extending Roo Code's capabili
 
 ## MCP Server Status
 
-You can view and manage your MCP server connections by clicking the server icon in the top navigation bar.
+You can view and manage your MCP server connections by clicking the <Codicon name="server" /> icon in the top navigation bar.
 
 ## Finding and Installing MCP Servers
 
@@ -71,7 +71,7 @@ Roo Code provides two settings to control the use of MCP servers, to help you ma
 
 If you don't want to use MCP servers at all, you can disable them completely:
 
-1. Open the Roo Code Settings (gear icon ⚙️)
+1. Open the Roo Code Settings (<Codicon name="gear" />)
 2. Find the "Enable MCP Servers" setting
 3. Uncheck the box
 
@@ -83,7 +83,7 @@ Roo Code can be asked to assist in creating new MCP servers. This is a powerful
 
 To disable MCP server creation:
 
-1. Open the Roo Code Settings (gear icon ⚙️)
+1. Open the Roo Code Settings (<Codicon name="gear" />)
 2. Find the "Enable MCP Server Creation" setting
 3. Uncheck the box
 

docs/advanced-usage/model-temperature.md

@@ -21,8 +21,8 @@ Different tasks benefit from different temperature settings.  For example:
 
 You can adjust the temperature in the Roo Code settings:
 
-1.  **Open the Roo Code Panel:** Click the Roo Code icon (🚀) in the VS Code Activity Bar.
-2.  **Open Settings:** Click the gear icon (⚙️) in the top right corner of the Roo Code panel.
+1.  **Open the Roo Code Panel:** Click the Roo Code icon (<Codicon name="rocket" />) in the VS Code Activity Bar.
+2.  **Open Settings:** Click the <Codicon name="gear" /> icon in the top right corner of the Roo Code panel.
 3.  **Find the Temperature Setting:** In the settings panel, you'll find a "Use custom temperature" setting within the API configuration section.
 4.  **Enter the Temperature Value:** Check the box and enter the temperature value you want to use. The range is typically from 0.0 to 1.0, but this may depend on the specific model and provider.