Enterprise-managed settings support any default model
Organizations can now configure a preferred GitHub Copilot model as the default for new conversations through enterprise-managed settings, allowing teams to choose the model that best suits their workflows.
You can now set your preferred GitHub Copilot model as the default for new conversations through enterprise-managed settings. This lets you choose the default model that best fits your workflows.
You can also customize the default by enterprise team, assigning a different default model based on team membership. Set the model key as overridable and update team configuration files in team-mappings.json so that enterprise teams can choose their own preferred default model. All other users inherit your enterprise default. Model defaults in managed settings are generally available with Copilot Business and Copilot Enterprise in the GitHub Copilot app, Copilot CLI, and Visual Studio Code.
Learn more in our docs about enterprise managed settings, or join the discussion in the GitHub Community.
The post Enterprise-managed settings support any default model appeared first on The GitHub Blog.
Source: original entry ↗
More from GitHub
Follow GitHub to get its new changes in your feed and email digest.
Copilot model policy API for enterprise, orgs, and teams
REST API endpoints now available to retrieve and update Copilot model policies for enterprises, teams, apps, and organizations, enabling centralized policy management at scale.
GitHub Copilot models deprecated
GitHub has deprecated certain models across GitHub Copilot experiences including Chat, inline edits, and code completions, effective October 19, 2026. Users may need to migrate to supported models.
Some Git over HTTPS may temporarily require authentication
GitHub may temporarily require authentication for clones and fetches of public repositories over HTTPS during periods of unusual traffic to protect service availability.