Roo Code — Agents
- File format
- YAML
- Syllago install method
- Project scope, Direct copy
- Symlink support
- Yes
- Native frontmatter fields
-
slug,name,roleDefinition,whenToUse,customInstructions,groups
Features
How each feature converts to syllago's canonical format. See format conversion for what these statuses mean.
Fields
Native frontmatter or config fields this provider exposes. The first column is the provider's own field name; the canonical key column links to syllago's cross-provider equivalent.
| Provider field | Conversion | Canonical key | Summary |
|---|---|---|---|
customModes | Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more → | — | Custom modes live in .roomodes (project) or custom_modes.yaml (global) as a YAML array of mode entries, not individual Markdown files per mode. |
groups | Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more → | — | Array declaring which Roo Code tool groups (read, edit, browser, command, mcp) the mode may use; edit may also carry a fileRegex restriction object for path-scoped file writes. |
roleDefinition | Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more → | — | Long-form text defining the mode's persona and system prompt; the primary behavioral instruction channel for a custom mode. |
customInstructions | Conversion type: No canonical equivalent — appended as prose in a conversion notes block so nothing is silently lost. Learn more → | — | Additional mode-specific instructions appended to roleDefinition to refine behavior without rewriting the persona. |
source | Conversion type: No canonical equivalent — appended as prose in a conversion notes block so nothing is silently lost. Learn more → | — | Optional source field on a mode entry annotates whether the mode is project-scoped or global-scoped for UI display. |
whenToUse | Conversion type: No canonical equivalent — appended as prose in a conversion notes block so nothing is silently lost. Learn more → | — | Optional guidance on when the orchestrator or user should switch to this mode; consumed by mode-selection heuristics. |
Other features
Behaviors, conventions, and capabilities that aren't tied to a single named field — things like path-based activation, discovery rules, and lifecycle behavior.
| Feature | Conversion | Summary |
|---|---|---|
agent_scopes | Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more → | Two scopes: project (.roomodes at the project root) and global (custom_modes.yaml in Roo Code's settings dir); project entries override global entries with the same slug |
definition_format | Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more → | YAML file (.roomodes for project scope, custom_modes.yaml for global scope) containing an array of custom mode entries with slug, name, roleDefinition, groups, and optional whenToUse, description, customInstructions fields |
invocation_patterns | Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more → | Users switch modes via the mode selector or /mode command; each mode is a distinct operating persona with its own roleDefinition and tool groups |
tool_restrictions | Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more → | groups array declares which tool groups (e.g., read, edit, browser, command, mcp) the mode may use; group entries may be strings or objects with fileRegex restrictions |
| Built-in modes (code, architect, ask, debug, orchestrator) | Not portable Conversion type: Not portable Unique to this provider — can’t be carried across providers. Learn more → | Five built-in modes ship with Roo Code; custom mode slugs must not collide with these, and custom-mode rule directories (.roo/rules-<slug>/) extend the same activation model. |