Insiders prioritizing Copilot CLI hooks over vscode extension hooks

[saikoumudi]

Does this issue occur when all extensions are disabled?: Yes/No

• VS Code Version: vscode insiders 1.120.0
• OS Version: Version 25H2

vscode insiders 1.120.0 is prioritizing the Github Copilot CLI plugin hooks over the hooks shipped via vscode insiders extension in .agents folder. thus users who have copilot cli azure plugin installed are seeing hook errors like this in vscode insiders. The screenshot is an example from Azure plugin hooks in Copilot CLI being prioritized over vscode extension (Github Copilot for Azure) hooks.

Steps to Reproduce:

1. Install Azure plugin (https://github.com/microsoft/azure-skills) in Github Copilot CLI
2. Try to run this prompt or anything related to azure that can invoke skills. Example - Build URL shortner app and deploy to azure. notice all the post tool use hook warnings in chat.

Couple of questions:

1. is it by design that local plugins are enabled by default?
2. Is there a plan to support copilot/claude hooks in vscode if users have plugins with hooks?

[pwang347]

Hi @saikoumudi, thank you for opening this issue.

1. is it by design that local plugins are enabled by default?

Will defer this to @connor4312

2. Is there a plan to support copilot/claude hooks in vscode if users have plugins with hooks?

Yes, copilot/claude hooks are supported in VS Code, see more information in https://code.visualstudio.com/docs/copilot/customization/agent-plugins#_hook-configuration-format

Seems like the issue here is we don't support PLUGIN_ROOT

[connor4312]

For Claude plugins (as given in the repo you shared) we interpolate CLAUDE_PLUGIN_ROOT, not PLUGIN_ROOT

vscode/src/vs/platform/agentPlugins/common/pluginParsers.ts

Lines 108 to 112 in 9df8712

	pluginRootToken: '${CLAUDE_PLUGIN_ROOT}',
	pluginRootEnvVar: 'CLAUDE_PLUGIN_ROOT',
	parseHooks(hookUri, json, pluginUri, workspaceRoot, userHome) {
	return interpolateHookPluginRoot(hookUri, json, pluginUri, workspaceRoot, userHome, '${CLAUDE_PLUGIN_ROOT}', 'CLAUDE_PLUGIN_ROOT');
	},

[saikoumudi]

@connor4312 - Do you have any plans to support PLUGIN_ROOT? Since it's coming from Open plugins - https://open-plugins.com/agent-builders/components/hooks

For example, I have both copilot and Claude azure plugin installed locally, however, copilot plugin is enabled by default in vscode insiders and copilot cli uses PLUGIN_ROOT. Since vscode doesnt support PLUGIN_ROOT, it is breaking our customers.

[connor4312]

For Open Plugins plugins, we do interpolate as PLUGIN_ROOT

vscode/src/vs/platform/agentPlugins/common/pluginParsers.ts

Lines 119 to 122 in 9df8712

	pluginRootToken: '${PLUGIN_ROOT}',
	pluginRootEnvVar: 'PLUGIN_ROOT',
	parseHooks(hookUri, json, pluginUri, workspaceRoot, userHome) {
	return interpolateHookPluginRoot(hookUri, json, pluginUri, workspaceRoot, userHome, '${PLUGIN_ROOT}', 'PLUGIN_ROOT');

[connor4312]

In your plugin, your Open Plugin manifest is pointing to hooks/hooks.json which uses CLAUDE_PLUGIN_ROOT. We don't replace CLAUDE_PLUGIN_ROOT when parsing in the Open Plugin format.

[saikoumudi]

@connor4312 Got it. Yes, I understand that open plugin manifest is pointing to hooks/hooks.json which is using CLUADE_PLUGIN_ROOT.

Let me clarify my questions -

1. Currently, Copilot CLI plugins are enabled by default in Vscode Insiders even when user has both copilot cli and claude code installed. Our Azure plugin in Copilot CLI points to this hooks file, which uses PLUGIN_ROOT. It works perfectly for Copilot CLI.
   If I understand what you are saying, you only honor OPEN_PLUGIN in hooks/hooks.json and not in custom hook files. Is that correct? If yes - Do you plan on supporting PLUGIN_ROOT in custom hooks file (which are not hooks/hooks.json)?
2. is it by design that local plugins in insiders are enabled by default? If yes - we have to make some changes on our end to make sure our users don't see these warnings