Align repository enabledPlugins behavior with Copilot CLI
@pwang347 is already working on this.
Since Sep 18, 2026.
- Dominant language
- TypeScript
- Stars
- 193k
- Forks
- 42.7k
- PR merge metrics
- PR metrics pending
Description
When a trusted workspace declares a marketplace and plugin in .github/copilot/settings.json, Copilot CLI treats enabledPlugins as a repository-scoped activation overlay: true installs/enables the plugin for that repository, and the plugin is not enabled globally.
VS Code reads the same file, but currently treats enabledPlugins: true only as a recommendation requiring manual installation. This gives the same configuration different semantics across the two clients.
Expected: align VS Code with Copilot CLI for trusted workspaces:
true: ensure the plugin is installed and activate it for the repository.false: deactivate it for the repository.- absent: preserve the user/global state.
- Do not persist repository-only enablement into global user settings.
- Ignore repository plugin settings until the workspace is trusted.
The initial workspace-plugin implementation explicitly left enablement/disablement unification as follow-up: #300585.
Related: #327404 tracks a bug in the current recommendation flow; this issue tracks the underlying cross-client behavior alignment.
🤖 Posted by GitHub Copilot on Harald's behalf.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.