GitHub Copilot: Team Plugin Defaults Now Generally Available
GitHub made team plugin defaults generally available, letting team maintainers and organization owners pick approved Agent Plugins that are enabled by default for a team's members. The defaults apply in VS Code, the GitHub Copilot app and Copilot CLI, and members can opt out where policy allows. The feature is available for Copilot Business and Copilot Enterprise, and enterprise or organization policies still take precedence.
Key Takeaways
- Team plugin defaults are generally available for organization teams.
- Maintainers and owners pick approved Agent Plugins from the team's Customize Copilot tab on github.com.
- Defaults apply in VS Code, the Copilot app and Copilot CLI.
- Child teams do not inherit a parent team's plugin defaults.
- Members can opt out in their client where policy allows.
- Enterprise and organization policies win over team defaults, and the feature requires Copilot Business or Enterprise.
Shared Plugin Setups for Whole Teams
GitHub announced general availability of team plugin defaults for organization teams. Team maintainers and organization owners can now choose approved Agent Plugins as defaults for their team, so members get a consistent Copilot setup without each person installing the same plugins by hand.
How to Configure It
On github.com, open the organization team and select the "Customize Copilot" tab. From there, maintainers can browse available plugins or add a marketplace from a GitHub repository. The selected plugins are then enabled by default for the team's direct members in VS Code, the GitHub Copilot app and Copilot CLI. Child teams do not inherit the defaults.
Opt-Out and Policy Precedence
Members keep some control: they can turn a team plugin off in their Copilot client where policy permits. Enterprise and organization policies override team choices, and GitHub states that team defaults do not override those controls.
Availability
Team customizations are available on Copilot Business and Copilot Enterprise.