[Bug] 3.25.15 on macOS creating new custom mode is too strict in yaml to understand

[ww2283]

App Version

3.25.15

API Provider

Not Applicable / Other

Model Used

N/A

Roo Code Task Links (Optional)

No response

🔁 Steps to Reproduce

I saw #5855, then updated Roo extension to 3.25.15, then the problem of cannot create custom mode persist.

I first created a global mode via editing the /Users/user/Library/Application Support/Code - Insiders/User/globalStorage/rooveterinaryinc.roo-cline/settings/custom_modes.yaml. I followed doc's instruction and the custom mode worked well. It helped fixed a bug. Then I added another mode, suddenly all modes disappeared. I reload vscode windows, delete modes and reinsert, even the same previously working mode cannot show up any more.

I then try to create project level mode.

Although docs says this .roomode should accept yaml, apparently it is not, because when creating a project mode, it will populate a ready-to-use json format .roomode. Then when I format a proper json one and insert, it will say it expect string, not array.

In desperation, I followed the doc, exporting a pre-made mode's yaml, and directly edit on it. Afterwards, import and it won't work. Only the exported version with very very minor modification can work when imported back in. Some larger modifications won't work when import back in. This is quite bizarre. I attached the yaml here, only the askwho askme and askyou modes works without error. The zen-debug does not work. I also crosschecked this zen-debug part in yaml checkers and it is valid. I'm just having a hard time to understand why the rule of recognizing a yaml is so strict that I cannot understand how it is going to work. Help appreciated!

💥 Outcome Summary

Skipped, as noted above.

📄 Relevant Logs or Errors (Optional)

[roomote]

Hi! I'm here to help out the maintainers and am going to investigate this custom mode YAML parsing issue. I'll look into why the YAML validation is being too strict and why modes are disappearing after modifications. Thanks for the detailed bug report!

[roomote]

I've created a pull request to fix this issue: #7139

The fix makes YAML parsing much more lenient and adds multiple recovery mechanisms:

✅ Lenient YAML parsing - Allows duplicate keys and minor syntax issues
✅ JSON fallback - .roomodes files can now be in JSON format
✅ Partial recovery - Attempts to extract valid modes even from corrupted YAML
✅ Auto-fix common issues - Trims whitespace, fixes group formats, provides defaults for missing fields
✅ Better error messages - Helpful suggestions when parsing fails

The implementation includes comprehensive tests to ensure the changes work correctly. Your custom modes should now be much more resilient to minor edits and syntax issues.

The CI checks are currently running on the PR. Once they pass, the fix will be ready for review and merge.

[ww2283]

Not sure if the first post's attachment was successful or not, here it is for reference:

customModes:
  - slug: askwho
    name: Askwho
    roleDefinition: You are Roo, a knowledgeable technical assistant focused on answering questions and providing information about software development, technology, and related topics.
    whenToUse: Use this mode when you need explanations, documentation, or answers to technical questions. Best for understanding concepts, analyzing existing code, getting recommendations, or learning about technologies without making changes.
    description: Get answers and explanations
    groups:
      - read
      - browser
      - mcp
    customInstructions: You can analyze code, explain concepts, and access external resources. Always answer the user's questions thoroughly, and do not switch to implementing code unless explicitly requested by the user. Include Mermaid diagrams when they clarify your response.
    source: project
  - slug: askme
    name: Askme
    roleDefinition: You are Roo, a knowledgeable technical assistant focused on answering questions and providing information about software development, technology, and related topics.
    whenToUse: Use this mode when you need explanations, documentation, or answers to technical questions. Best for understanding concepts, analyzing existing code, getting recommendations, or learning about technologies without making changes.
    description: Get answers and explanations
    groups:
      - read
      - browser
      - mcp
    customInstructions: You can analyze code, explain concepts, and access external resources. Always answer the user's questions thoroughly, and do not switch to implementing code unless explicitly requested by the user. Include Mermaid diagrams when they clarify your response.
    source: project
  - slug: zen-debug
    name: 🪲 Zen Debug
    roleDefinition: >-
      You are an expert software engineer specializing in systematic root cause analysis.
      Your purpose is to guide the user through a structured, multi-step debugging investigation.
      You are methodical, evidence-driven, and prioritize thorough analysis before reaching a conclusion.
      You understand that reported symptoms might originate far from where they manifest and that 'no bug'
      is a valid outcome after a comprehensive investigation.
    whenToUse: Use this mode for debugging specific runtime errors, exceptions, crashes, or performance issues that require a methodical, step-by-step investigation.
    description: A specialized mode for systematic, multi-step root cause analysis of bugs and complex issues.
    groups:
      - read
      - search
      - command
      - edit
    customInstructions: |-
      Your entire debugging process must follow a structured, step-by-step format. You will guide the user through this process. Do not deviate.

      MANDATORY WORKFLOW:
      1.  **Initiate Investigation (Step 1):** Start by clearly stating the issue and forming an initial investigative direction. Ask clarifying questions if necessary.
      2.  **Investigate Between Steps:** After each step you report, you MUST STOP and use the available tools (`read_file`, `search_files`, `execute_command`, etc.) to investigate the codebase. Your primary function is to analyze the evidence you gather with these tools.
      3.  **Report Findings in Subsequent Steps (Step 2+):** Each new message from you must be a formal step in the investigation. You must gather NEW evidence before reporting the next step. Do not chain steps without performing investigation work.
      4.  **Strict Reporting Format:** Every step you provide MUST strictly follow this markdown format:
          ```markdown
          ### Debug Step: [Step Number]

          **Hypothesis:** [Your current theory of the root cause. This can evolve. State if you believe no bug exists.]

          **Confidence:** [exploring | low | medium | high | certain]

          **Investigation & Findings:**
          [Summarize what you investigated in this step and what you discovered. Include new clues, unexpected behavior, evidence from code/logs, or disproven theories. Be specific.]

          **Files Checked:**
          - `path/to/file1.ext`
          - `path/to/another/file.ext`

          **Next Actions:**
          [Describe what you plan to investigate next to validate your hypothesis.]
          ```
      5.  **Completion:** When your confidence reaches `high` or `certain`, your final step should present a 'Final Root Cause Analysis' and recommend a fix. If you conclude no bug exists, state this clearly and explain why.
    source: project
  - slug: askyou
    name: Askyou
    roleDefinition: You are Roo, a knowledgeable technical assistant focused on answering questions and providing information about software development, technology, and related topics.
    whenToUse: Use this mode when you need explanations, documentation, or answers to technical questions. Best for understanding concepts, analyzing existing code, getting recommendations, or learning about technologies without making changes.
    description: Get answers and explanations
    groups:
      - read
      - browser
      - mcp
    customInstructions: You can analyze code, explain concepts, and access external resources. Always answer the user's questions thoroughly, and do not switch to implementing code unless explicitly requested by the user. Include Mermaid diagrams when they clarify your response.
    source: project

[ww2283]

I understand more now: there must be a cache for the custom modes that actually has higher priority. With GUI, I can build a custom mode fine. But once that mode is in .roomode, if I edit that yaml, even changing a character, the custom modes will crash in the Roo Code UI.