vscode extension tool interface

[complyue]

Context

Some tools would need vscode environment to correct function, but MCP would run the tool in separate os process, so no access to vscode env from the tool side.

This PR adds tool registration facility from other vscode extensions, otherwise basically the MCP tool integration solution.

Implementation

Please see PR contents.

How to Test

https://github.com/complyue/Roo-NB is an alternative way to add Notebook functionality to Roo, with this PR and that extension run together, it's equivalently what #1729 does.

Get in Touch

complyue Discord

---

Important

Introduces a new interface for VSCode extensions to register and manage custom tools within the Roo environment, with updates to handle tool interactions and UI components.

• Behavior:
  • Adds use_ext_tool functionality to allow VSCode extensions to register and use custom tools.
  • Updates Cline.ts, responses.ts, and system.ts to handle use_ext_tool requests.
  • Implements ExtensionToolManager in ExtensionToolManager.ts for managing extension tools.
• UI Components:
  • Adds ExtToolRow.tsx and ExtToolsView.tsx for displaying and managing extension tools in the UI.
  • Updates AutoApproveMenu.tsx, ChatRow.tsx, and ChatView.tsx to support extension tool interactions.
• Settings:
  • Updates AutoApproveSettings.tsx and SettingsView.tsx to include settings for auto-approving extension tools.
  • Adds localization strings in chat.json and settings.json for new extension tool features.

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

[changeset-bot]

⚠️ No Changeset found

Latest commit: 55a0617

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[ellipsis-dev]

This pull request is quite large, with 37 files changed and over 1000 lines added. It includes a variety of changes such as documentation updates, new features, tests, and UI components.

To improve the review process, it might be beneficial to split this pull request into smaller, more focused ones. Here are some suggestions on how to split the changes:

1. Documentation: Separate the changes related to the Extension Tool API documentation into its own pull request.
2. Core Features: Group the changes related to the core functionality of extension tools, such as those in src/core and src/exports, into another pull request.
3. UI Components: Consider creating a separate pull request for the changes in the webview-ui directory, focusing on the UI integration of extension tools.

This approach will make it easier to review and test each part independently, ensuring a smoother integration process.

[ellipsis-dev]

This error message formatter duplicates the existing invalidMcpToolArgumentError. Consider consolidating these into a single function.

• function invalidMcpToolArgumentError (responses.ts)

^{This comment was generated because it violated a code review rule: mrule_fYE6mUdYYxZL58YF.}

[ellipsis-dev]

Consider using a stricter type than Record<string, any> for the properties field in the inputSchema. Using unknown or a well-defined interface for tool parameters can improve type checking and reduce potential runtime errors.

Suggested change

	properties?: Record<string, any>
	properties?: Record<string, unknown>

^{This comment was generated because it violated a code review rule: mrule_QkEwsCio7v34DaCF.}

[mrubens]

This is really cool - thank you for the contribution!

The main thing I'm thinking about is how to make this available without confusing people who aren't interested in it. For instance could we get by without having an auto-approve toggle for this? It seems like we might want the auto-approve to be at the tool level anyway (and we should probably clean up MCP on this front as well).

Let me sleep on this and get back to you. Impressive work overall!

[complyue]

This is really cool - thank you for the contribution!

Great you are interested! I should thank you for Roo in the first place!

The main thing I'm thinking about is how to make this available without confusing people who aren't interested in it. For instance could we get by without having an auto-approve toggle for this? It seems like we might want the auto-approve to be at the tool level anyway (and we should probably clean up MCP on this front as well).

Yes, I feel MCP auto approval is already some coarse-grained than ideal, at least it implemented per-tool approval, while this PR is approving all Ext Tools as a whole, definitely not right. I thought about implementing finer grained per-tool approval for Ext Tool functions, taking MCP ui as example, but ui stuffs are more or less beyond my capacity (tho luckily Cursor + Sonnet has got me this far).

Anyway, the core idea of this PR is simple and should be rather lightweight in coding, if not messing with UI design and UX considerations. Despite this PR, I'll be very happy if Roo would officially take this idea into a generalized (MCP+, including vscode ext, maybe workspace file based etc.) framework to integrate more external/modular agentic tools, I'd greatly enjoy contributing more tools (notebook ready, a long-run ai schedule under design, and maybe more) to Roo under this framework.

Let me sleep on this and get back to you. Impressive work overall!

Thanks! And please take your time and get good sleep.

[hannesrudolph]

@complyue Thanks for submitting this PR, and sincere apologies that it took us so long to review and respond. You deserved a quicker response from us.

We're closing this PR now because it's no longer applicable due to the recent development of the Roo Code Marketplace. If you'd like to revisit this within the new context, please start by opening a new issue using our issue-first approach.

We genuinely appreciate your patience and willingness to contribute. Thanks again!