Disable Default Modes

[hannesrudolph]

I have a related use case where I want to customize the built in modes with knowledge of an internal framework and add some custom modes that are specific to the framework.

For example, I have custom rules for the Code mode that teach Roo to write code in our framework.

I’m not sure that I have a use for all four default modes though, and I don’t want to override them to add internal context and then keep up with upstream changes to the default modes though instructions.

It does feel like a simple toggle to enable or disable any mode, built in or custom, would be useful.

Agree with this 100%

Originally posted by @mrubens in #2588

[daniel-lxs]

Hey, do you consider #2795 a suitable solution for this?
For example, your custom mode could have a "When to use" (from this PR #3571) rule to prefer that mode over the default ones.

I don’t want to override them to add internal context and then keep up with upstream changes to the default modes though instructions.

When you override default modes, the only thing being overridden are the custom instructions.
Could you clarify what you mean by "keeping up with upstream changes"?

The main concern with disabling default modes instead of overriding them is that it could happen accidentally and render Roo Code unable to, for example, edit code if Code mode is disabled.

[gridaphobe]

Excluding the unneeded modes from the switch-mode tool would be useful, yeah. But ideally I think I’d exclude them from the dropdown picker as well.

I understand you could misconfigure Roo to the point of being unusable, but that’s no different than what you can break by overriding the system prompt, which Roo does allow.

[daniel-lxs]

@gridaphobe

but that’s no different than what you can break by overriding the system prompt, which Roo does allow.

Actually, there's a difference, we have a permanent warning when footgun is active:

How do you suggest we warn users (permanently if possible) when they turn off the default modes?

I think @hannesrudolph could agree that if we don't do this right, it could lead to a lot of support requests/threads from users who forget they disabled the custom modes or don't get what that means.

[gridaphobe]

Ah, didn’t realize you had that warning.

As far as preventing accidental confusion, I think I’d expect something like the following:

1. All defined modes are visible in the modes menu, regardless of enabled status.
2. The modes menu has a toggle button to enable/disable modes. And probably it should have some clear visual indicator in the tab bar of which modes are enabled/disabled.
3. To prevent making the system completely unusable, we should probably require at least one active mode. Maybe the Code mode is always active and cannot be disabled since it’s the more basic mode. Or we just require that at least one mode be active, and don’t prescribe further.

I think that would make it pretty clear and understandable.

[daniel-lxs]

@gridaphobe
Yes, a PR that considers these points makes more sense. Basically, for any feature that could potentially break Roo Code, we should add a warning or indicator.