GitHub Enterprise administrators can now set model to auto in enterprise managed-settings.json so new Copilot conversations start with auto model selection.
The setting is part of a broader managed-settings system that GitHub also made generally available on July 1. Enterprise Cloud customers can keep managed-settings.json in a selected organization’s .github-private repository. GitHub says the configuration applies in VS Code and Copilot CLI for users licensed through Copilot Business or Copilot Enterprise.
This moves model routing from a developer habit into an enterprise standard.
Auto routing becomes a default, not just a user choice
GitHub says administrators can add auto to .github-private/.github/copilot/managed-settings.json so new conversations begin with Copilot auto model selection. Users can still switch to a different model for a specific conversation.
That balance is important. The enterprise can make auto routing the starting point without fully removing local discretion. The admin goal is consistency: reduce the number of users picking models by habit, hype, or stale preference when the system can route based on task.
The managed-settings post gives the control plane. Supported keys include extraKnownMarketplaces, enabledPlugins, strictKnownMarketplaces, disableBypassPermissionsMode, and model. GitHub says supported file-based user configuration is overridden for those keys, and the managed configuration is fetched when a user authenticates, stored in memory, and refreshed hourly.
Routing and governance are merging
This update fits GitHub’s larger Copilot control pattern. The same week included session streaming, credit controls, browser tools, vision, and Kimi K2.7 Code as a new selectable model. Capability is expanding, and so is the administrative layer around it.
For engineering leaders, model routing is no longer only a quality question. It is a policy question. Which model is allowed for which task? What happens by default? Who can override? How do those choices show up in audit, billing, and incident review?
Auto selection can be useful because developers do not always know which model is best for a task. It can also hide a decision that teams may want to understand. A routed answer still needs governance around allowed providers, data handling, cost, and task type.
