A Guth Labs publication ↗
Back to News

GitHub makes Copilot team plugin defaults generally available

Green glass toolkit holding fitted green and cream modular components divided by a gold pathway.
AI-generated editorial illustration

GitHub made team-level Copilot customizations generally available on November 18, allowing team maintainers and organization owners to select shared plugin defaults, according to its changelog.

The feature is available for Copilot Business and Copilot Enterprise. Maintainers can use a team’s Customize Copilot tab to browse built-in, enterprise and team-added marketplaces, then select individual plugins. Adding a marketplace makes its plugins discoverable; it does not enable every plugin automatically.

Selected plugins are enabled by default for direct team members in Visual Studio Code, the GitHub Copilot app and Copilot CLI. Members of child teams do not inherit those defaults. Individuals can turn a team plugin off when their organization’s policies allow it.

Enterprise and organization rules remain authoritative. Team choices cannot override blocked plugins, required plugins or restrictions on which marketplaces are allowed.

The update adds a team-level option between personal setup and organization-wide controls, rather than replacing existing repository defaults or enterprise policies. For development groups that use the same tools, it reduces repeated setup while preserving centrally enforced restrictions and permitted individual choice.

Sources and citations

Revision history

Published .