Type

Bug

Problem / Value

When a custom storage path is configured in the extension settings, custom modes stored there are not loaded. This prevents users who store settings outside the default location (for portability or sync) from seeing their custom modes.

Context

Affects users who set a custom storage location for Roo Code’s data. After configuring the setting and placing a valid custom modes YAML in that location, the mode selector still only shows built‑in modes.

Reproduction

1. In VS Code, open Roo Code settings and set “Custom storage path” to an absolute folder.

2. Inside that folder, create a “settings” directory.

3. Add a valid custom modes YAML file named “custom_modes.yaml” in the “settings” directory with at least one custom mode.

4. Reload the window or restart Roo Code and open the mode selector.

5. Expected result
   Custom mode(s) from the YAML appear in the mode selector.

6. Actual result
   Only default/built‑in modes appear; custom modes from the configured storage path are ignored.

Constraints/Preferences

• Respect the configured custom storage path consistently for all features that read from the global “settings” area (including custom modes).
• Maintain current behavior when the setting is empty (use the default location).