Live
Cloudflare Images Analytics Dashboard Adds 30‑Day Delivery VisibilityAmazon ECS Adds Native Blue/Green, Canary, and Linear Deployments for Safer Container RolloutsGemini agentic tools add LLM‑driven automation to Partner Marketing StudioGitHub Actions makes RHEL 9/10 runner images generally available for larger workloadsIntegrating Decider Models to Reduce Latency and Cost in AI Agent WorkflowsAWS Emulator Enables Local Testing of 200+ Services, but Lacks IAM ValidationSageMaker AI monitoring adds automatic latency drift, idle GPU, and configuration gap detection for inference endpointsEmbedding Proactive Governance into Enterprise‑Scale Agentic AICloudflare Images Analytics Dashboard Adds 30‑Day Delivery VisibilityAmazon ECS Adds Native Blue/Green, Canary, and Linear Deployments for Safer Container RolloutsGemini agentic tools add LLM‑driven automation to Partner Marketing StudioGitHub Actions makes RHEL 9/10 runner images generally available for larger workloadsIntegrating Decider Models to Reduce Latency and Cost in AI Agent WorkflowsAWS Emulator Enables Local Testing of 200+ Services, but Lacks IAM ValidationSageMaker AI monitoring adds automatic latency drift, idle GPU, and configuration gap detection for inference endpointsEmbedding Proactive Governance into Enterprise‑Scale Agentic AI
GitHub

Implementing Copilot team plugin defaults for consistent AI assistance

AI SummaryPowered by AI

GitHub now allows organization owners and team maintainers to set default Copilot plugins for a specific team. This gives engineers a shared baseline while preserving organization‑wide policy control.

GitHub has added the ability to define a default set of Copilot plugins at the team level. Team maintainers and organization owners can select approved Agent Plugins that are automatically enabled for direct team members in VS Code, the Copilot app, and the Copilot CLI. The change reduces per‑developer setup effort while still respecting higher‑level policies.

Configuring Copilot team plugin defaults

To apply defaults, open the target team in the GitHub web UI and choose the Customize Copilot tab. From there you can:

  • Browse plugins from the built‑in Copilot marketplace, any enterprise‑registered marketplaces, or additional marketplaces added by the team.
  • Add a marketplace by pointing to a GitHub repository that contains a plugin marketplace definition.
  • Select individual plugins to enable for the team.

Selected plugins are turned on by default for the team’s direct members across supported clients. Child‑team members do not inherit these defaults.

Policy hierarchy and overrides

Team defaults are optional and can be disabled by individual members where policy permits. Enterprise and organization policies still take precedence; they can require, block, or restrict marketplaces regardless of team settings. Copilot clients continue to enforce these higher‑level controls, and team defaults never override them.

Operational considerations

Adopting team defaults introduces a shared configuration point that simplifies onboarding and ensures consistent AI assistance across a team. However, teams should monitor which marketplaces are added, as any new marketplace expands the pool of available plugins. Because child teams do not inherit defaults, separate configuration may be needed for nested structures. Teams must also verify that their members’ ability to disable plugins aligns with security or compliance requirements.

Related CloudNinjas coverage: AI engineering.

What This Means For Practitioners

  • Plan a baseline plugin set that matches the team’s workflow and add it via the Customize Copilot UI.
  • Review organization and enterprise policies to confirm they do not conflict with the chosen defaults.
  • Document the plugin list and communicate the optional opt‑out process to team members.
  • Audit added marketplaces periodically to ensure they remain approved and do not introduce unwanted behavior.
Originally published atGitHub Changelog