Last updated: November 20, 2026
GitHub Copilot team plugins, generally available since November 18, 2026, let team maintainers and organization owners pick Agent Plugins that turn on by default for a team’s direct members in VS Code, the GitHub Copilot app and Copilot CLI. The feature is for Copilot Business and Enterprise, and existing policies still take precedence.
Contents
- What changed on November 18
- Plugins, marketplaces and enabled states
- Team defaults compared with other controls
- How to set default plugins for a team
- Adding a private plugin marketplace
- Managing team plugins with the REST API
- What team members see and how to opt out
- Limitations to plan for
- Frequently asked questions
What changed on November 18
In a GitHub Changelog post dated November 18, 2026, GitHub announced that team customizations are generally available for organization teams. The goal is to share the Copilot plugins a team relies on without asking every member to repeat the same setup.
GitHub describes team defaults as a shared starting point between individual customization and organization-wide policy.
Related recent changes include GitHub Enterprise Server support in the GitHub Copilot app and the November Copilot CLI release.
Plugins, marketplaces and enabled states
According to GitHub’s plugins documentation, a plugin packages related customizations so you can install them together. A plugin can include custom agents, skills, hooks, extensions, MCP server configurations and LSP server configurations.
Plugins come from marketplaces. The built-in marketplace in VS Code, Copilot CLI and the GitHub Copilot app is awesome-copilot. A plugin’s identifier combines its name and its marketplace name in the form PLUGIN-NAME@MARKETPLACE-NAME.
GitHub separates three states, and the distinction matters when a colleague can see a plugin but cannot use it:
- Available: adding a marketplace makes its plugins available to browse.
- Installed: installing a plugin adds it to a surface.
- Enabled: enabling a plugin makes its components available in sessions on that surface.
Team defaults compared with other controls
This table compares team defaults with the configuration sources in the plugins documentation.
| Control | Where it is set | Effect | Can a member turn it off? |
|---|---|---|---|
| Team defaults (new) | Organization team on github.com | Enable selected plugins by default for direct team members | Yes, where policy permits |
| Repository defaults | .github/copilot/settings.json |
Enable a plugin for everyone who works in a repository | Yes, where the surface supports a local override |
| Enterprise managed settings | Enterprise policy | Require or block a plugin across supported surfaces | No. Managed policy always wins |
| Enterprise team managed settings | Enterprise team files | Add required plugins through enabledPlugins |
No. These entries are managed policy |
One practical point: managed settings cannot enable an optional plugin by default. They only require or block plugins.
How to set default plugins for a team
You need to be a team maintainer or an organization owner. The steps below follow the GitHub announcement.
- On github.com, open your organization and go to the team you want to configure.
- Select the Customize Copilot tab.
- Browse plugins from the marketplaces built into Copilot, your enterprise’s marketplaces and any marketplaces the team has added.
- If the plugin you want lives elsewhere, add a marketplace from a GitHub repository that contains a plugin marketplace. This makes its plugins available to browse.
- Add each plugin you want to the team. Adding a marketplace alone does not enable anything.
- Ask a direct member to confirm the plugin appears in their client, then test it on a small task.
Selected plugins are enabled by default for the team’s direct members in VS Code, the GitHub Copilot app and Copilot CLI. Check that each plugin supports the surfaces your team uses, because some components only work in a particular surface.
Adding a private plugin marketplace
Many teams will want to share internal plugins. GitHub’s guide to creating and sharing a plugin marketplace explains the setup. The required catalog file is marketplace.json, placed in .github/plugin/, and each plugin directory sits at the path listed in its source field.
Choose a stable, kebab-case marketplace name such as engineering-tools. Plugin identifiers include this name, so renaming the marketplace changes the identifier people use in settings and commands.
People who add the marketplace or receive its plugins need read access to the repository and must be signed in to GitHub in their client. GitHub notes that organization membership alone does not guarantee access to a private repository.
Managing team plugins with the REST API
GitHub also documents REST API endpoints for Copilot team customizations. Note that while the team feature is generally available, these endpoints are marked as public preview and subject to change.
| Method | What it does | Classic token scope |
|---|---|---|
GET |
Reads the team’s GitHub-managed customizations | admin:org or read:org |
PUT |
Replaces the customizations, creating them on the first write | admin:org |
DELETE |
Deletes the customizations; deleting ones that do not exist succeeds | admin:org |
All three use the path /orgs/{org}/teams/{team_slug}/copilot/customizations and the X-GitHub-Api-Version: 2026-03-10 header. The caller must be an organization owner or a team maintainer.
The request body has two objects. pluginAssignments is keyed by PLUGIN@MARKETPLACE, and the only documented state is defaultEnabled. extraKnownMarketplaces lists added marketplaces, for example one with a GitHub repository source.
PUT /orgs/ORG/teams/TEAM_SLUG/copilot/customizations
{
"pluginAssignments": {
"code-review@acme-marketplace": { "state": "defaultEnabled" }
},
"extraKnownMarketplaces": {
"acme-marketplace": {
"source": { "source": "github", "repo": "acme/copilot-marketplace" }
}
}
}
Because PUT replaces the whole document, read the current state with GET first and send the full list back. A 409 response means the team keeps its customizations in a repository, and a 422 response returns the validation failure reason.
What team members see and how to opt out
Team members do not need to install anything by hand. To check what is active in Copilot CLI, the CLI plugin guide lists copilot plugin list. The same guide documents copilot plugin disable PLUGIN-NAME, which turns off a plugin without uninstalling it, and copilot plugin enable PLUGIN-NAME to turn it back on.
For other recent Copilot features, see our guides to GitHub Copilot browser use and GitHub Copilot Evals.
Limitations to plan for
- Plans: team customizations are for Copilot Business and Copilot Enterprise only.
- Direct members only: child teams do not inherit defaults.
- Three clients: the announcement names VS Code, the GitHub Copilot app and Copilot CLI as the surfaces that receive team defaults.
- Defaults, not mandates: members can switch a team plugin off where policy permits. Use enterprise managed settings to require a plugin.
- Policy first: team choices cannot enable a blocked plugin or a disallowed marketplace.
- API preview: the REST endpoints may change before they reach general availability.
Frequently asked questions
What are GitHub Copilot team plugins?
They are Agent Plugins that a team maintainer or organization owner selects as defaults for an organization team. Since November 18, 2026, the selected plugins are enabled by default for the team’s direct members in VS Code, the GitHub Copilot app and Copilot CLI.
Which Copilot plans support team customizations?
GitHub says team customizations are available for Copilot Business and Copilot Enterprise. The announcement does not list a separate charge for the feature.
Can team members turn off a team plugin?
Yes, where policy permits. Team defaults are optional, so a member can turn a team plugin off in their Copilot client. Plugins that enterprise managed settings require cannot be turned off.
Do child teams inherit team plugin defaults?
No. GitHub states that selected plugins apply to the team’s direct members only. Members of child teams do not inherit them, so set defaults on each team that needs them.
Can I manage team plugins with the REST API?
Yes. GET, PUT and DELETE requests to /orgs/{org}/teams/{team_slug}/copilot/customizations read, replace and delete a team’s customizations. These endpoints are in public preview and may change.
Sources
- GitHub Changelog: Customize GitHub Copilot for your team (November 18, 2026)
- GitHub Docs: Plugins for GitHub Copilot
- GitHub Docs: REST API endpoints for Copilot team customizations
- GitHub Docs: Creating and sharing a plugin marketplace on GitHub
- GitHub Docs: Finding and installing plugins for GitHub Copilot CLI
Image: GitHub mark (Octicons), by GitHub, MIT license, via Wikimedia Commons. Placed on a white background and resized. GitHub and Copilot are trademarks of GitHub, Inc. FreeAnswers is not affiliated with or endorsed by GitHub.