GitHub Copilot team customizations are generally available: team maintainers can turn on approved agent plugins by default for direct members
A team layer now sits between personal setup and organization policy, so shared plugins no longer need per-person setup. For engineering teams rolling out Copilot plugins and skills.
// Key points
- Team maintainers and organization owners can open the Customize Copilot tab on a team and pick plugins from built-in, enterprise or team-added marketplaces as team defaults.
- Selected plugins are on by default for the team's direct members in VS Code, the Copilot app and Copilot CLI; child team members do not inherit them, and members can turn them off where policy permits.
- Enterprise and organization policies take precedence over team choices, and clients still enforce allowed marketplaces and required or blocked plugins.
- Available for Copilot Business and Copilot Enterprise.
Builder's takeYesterday's Copilot Evals covers whether a plugin is good; this covers how it gets distributed. Together, team-level skills can be tested and released like code. My advice: create a plugin marketplace repo for your team, put in only plugins that passed evals, and make those the team default instead of everyone installing their own set.
// Background · from #Coding agents
Full timeline →- Nov 19 Google releases Gemini 4 Neon at $3 input and $15 output per million tokens, with 32% lower cost per task than Carbon at its default high level
- Nov 19 Airbnb shares how it picks models for coding agents: eight new models in about five weeks, with defaults and effort ceilings set by cost per task
- Nov 19 RadixArk open-sources DaisyRose-27B: reinforcement learning on Qwen3.8-27B with 1,200 long-horizon agent tasks lifts Terminal-Bench 4.1 from 5.6% to 12.0%