Skip to content

Clarify custom mode YAML parsing limitations#237

Closed
HumanSpark wants to merge 1 commit into
RooCodeInc:mainfrom
HumanSpark:patch-1
Closed

Clarify custom mode YAML parsing limitations#237
HumanSpark wants to merge 1 commit into
RooCodeInc:mainfrom
HumanSpark:patch-1

Conversation

@HumanSpark

@HumanSpark HumanSpark commented Jun 24, 2025

Copy link
Copy Markdown

This commit updates the documentation for manually editing custom modes (.roomodes) to improve clarity and help users avoid some parsing pitfalls discovered during real-world testing.

The key changes include:

  • Adding a new "Troubleshooting & Known Limitations" section to centralize practical advice.
  • Clarifying that YAML Anchors & Aliases (&, *) are not supported by the parser.
  • Warning that the complex fileRegex permission syntax is unstable and recommending a simpler, more reliable alternative (groups: [read, edit]).
  • Adding guidance on basic details like ensuring UTF-8 file encoding and avoiding invisible characters in indentation.

These updates provide an accurate reflection of the YAML parser's behavior and will lead to a better user experience.


Important

Updates documentation to clarify YAML parsing limitations for custom modes, including unsupported features and recommended practices.

  • Documentation Updates:
    • Adds "Troubleshooting & Known Limitations" section in custom-modes.mdx.
    • Clarifies unsupported YAML Anchors & Aliases (&, *).
    • Advises against using complex fileRegex syntax due to instability.
    • Recommends simple groups: [read, edit] permissions.
    • Emphasizes UTF-8 encoding and avoiding invisible characters in indentation.

This description was created by Ellipsis for 4e1e043. You can customize this summary. It will automatically update as commits are pushed.

This commit updates the documentation for manually editing custom modes (`.roomodes`) to improve clarity and help users avoid some parsing pitfalls discovered during real-world testing.

The key changes include:

* Adding a new "Troubleshooting & Known Limitations" section to centralize practical advice.
* Clarifying that YAML Anchors & Aliases (`&`, `*`) are not supported by the parser.
* Warning that the complex `fileRegex` permission syntax is unstable and recommending a simpler, more reliable alternative (`groups: [read, edit]`).
* Adding guidance on basic details like ensuring UTF-8 file encoding and avoiding invisible characters in indentation.

These updates provide an accurate reflection of the YAML parser's behavior and will lead to a better user experience.
@vercel

vercel Bot commented Jun 24, 2025

Copy link
Copy Markdown

@HumanSpark is attempting to deploy a commit to the Roo Code Team on Vercel.

A member of the Team first needs to authorize it.

Comment thread docs/features/custom-modes.mdx
@daniel-lxs

Copy link
Copy Markdown
Member

Thank you @HumanSpark!

@hannesrudolph can you take a look?

@daniel-lxs daniel-lxs moved this from Triage to PR [Needs Prelim Review] in Roo Code Roadmap Jun 24, 2025
@hannesrudolph

Copy link
Copy Markdown
Contributor

@HumanSpark why not just fix the limitation?

@HumanSpark

Copy link
Copy Markdown
Author

@HumanSpark why not just fix the limitation?

Good question. Lack of confidence mostly! I've never used git before, and haven't "coded in anger" in decades.

@daniel-lxs

Copy link
Copy Markdown
Member

Should be fixed by RooCodeInc/Roo-Code#5099

@daniel-lxs daniel-lxs moved this from PR [Needs Prelim Review] to Done in Roo Code Roadmap Jun 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

No open projects
Archived in project

Development

Successfully merging this pull request may close these issues.

3 participants