vscode-copilot-release icon indicating copy to clipboard operation
vscode-copilot-release copied to clipboard
verified publisher icon microsoft

Built-in tools no longer shown co-pilot enterprise

Open hu3bi opened this issue 10 months ago • 6 comments

  • Copilot Chat Extension Version: Version: 1.99.3 Commit: 17baf841131aa23349f217ca7c570c76ee87b957 Date: 2025-04-15T23:18:46.076Z Electron: 34.3.2 ElectronBuildId: 11161073 Chromium: 132.0.6834.210 Node.js: 20.18.3 V8: 13.2.152.41-electron.0 OS: Linux x64 6.12.23-1-lts

  • VS Code Version: Version: 1.99.3 Commit: 17baf841131aa23349f217ca7c570c76ee87b957 Date: 2025-04-15T23:18:46.076Z Electron: 34.3.2 ElectronBuildId: 11161073 Chromium: 132.0.6834.210 Node.js: 20.18.3 V8: 13.2.152.41-electron.0 OS: Linux x64 6.12.23-1-lts

  • OS Version: Arch, up to date

Steps to Reproduce:

  1. click on the tools icon (screenshot, red box)
  2. instead of providing built-in tools, it asks me to add an MCP Server.

Happens with any model I select.

Worth mentioning, before I switched to copilot enterprise it worked. My copilot enterprise has everything approved and allowed. Image

Workaround: use # to use built-in tools.

hu3bi avatar Apr 19 '25 15:04 hu3bi

Same issue here, not able to use any mcp tools installed by vs code extensions.

VigneshIyappan1 avatar Apr 24 '25 07:04 VigneshIyappan1

instead of providing built-in tools, it asks me to add an MCP Server.

In 1.99 the tools picker doesn't show built-in tools (we have changed that for 1.100). It's likely that your enterprise subscription prevents MCP servers for policy reasons. Please check the settings editor for the chat.mcp.enabled setting

jrieken avatar Apr 25 '25 07:04 jrieken

@jrieken

It's likely that your enterprise subscription prevents MCP servers for policy reasons. Please check the settings editor for the chat.mcp.enabled setting

I am the enterprise owner. How can I check, that this has not happened? I checked copilot policies and other policies. Looks all good to me. Don't have any org policies defined, and the one for copilot looked good too.

Please check the settings editor for the chat.mcp.enabled setting

Looks good too

hu3bi avatar Apr 25 '25 10:04 hu3bi

  • Copilot Chat Extension Version: Version: 1.99.3 Commit: 17baf841131aa23349f217ca7c570c76ee87b957 Date: 2025-04-15T23:18:46.076Z Electron: 34.3.2 ElectronBuildId: 11161073 Chromium: 132.0.6834.210 Node.js: 20.18.3 V8: 13.2.152.41-electron.0 OS: Linux x64 6.12.23-1-lts
  • VS Code Version: Version: 1.99.3 Commit: 17baf841131aa23349f217ca7c570c76ee87b957 Date: 2025-04-15T23:18:46.076Z Electron: 34.3.2 ElectronBuildId: 11161073 Chromium: 132.0.6834.210 Node.js: 20.18.3 V8: 13.2.152.41-electron.0 OS: Linux x64 6.12.23-1-lts
  • OS Version: Arch, up to date

Steps to Reproduce:

  1. click on the tools icon (screenshot, red box)
  2. instead of providing built-in tools, it asks me to add an MCP Server.

Happens with any model I select.

Worth mentioning, before I switched to copilot enterprise it worked. My copilot enterprise has everything approved and allowed. Image

Workaround: use # to use built-in tools.

saleh1599 avatar May 04 '25 02:05 saleh1599

Hey @jrieken @connor4312, this issue might need further attention.

@hu3bi, you can help us out by closing this issue if the problem no longer exists, or adding more information.

vs-code-engineering[bot] avatar Oct 03 '25 15:10 vs-code-engineering[bot]

@vs-code-engineering

With all the feature and ui changes, I am not sure how vscode is supposed to look.

This is how vscode currently looks:

AGENT: Image

Notice, that the button on agent mode only opens tools configuration menu as a floating window in the middle of vscode. ⇒ see

Image

ASK: Image

Is that to be expected or should I have this tools button?

hu3bi avatar Oct 05 '25 07:10 hu3bi