On 18 November 2026 GitHub announced that team customizations for GitHub Copilot are generally available for organisation teams, per its changelog.
What changed
Team maintainers and organisation owners can pick approved agent plugins and make them the default for a team. Members then start with the same set-up instead of installing plugins one by one. On github.com the setting sits in the team’s Customize Copilot tab, where plugins can be browsed from Copilot’s built-in marketplaces, an enterprise’s marketplaces, or a marketplace added from a GitHub repository.
The detail that matters
- Selected plugins are on by default for a team’s direct members in VS Code, the GitHub Copilot app and Copilot CLI.
- Defaults are optional: members can turn a team plugin off where policy allows.
- Child teams do not inherit the plugins.
- Enterprise and organisation policies win. Allowed marketplaces and required or blocked plugins still apply, and a team default cannot override them.
- It is limited to Copilot Business and Copilot Enterprise.
Why it matters
AI coding tools are moving from individual preference to team standard. Which plugins, instructions and connectors an engineering team starts from now shapes the code it produces, and it can be set centrally. That is good for consistency, and it makes tooling a governance question rather than a personal one.
So what
If you commission software, ask your development partner which AI tools and plugins their team runs by default, who approves them, and what is blocked. Our AI-assisted development work uses a defined, reviewed toolset on every project. If you are scoping a product, see custom software development or start a project.