Debug mode and power steering

docs/advanced-usage/custom-modes.md

@@ -11,7 +11,6 @@ Roo Code allows you to create **custom modes** to tailor Roo's behavior to speci
 ## Why Use Custom Modes?
 
 *   **Specialization:** Create modes optimized for specific tasks, like "Documentation Writer," "Test Engineer," or "Refactoring Expert"
-*   **Default Modes Tool Access Customization:** Modify which tools are allowed for the default modes (Code, Architect, Ask). Note that restricting tools for default modes may cause unintended outcomes in Roo Code's performance
 *   **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

docs/advanced-usage/experimental-features.md

@@ -38,6 +38,10 @@ Adds a new tool for searching and replacing text in a file.
 
 Adds a new tool for inserting content at any position in a file.
 
+### Power Steering
+
+When enabled, Roo will remind the model about the details of its current mode definition more frequently. This will lead to stronger adherence to role definitions and custom instructions, but will use more tokens per message.
+
 ## Providing Feedback
 
 If you encounter any issues with experimental features, or if you have suggestions for improvements, please report them on the [Roo Code GitHub Issues page](https://github.com/RooVetGit/Roo-Code/issues).

docs/advanced-usage/model-temperature.md

@@ -16,6 +16,7 @@ Different tasks benefit from different temperature settings.  For example:
 *   **Code Mode (Low Temperature):** When writing code, you generally want precise and correct results.  A lower temperature (e.g., 0.0 - 0.3) is usually best.
 *   **Architect Mode (Medium Temperature):** When brainstorming architectural designs, you might want more creative suggestions.  A medium temperature (e.g., 0.4 - 0.7) can be helpful.
 *   **Ask Mode (Medium to High Temperature):** When asking open-ended questions or seeking explanations, a higher temperature (e.g., 0.7 - 1.0) can lead to more diverse and insightful responses.  You might even go higher for creative writing tasks.
+*   **Debug Mode (Low Temperature):** When tracking down bugs, you want precise and correct results.  A lower temperature (e.g., 0.0 - 0.3) is usually best.
 
 ## How to Adjust Temperature in Roo Code
 
@@ -32,7 +33,7 @@ Roo Code allows you to create multiple API configuration profiles.  This is *ver
 
 *   **Create a "Code - Low Temp" profile:** Configure this profile with your preferred API provider, a code-focused model (like Claude 3.5 Sonnet), and a low temperature (e.g., 0.1).
 *   **Create an "Ask - High Temp" profile:** Configure this profile with the same provider (or a different one), perhaps a model better suited for general knowledge, and a higher temperature (e.g., 0.8).
-*   **Switch Profiles:**  Use the "Configuration Profile" dropdown in the Roo Code settings to quickly switch between your saved configurations.  You can also set a default configuration for each mode (Code, Architect, Ask), so Roo Code automatically uses the appropriate settings when you switch modes.
+*   **Switch Profiles:**  Use the "Configuration Profile" dropdown in the Roo Code settings to quickly switch between your saved configurations.  You can also set a default configuration for each mode (Code, Architect, Ask, Debug), so Roo Code automatically uses the appropriate settings when you switch modes.
 
 This lets you tailor the AI's behavior to the specific task at hand without constantly adjusting settings.
 

docs/advanced-usage/prompt-engineering.md

@@ -33,7 +33,7 @@ It's often helpful to guide Roo Code through a "think-then-do" process:
 You can provide custom instructions to further tailor Roo Code's behavior. There are two types of custom instructions:
 
 *   **Global Custom Instructions:** Apply to all modes.
-*   **Mode-Specific Custom Instructions:** Apply only to a specific mode (e.g., Code, Architect, Ask, or a custom mode).
+*   **Mode-Specific Custom Instructions:** Apply only to a specific mode (e.g., Code, Architect, Ask, Debug, or a custom mode).
 
 Custom instructions are added to the system prompt, providing persistent guidance to the AI model. You can use these to:
 

docs/basic-usage/modes.md

@@ -4,14 +4,16 @@ Roo Code offers different "modes" to tailor its behavior and capabilities to spe
 
 ## Built-in Modes
 
-Roo Code comes with three built-in modes:
+Roo Code comes with four built-in modes:
 
 *   **Code Mode (Default):** This is the general-purpose coding mode.  Roo Code can read, write, and execute code in this mode. It's designed for tasks like creating new features, refactoring existing code, and fixing bugs.
 
 *   **Architect Mode:** This mode is for high-level planning and design discussions. Roo Code can read files in this mode, but it *cannot* write to files or execute commands. Use this mode to discuss system architecture, design patterns, or overall project structure.
 
 *   **Ask Mode:** This mode is for asking questions and getting explanations. Roo Code can read files, access external resources, but it *cannot* modify files or run commands. Use this mode to understand code, explore concepts, or get help with specific problems. You can use this mode to learn more about new or existing code.
 
+*   **Debug Mode:** This mode is specifically designed for systematic problem diagnosis. It uses a structured approach where Roo Code first analyzes potential causes, narrows down the most likely explanations, and validates them through strategic logging before implementing fixes. This methodical process helps ensure more accurate bug fixes.
+
 ## Why Use Modes?
 
 Modes help to:
@@ -24,7 +26,7 @@ Modes help to:
 
 You can switch between modes using the dropdown menu in the chat input area:
 
-1.  **Locate the Dropdown:**  Find the dropdown menu to the left of the chat input box. It will usually display the name of the current mode (e.g., "Code", "Architect", "Ask").
+1.  **Locate the Dropdown:**  Find the dropdown menu to the left of the chat input box. It will usually display the name of the current mode (e.g., "Code", "Architect", "Ask", "Debug").
 
 2.  **Select a Mode:** Click the dropdown and choose the mode you want to use.
 
@@ -41,5 +43,6 @@ Roo Code also allows you to create your own custom modes, with tailored instruct
 *   Start in **Code Mode** for most coding tasks.
 *   Switch to **Architect Mode** when planning or discussing high-level design.
 *   Use **Ask Mode** when you need to understand code or concepts.
-*   Experiment with different modes to find what works best for your workflow.
-*   Create **Custom Modes** to have even finer control over what actions each mode has access to.
+*   Switch to **Debug Mode** when tracking down bugs.
+*   Create **Custom Modes** to optimize Roo Code for your own project and workflows.
+*   Experiment with different modes to find what works best!

docs/faq.md

@@ -90,6 +90,7 @@ Open the Roo Code panel (<Codicon name="rocket" />) and type your task in the ch
 *   **Code:** For general-purpose coding tasks.
 *   **Architect:** For planning and technical leadership.
 *   **Ask:** For answering questions and providing information.
+*   **Debug:** For systematic problem diagnosis.
 
 You can also create [Custom Modes](/advanced-usage/custom-modes).
 

docs/index.md

@@ -28,6 +28,7 @@ Roo Code adapts to your needs with specialized [modes](basic-usage/modes):
 - **Code Mode:** For general-purpose coding tasks
 - **Architect Mode:** For planning and technical leadership
 - **Ask Mode:** For answering questions and providing information
+- **Debug Mode:** For systematic problem diagnosis
 - **[Custom Modes](advanced-usage/custom-modes):** Create unlimited specialized personas for security auditing, performance optimization, documentation, or any other task
 
 ### Smart Tools