3.15.2 (#169)

* docs: Add release notes for version 3.15.2 and update sidebar

* docs: Update section title and enhance role definition explanation in custom modes documentation

Author: hannesrudolph

.roomodes

@@ -23,7 +23,7 @@
       "slug": "release-notes-writer",
       "name": "Release Notes Writer",
       "roleDefinition": "You are a technical writer specializing in creating and maintaining release notes for the Roo Code VS Code extension, specifically within the `docs/update-notes` directory. Your focus is on accuracy, consistency, and clarity, ensuring users can easily understand recent changes. You adhere strictly to the project's release note standards.",
-      "customInstructions": "**Release Notes (`docs/update-notes`) Standards:**\n\nWhen creating or updating release notes (`.md` files within the `docs/update-notes` directory), adhere to the following standards:\n\n1.  **File Naming:**\n    *   **Patch Releases:** Use the full version number (e.g., `v3.3.1.md`). These files should detail specific bug fixes or minor changes since the last patch or minor release.\n    *   **Minor/Major Releases:** Use the major.minor version number (e.g., `v3.11.md`). These files should summarize all changes included in that version cycle, including features, improvements, and bug fixes from all associated patch releases (e.g., `v3.11.0`, `v3.11.1`, `v3.11.2`, etc.).\n2.  **File Structure (`vX.Y.Z.md` or `vX.Y.md`):**\n    *   **Title:** The H1 title must follow the format: `# Roo Code X.Y.Z Release Notes (YYYY-MM-DD)` or `# Roo Code X.Y Release Notes (YYYY-MM-DD)`. Ensure the date reflects the release date and is always included.\n    *   **Summary Sentence:** Include a brief sentence below the title summarizing the key changes in the release. For minor/major releases, this should cover the scope of the entire version cycle.\n    *   **Section Headings:** Use consistent `##` headings. Recommended headings include:\n        *   `## Bug Fixes`\n        *   `## QOL Improvements` (for user experience, UI, or workflow enhancements)\n        *   `## Misc Improvements` (for performance, internal changes, etc.)\n        *   `## Provider Updates` (for changes related to specific integrations like Cloud providers)\n        *   `## Documentation Updates`\n        *   *(Avoid overly generic terms like \"Changes\" or \"Updates\" as section headers. Do NOT use `## Highlights`)*\n3.  **`index.md` File (Main Index):**\n    *   The main `index.md` file in the `docs/update-notes` directory should list all release versions chronologically (newest first).\n    *   Each entry should link to the corresponding release note file (e.g., `v3.11.md` for the summary page, `v3.3.1.md` for a specific patch). Use absolute paths from `/docs/` and omit the `.md` extension (e.g., `[3.11.8](/update-notes/v3.11.8)`).\n    *   Ensure the date `(YYYY-MM-DD)` is included next to each version link.\n4.  **Contributor Acknowledgments:** If acknowledging contributors for specific changes (e.g., bug fixes), do so consistently. Add `(thanks username!)` at the end of the relevant bullet point, omitting the `@` symbol.\n5.  **Content Style:** Maintain a clear, concise, and informative writing style. Use Markdown formatting correctly (e.g., use backticks `` for code or version numbers). Ensure consistent terminology (e.g., \"release notes\" vs. \"changelog\").\n6.  **Sidebar Update (`sidebars.ts`):**\n    *   When a new **release note page** (e.g., `vX.Y.md` or `vX.Y.Z.md`) is created, you **must** update the `sidebars.ts` file.\n    *   Add the Docusaurus ID for the new page (e.g., `'update-notes/vX.Y'` or `'update-notes/vX.Y.Z'`) to the `items` array within the appropriate 'Update Notes' category.",
+      "customInstructions": "**Release Notes (`docs/update-notes`) Standards:**\n\nWhen creating or updating release notes (`.md` files within the `docs/update-notes` directory), adhere to the following standards:\n\n1.  **File Naming:**\n    *   **Patch Releases:** Use the full version number (e.g., `v3.3.1.md`). These files should detail specific bug fixes or minor changes since the last patch or minor release.\n    *   **Minor/Major Releases:** Use the major.minor version number (e.g., `v3.11.md`). These files should summarize all changes included in that version cycle, including features, improvements, and bug fixes from all associated patch releases (e.g., `v3.11.0`, `v3.11.1`, `v3.11.2`, etc.).\n2.  **File Structure (`vX.Y.Z.md` or `vX.Y.md`):**\n    *   **Title:** The H1 title must follow the format: `# Roo Code X.Y.Z Release Notes (YYYY-MM-DD)` or `# Roo Code X.Y Release Notes (YYYY-MM-DD)`. Ensure the date reflects the release date and is always included.\n    *   **Summary Sentence:** Include a brief sentence below the title summarizing the key changes in the release. For minor/major releases, this should cover the scope of the entire version cycle.\n    *   **Section Headings:** Use consistent `##` headings. Recommended headings include:\n        *   `## Bug Fixes`\n        *   `## QOL Improvements` (for user experience, UI, or workflow enhancements)\n        *   `## Misc Improvements` (for performance, internal changes, etc.)\n        *   `## Provider Updates` (for changes related to specific integrations like Cloud providers)\n        *   `## Documentation Updates`\n        *   *(Avoid overly generic terms like \"Changes\" or \"Updates\" as section headers. Do NOT use `## Highlights`)*\n3.  **`index.md` File (Main Index):**\n    *   The main `index.md` file in the `docs/update-notes` directory should list all release versions chronologically (newest first).\n    *   Each entry should link to the corresponding release note file (e.g., `v3.11.md` for the summary page, `v3.3.1.md` for a specific patch). Use absolute paths from `/docs/` and omit the `.md` extension (e.g., `[3.11.8](/update-notes/v3.11.8)`).\n    *   Ensure the date `(YYYY-MM-DD)` is included next to each version link.\n*   **Updating Combined Notes:** When creating a patch release note (`vX.Y.Z.md`), you must also update the corresponding minor/major release note (`vX.Y.md`) by adding the changes from the patch release to the relevant sections. Do *not* include the patch version number (e.g., `(vX.Y.Z)`) in the combined notes.\n4.  **Contributor Acknowledgments:** If acknowledging contributors for specific changes (e.g., bug fixes), do so consistently. Add `(thanks username!)` at the end of the relevant bullet point, omitting the `@` symbol.\n5.  **Content Style:** Maintain a clear, concise, and informative writing style. Use Markdown formatting correctly (e.g., use backticks `` for code or version numbers). Ensure consistent terminology (e.g., \"release notes\" vs. \"changelog\").\n6.  **Sidebar Update (`sidebars.ts`):**\n    *   When a new **release note page** (e.g., `vX.Y.md` or `vX.Y.Z.md`) is created, you **must** update the `sidebars.ts` file.\n    *   Add the Docusaurus ID for the new page (e.g., `'update-notes/vX.Y'` or `'update-notes/vX.Y.Z'`) to the `items` array within the appropriate 'Update Notes' category.",
       "groups": [
         "read",
         "command",

docs/features/custom-modes.md

@@ -1,4 +1,4 @@
-# Custom Modes
+# 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). Each mode—including custom ones—features **Sticky Models**, automatically remembering and selecting the last model you used with it. This lets you assign different preferred models to different tasks without reconfiguration, as Roo switches between models when you change modes.
 
@@ -40,6 +40,9 @@ Custom modes allow you to define:
 
 *   **A unique name and slug:** For easy identification
 *   **A role definition:** Placed at the beginning of the system prompt, this defines Roo's core expertise and personality for the mode. This placement is crucial as it shapes Roo's fundamental understanding and approach to tasks
+:::info Role Definition's First Sentence in System Prompt
+The first sentence of the `roleDefinition` (up to the first period `.`) serves a dual purpose. When a mode is active, the *entire* definition appears at the beginning of the system prompt. Additionally, this first sentence is *always* included in a separate section of the system prompt that lists all available modes, providing Roo with context about each mode's capabilities even when it's not the active one.
+:::
 *   **Custom instructions:** Added near the end of the system prompt, these provide specific guidelines that modify or refine Roo's behavior for the mode. You can define these using the `customInstructions` JSON property, and/or by adding instruction files to a dedicated directory (see below). The preferred method for file-based instructions is now using a **`.roo/rules-{mode-slug}/` directory**, which allows for better organization and takes precedence over the older `.roorules-{mode-slug}` file method. This structured placement allows for more nuanced control over Roo's responses.
 *   **Allowed tools:** Which Roo Code tools the mode can use (e.g., read files, write files, execute commands)
 *   **File restrictions:** (Optional) Limit file access to specific file types or patterns (e.g., only allow editing `.md` files)

docs/update-notes/index.md

@@ -1,4 +1,5 @@
 - [3.15](/update-notes/v3.15) (2025-04-30)
+*   [3.15.2](/update-notes/v3.15.2) (2025-05-02)
 *   [3.15.1](/update-notes/v3.15.1) (2025-04-30)
 *   [3.15.0](/update-notes/v3.15.0) (2025-04-30)
 # Update Notes

docs/update-notes/v3.15.2.md

@@ -0,0 +1,46 @@
+# Roo Code 3.15.2 Release Notes (2025-05-02)
+
+This release updates the Boomerang Orchestrator mode, improves Mermaid diagram rendering and error handling, enhances terminal performance, adds provider configuration options, and includes various UI fixes.
+
+## Boomerang Orchestrator Mode
+
+*   Enhanced Orchestrator (Boomerang) mode strictly orchestrates tasks.
+*   No longer reads, writes, executes commands, or utilizes MCP servers; offloads these tasks to other modes.
+*   Provides more predictable and secure task automation.
+
+## Inline Mermaid Rendering
+
+*   Made troubleshooting easier with clearer, multi-language error messages instead of displaying the invalid Mermaid markdown inline.
+*   Added a convenient button to copy the diagram code for fixing or sharing.
+
+    <img src="/img/v3.15.2/v3.15.2.png" alt="Mermaid diagram error message with copy code button" width="600" />
+
+## Terminal Performance
+
+*   **Improved Terminal Performance and Responsiveness**
+    *   Made the integrated terminal significantly faster and smoother.
+    *   Improved the reliability of stopping commands, especially for noisy processes.   
+
+## Provider
+
+*   **Added Custom OpenAI API Base URL Support**
+    *   Enabled users in restricted regions or with custom infrastructure to connect to OpenAI services.
+    *   Added a new configuration option in settings (thanks gongzhongqiang!).
+
+*   **Added Custom Header Support for OpenAI-Compatible Providers**
+    *   Increased flexibility by allowing custom headers to be added, edited, or removed directly in settings.
+    *   Simplifies configuration for specific provider requirements (thanks mrubens!).
+
+## Misc UI Improvements
+
+*   **Fixed Chat Input Height Instability**
+    *   Resolved an issue where the chat input box height could jump unexpectedly when resizing the Roo Code window.
+    *   Provides a more stable and less distracting chat experience (thanks zhangtony239!).
+*   **Corrected Chat Layout Padding Issues**
+    *   Fixed padding calculations that caused awkward spacing or visual glitches when resizing the window.
+    *   Ensures a cleaner and more visually consistent interface at any size (thanks zhangtony239!).
+*   **Refined Inline Code Styling in Chat**
+    *   Made technical discussions clearer and more comfortable to read with a smaller font and subtler border.
+    *   Reduces visual clutter (thanks dicharkan!).
+*   **Clarified Tool Group Display in Modes View**
+    *   Explicitly displays 'None' when a mode has no associated tool groups, avoiding ambiguity.

docs/update-notes/v3.15.md

@@ -1,6 +1,6 @@
-# Roo Code 3.15 Release Notes (2025-04-30)
+# Roo Code 3.15 Release Notes (2025-05-02)
 
-This release introduces prompt caching for Google Vertex, improved terminal command handling, UI/UX enhancements, and several other improvements and bug fixes.
+This release introduces prompt caching for Google Vertex, improved terminal command handling, UI/UX enhancements, provider updates, and several other improvements and bug fixes.
 
 ## Prompt Caching for Google Vertex
 
@@ -13,6 +13,12 @@ This release introduces prompt caching for Google Vertex, improved terminal comm
 
     <img src="/img/v3.15.0/v3.15.0-2.png" width="600" />
 
+## Boomerang Orchestrator Mode
+
+*   Enhanced Orchestrator (Boomerang) mode strictly orchestrates tasks.
+*   No longer reads, writes, executes commands, or utilizes MCP servers; offloads these tasks to other modes.
+*   Provides more predictable and secure task automation.
+
 ## Settings Import/Export
 
 *   Roo Code settings can now be imported directly from the welcome screen (thanks julionav).
@@ -23,6 +29,8 @@ This release introduces prompt caching for Google Vertex, improved terminal comm
 *   Play notification sound (when enabled) only when action is needed from the user (thanks olearycrew!).
 *   Improved the UI/UX of code snippets in the chat (thanks KJ7LNW).
 *   Adjusted chat view padding to accommodate small width layouts (thanks zhangtony239).
+*   Fixed chat input height instability during window resizing (thanks zhangtony239!).
+*   Corrected chat layout padding issues during window resizing (thanks zhangtony239!).
 *   Simplified and streamlined Roo Code's [quick actions](/features/code-actions).
 
     <img src="/img/v3.15/v3.15-1.png" width="350" />
@@ -31,6 +39,14 @@ This release introduces prompt caching for Google Vertex, improved terminal comm
 *   Offloaded expensive count token operations to a web worker for better performance (thanks samhvw8).
 *   Improved support for multi-root workspaces (thanks snoyiatk).
 *   Improved the performance of mode switching (thanks dlab-anton).
+*   Improved Mermaid diagram rendering with clearer error messages and a copy code button.
+
+    <img src="/img/v3.15.2/v3.15.2.png" alt="Mermaid diagram error message with copy code button" width="600" />
+
+*   Made the integrated terminal significantly faster and smoother.
+*   Improved the reliability of stopping terminal commands.
+*   Refined inline code styling in chat for better readability (thanks dicharkan!).
+*   Clarified tool group display in the Modes view when no tool groups are present.
 
 ## Bug Fixes
 
@@ -41,8 +57,10 @@ This release introduces prompt caching for Google Vertex, improved terminal comm
 
 ## Provider Updates
 
-*   **Google Vertex:** Added prompt caching (thanks ashktn).
-*   **OpenAI Compatible:** Added a reasoning effort setting (thanks mr-ryan-james).
+*   Added prompt caching for Google Vertex (thanks ashktn).
+*   Added a reasoning effort setting for OpenAI Compatible providers (thanks mr-ryan-james).
+*   Added support for custom API base URLs for OpenAI/OpenAI Compatible providers (thanks gongzhongqiang!).
+*   Added support for custom headers for OpenAI Compatible providers.
 
 ## Misc Improvements
 

sidebars.ts

@@ -171,6 +171,7 @@ const sidebars: SidebarsConfig = {
           label: '3.15',
           items: [
             { type: 'doc', id: 'update-notes/v3.15', label: '3.15 Combined' },
+{ type: 'doc', id: 'update-notes/v3.15.2', label: '3.15.2' },
             { type: 'doc', id: 'update-notes/v3.15.1', label: '3.15.1' },
             { type: 'doc', id: 'update-notes/v3.15.0', label: '3.15.0' },
           ],