Free Intensive Nov 21–22Free 2-day hands-on Vibecoding Intensive on Nov 21–22 at 16:00 MSK (Sat–Sun) · Live Cohort 3 starts Nov 23Join Free →Cohort 3 (Nov 23)
ReleaseInsight · On RadarGitHub Changelog→ original

GitHub Copilot now lets teams share plugins by default

GitHub Copilot now has team customizations. A maintainer or organization owner picks approved plugins, and they turn on automatically for team members. Previously, each person had to repeat the same setup manually. The plugins work in VS Code, the GitHub Copilot app, and Copilot CLI, and enterprise and organization policies still take precedence over the team's choices. For a new hire, this means the right tools are already enabled on day one.

AI-processed from GitHub Changelog; edited by Hamidun News
GitHub Copilot now lets teams share plugins by default
Source: GitHub Changelog. Collage: Hamidun News.
Listen to article
Article Fact Sheet & Key Figures
ParameterDetails
Primary sourceGitHub Changelog ↗
Editor-in-Chief
Key metric #1Available on Copilot Business and Copilot Enterprise plans
Key metric #2Members of child teams do not inherit plugins
Key metric #3Any member can turn off a plugin if policy allows it

Picture a new developer joining a team. They install the editor, connect to the repositories, and then spend half a day asking colleagues which Copilot plugins everyone uses and how to enable them. Each person ends up with a different configuration, and there are no shared rules. GitHub is closing that gap: team customizations for Copilot are now generally available for teams within organizations.

What changed

Until now, Copilot had two levels of configuration: personal, which each person assembles for themselves, and the organization or enterprise level, which sets policies. Now there is a layer in between. Team maintainers and organization owners can select approved agent plugins and make them team defaults. In GitHub's wording, this is a shared starting point between individual customization and organization-wide policy.

Setup happens on github.com. You open the organization's team page and go to the Copilot plugin settings. Plugins can come from several sources: Copilot's built-in marketplaces, your enterprise's private marketplaces, and any the team has added itself. You can also connect a GitHub repository that contains a plugin marketplace. Its contents then become viewable, and the plugins you need are added to the team one by one.

Where it works and its limits

Selected plugins are enabled by default for direct members of the team. They work in VS Code, the GitHub Copilot app, and Copilot CLI. There are several important caveats:

  • Members of child teams do not inherit plugins from the parent team. If you have a nested structure, you must configure defaults at each level.
  • Team defaults are optional. A member can disable a plugin in their Copilot client if policy allows it.
  • Enterprise and organization policies take precedence over team choices. Copilot clients still enforce which marketplaces are permitted and which plugins are required or blocked. Team settings do not override these rules.

The feature is available only on Copilot Business and Copilot Enterprise plans. Owners of individual plans do not need it by definition, since they have no teams.

Why it matters for practitioners

The main benefit is organizational. Agent plugins, such as those that add external tools, codebase knowledge, or workflows, are useful only when people actually use them. When they had to be installed manually, they stayed with enthusiasts while everyone else worked with a plain Copilot. Team defaults close that gap: something useful one person finds can become the norm for the whole team in a couple of clicks.

For team leads and platform engineers, this is also a way to govern lightly. Hard bans and mandatory plugins stay at the organization level, while the team gets freedom to choose a convenient set within what is allowed. If, for example, the backend team and the mobile team use different tools, they don't need to argue about a company-wide policy.

What to do right now:

  1. Check which Copilot plugins your developers already use on their own. Chances are the best of them can become the team standard.
  2. Pick one or two maintainers who will own the team's plugin list.
  3. If you have a custom marketplace in a repository, connect it to the team and add vetted plugins from it.
  4. Remember nested teams: their defaults must be set separately.

This is a modest update with no headline metrics, but small changes like this determine whether an AI assistant becomes a shared team tool or stays a personal toy for a few people. GitHub has put the details and discussion in the Copilot documentation and community.

Story

Key Questions Answered

What changed?

Until now, Copilot had two levels of configuration: personal, which each person assembles for themselves, and the organization or enterprise level, which sets policies. Now there is a layer in between. Team maintainers and organization owners can select approved agent plugins and make them team defaults. In GitHub's wording, this is a shared starting point between individual customization and organization-wide policy. Setup happens on github.com.

Where it works and its limits?

Selected plugins are enabled by default for direct members of the team. They work in VS Code, the GitHub Copilot app, and Copilot CLI. There are several important caveats: Members of child teams do not inherit plugins from the parent team. If you have a nested structure, you must configure defaults at each level. Team defaults are optional. A member can disable a plugin in their Copilot client if policy allows it. Enterprise and organization policies take precedence over team choices.

Why it matters for practitioners?

The main benefit is organizational. Agent plugins, such as those that add external tools, codebase knowledge, or workflows, are useful only when people actually use them. When they had to be installed manually, they stayed with enthusiasts while everyone else worked with a plain Copilot. Team defaults close that gap: something useful one person finds can become the norm for the whole team in a couple of clicks. For team leads and platform engineers, this is also a way to govern lightly.

ZK
Zhemal Khamidun — CPO at Alpina Digital, product manager of AlpinaGPT. Building AI products since 2019. Hamidun News is a pet project that grew into a production aggregator with 6,000+ readers.
✦ Hands-On AI Engineering · Hamidun Academy

Build & Ship Production AI Agents Without Boilerplate Code

Start your free 72-hour trial at Hamidun Academy (academy.hamidun.com) — interactive lessons on Claude Code & Cursor, live Tech Radar, and production agent templates.

Start 72h Free Trial →Vibe-Coding Intensive
What do you think?
Loading comments…