Debug mode and power steering

[mrubens]

Important

Add Debug Mode for systematic problem diagnosis and Power Steering feature for stronger adherence to mode definitions.

• New Debug Mode:
  • Added as a built-in mode in modes.md, faq.md, and index.md for systematic problem diagnosis.
  • Uses a low temperature setting (0.0 - 0.3) as per model-temperature.md.
  • Included in mode-specific custom instructions in prompt-engineering.md.
• Power Steering Feature:
  • Described in experimental-features.md as a feature that increases adherence to mode definitions by using more tokens per message.
• Documentation Updates:
  • Removed a bullet point in custom-modes.md related to default modes tool access customization.
  • Updated mode switching instructions in modes.md to include Debug Mode.

^{This description was created by for d7a03a6. It will automatically update as commits are pushed.}

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to d7a03a6 in 1 minute and 31 seconds

More details

• Looked at 126 lines of code in 7 files
• Skipped 0 files when reviewing.
• Skipped posting 14 drafted comments based on config settings.

1. docs/advanced-usage/custom-modes.md:11

• Draft comment:
  The removal of the 'Default Modes Tool Access Customization' bullet is noted. Confirm that this change is intentional and that it doesn’t remove important configuration guidance for default modes.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  The comment is asking the PR author to confirm their intention regarding the removal of a specific bullet point. This violates the rule against asking the author to confirm their intention or to ensure that the behavior is intended. Therefore, this comment should be removed.

2. docs/advanced-usage/experimental-features.md:41

• Draft comment:
  The addition of the 'Power Steering' section clearly explains the feature and token usage impact. Consider noting any performance considerations if relevant.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

3. docs/advanced-usage/model-temperature.md:19

• Draft comment:
  The addition of the 'Debug Mode (Low Temperature)' bullet maintains consistency across modes. Verify that the temperature recommendations are aligned with intended debugging precision.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

4. docs/advanced-usage/prompt-engineering.md:36

• Draft comment:
  Including 'Debug' in the list for mode-specific custom instructions is a good update for consistency. Ensure all mode references are updated similarly in supporting docs.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

5. docs/basic-usage/modes.md:7

• Draft comment:
  Updating the built-in modes section to include Debug mode (and reflecting four built-in modes) is clear. The tip list has been updated accordingly—this aligns well with the new features.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

6. docs/faq.md:43

• Draft comment:
  The FAQ update now lists Debug mode among the supported modes. This ensures users are aware of all available built-in modes.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

7. docs/index.md:31

• Draft comment:
  The index now includes Debug mode in the key features section. This update provides a consistent overview of Roo Code's capabilities.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

8. docs/advanced-usage/experimental-features.md:41

• Draft comment:
  Added the 'Power Steering' section appears clear. Consider clarifying that increased token usage may affect costs for users, and if possible, provide guidance on how to manage this.
• Reason this comment was not posted:
  Confidence changes required: 50% <= threshold 50%
  None

9. docs/advanced-usage/model-temperature.md:19

• Draft comment:
  The addition of the Debug Mode bullet with low temperature settings is consistent. Please ensure that the UI and configuration defaults are updated accordingly.
• Reason this comment was not posted:
  Confidence changes required: 50% <= threshold 50%
  None

10. docs/advanced-usage/prompt-engineering.md:35

• Draft comment:
  Including Debug in the list of mode-specific custom instructions is appropriate. Ensure that all related documentation and UI elements reference Debug mode consistently.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

11. docs/basic-usage/modes.md:7

• Draft comment:
  The updated built-in modes section now correctly lists four modes, including Debug Mode. Verify that the UI dropdown order and default selection mirror this documentation.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

12. docs/faq.md:88

• Draft comment:
  The FAQ now includes Debug mode, which is helpful. Consider adding a direct link to the Debug mode documentation for users who want further details.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

13. docs/index.md:26

• Draft comment:
  The key features section in the index has been updated to include Debug Mode. This update appears consistent with the other documentation changes.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

14. docs/index.md:7

• Draft comment:
  Typographical error: The text 'Roo Code (formerly Roo Cline)' in Line 7 appears to have a typo. If this is unintended and the product was always 'Roo Code', please update 'Roo Cline' to 'Roo Code' for consistency.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

Workflow ID: wflow_CMskDyONSTs7sitH

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.