feat: add individual tool controls to settings

[KJ7LNW]

Context

This PR adds the ability to selectively enable/disable individual tools in the settings UI. This allows users to remove tools they never plan to use from the system prompt, saving valuable context tokens.

Implementation

• Added new settings schema for individual tool controls in global-settings.ts
• Created a new ToolsSettings UI component with checkboxes for each tool
• Added logic to filter tools based on these settings in tools/index.ts
• Integrated with the system prompt generation

How to Test

1. Open Roo Code settings
2. Navigate to the Tools section
3. Toggle individual tools on/off
4. Verify that disabled tools are removed from the system prompt

Get in Touch

Discord: KJ7LNW

Fixes #5963

---

Important

This PR adds UI and backend support for enabling/disabling individual tools in settings, affecting system prompt generation and tool availability.

• Settings Schema:
  • Added individual tool control settings in global-settings.ts.
• UI Components:
  • Created ToolsSettings component in ToolsSettings.tsx with checkboxes for each tool.
  • Integrated ToolsSettings into SettingsView.tsx.
• Logic:
  • Updated tools/index.ts to filter tools based on new settings.
  • Modified generateSystemPrompt.ts to incorporate tool settings.
• State Management:
  • Updated ExtensionStateContext.tsx to include tool settings.
• Webview Communication:
  • Added message handling for tool settings in webviewMessageHandler.ts.
• Localization:
  • Updated settings.json for tool-related strings.

^{This description was created by for f825bff. You can customize this summary. It will automatically update as commits are pushed.}

[shariqriazz]

I love this! ive been running similar setup on my fork for a month almost but my UI isn't very good, additionally i have an option to make #MODES part also granular so each mode can select which mode should be visible in its system prompt ( this helps when u have multiple agents packaged with specific workflows so they do not conflict with each other )

[hannesrudolph]

I have not reviewed in depth but the MCP portion of the tools are already excluded if you have MCP disabled. This seems redundant. Same with apply_diff.

[adamhill]

Thanks for doing this @KJ7LNW !

We really need some way to start excluding tools at a project level.

There are now hyper specific MCP's like "Apple Development Docs" - https://github.com/kimsungwhee/apple-docs-mcp that I really only want to use by flagging something for Swift projects only.

[daniel-lxs]

Hey @KJ7LNW, I really like the implementation, it looks super clean. I think there are a few things worth considering:

1. The system prompt currently includes references to specific tools. Should we clean that up first to avoid confusing the model if certain tools aren’t available?

2. Some tools can be disabled in different ways. For example, tools can be disabled per mode, codebase_search can be turned off via a feature flag, and MCP tools depend on whether any MCP is setup and running. Should we try to unify these so that there are no multiple places for these settings scattered across Roo Code?

3. Should these settings be tied to profiles, or even to individual modes? That could make them more useful for defining modes with limited tool access.

It might make sense to split this into a couple of smaller PRs so each part is easier to test and validate.

Let me know what you think!

[KJ7LNW]

Hey @KJ7LNW, I really like the implementation, it looks super clean. I think there are a few things worth considering:

1. The system prompt currently includes references to specific tools. Should we clean that up first to avoid confusing the model if certain tools aren’t available?

that is a good idea, I have always thought the tools should only be mentioned in the specific tool section

2. Some tools can be disabled in different ways. For example, tools can be disabled per mode, `codebase_search` can be turned off via a feature flag, and MCP tools depend on whether any MCP is setup and running. Should we try to unify these so that there are no multiple places for these settings scattered across Roo Code?

certainly I think you can completely remove the Browser items on the LHS of the global settings since it does is turn it off.

I am not sure what to suggest about MCP, but you guys seem to have a plan on how to do that, I have not used MCP so I do not have any feedback there---however if you are going to have a global tools list to turn things on and off I think it should always contain all tools and there should be a test to enforce that for when new tools are added.

3. Should these settings be tied to profiles, or even to individual modes? That could make them more useful for defining modes with limited tool access.

extending this to apply to modes is a great idea --- actually that would be the preferred implementation, but it was more complex than I wanted to tackle.

It might make sense to split this into a couple of smaller PRs so each part is easier to test and validate.

Let me know what you think!

All of those are great ideas. I do not have time to work on it so if you would like to assign this to someone else, then please do.