missing role definition when selecting default mode

[devxpain]

App Version

Version: 3.19.3

API Provider

Not Applicable / Other

Model Used

N/A

🔁 Steps to Reproduce

1. Make sure the Mode's Role Definition is default value
2. Open Modes View
3. Click Preview System Prompt
4. The Role Definition is Empty

💥 Outcome Summary

Expected the Role Definition is same as default value

📄 Relevant Logs or Errors (Optional)

[dosubot]

Hi @devxpain! I'm Dosu and I’m helping the Roo-Code team.

Based on the documentation, each mode in Roo Code—including the default modes—should have a roleDefinition that defines its core identity and expertise. This value is used to shape Roo's behavior and is placed at the beginning of the system prompt when the mode is active. Custom modes and overrides (either global or project-specific) can also define or replace this value, and these overrides take precedence over the default mode's definition if present. The configuration for modes, including roleDefinition, is typically managed in .roomodes files or through the Prompts tab in the UI [source].

However, I could not find any documentation or release notes that specifically address the issue of the role definition being empty when selecting the default mode in version 3.19.3. There is a mention of a bug fix related to role definition overrides for built-in modes in version 3.2.6, which suggests that earlier versions may have had issues with how role definitions were loaded or displayed [source]. If you are experiencing this issue in 3.19.3, it may be related to that bug.

There are no documented troubleshooting steps for this specific problem. If you have not already, you might try updating to a newer version of Roo Code, as later releases include fixes and improvements related to mode configuration and role definitions. If you are using custom or project-specific mode overrides, double-check that your configuration files are valid and that no overrides are unintentionally clearing the roleDefinition.

If you need more detailed help with your specific configuration, sharing the contents of your .roomodes or custom mode files may help diagnose the issue.

To reply, just mention my name @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}   

[devxpain]

Hi @dosubot, could you take a look at #4286 to understand what I mean?

[dosubot]

Yes, I understand your meaning. The pull request #4286 specifically addresses the bug where the getModeSelection function could select a promptComponent as the active mode even if it did not have a valid roleDefinition. This led to situations where the role definition would be empty, overriding the correct definitions from built-in modes—exactly matching the issue you described in version 3.19.3.

The fix in #4286 ensures that promptComponent is only considered if it actually has a roleDefinition, so the system will fall back to the correct default or built-in mode definition if not. This change directly resolves the problem of seeing an empty role definition when previewing the system prompt with the default mode.

I could not find documentation or release notes confirming whether this fix has been released in a version after 3.19.3, but the logic and intent of the pull request match your report. If you are still seeing this issue, it is likely because you are on a version before this fix was merged and released.

To reply, just mention my name @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}