Copilot Auto Is Now a Per-Prompt Budget Decision

GitHub Copilot’s automatic model selection now has efficiency, balance, and intelligence settings. The names sound like three model lists. GitHub says they use the same eligible pool and make a different routing decision for each prompt.

That turns “auto” into a small policy engine. It weighs expected quality and premium-request cost, chooses a model, and bills according to the model selected. Paid users receive a ten-percent discount when they use auto selection.

The setting changes the objective, not the inventory

An efficiency setting does not guarantee a cheap model, and intelligence does not pin the most expensive one. The router still estimates what each prompt needs. Two similar requests can therefore have different cost and behavior.

That is reasonable for an individual who wants less model management. It complicates organizational evaluation. A team can no longer attribute a result to one fixed model simply because Copilot was set to auto.

Measure work completed, not prompt price

The cheapest request is not cheaper if it produces a patch that takes longer to repair. The most capable model is wasteful when the task is boilerplate. I would compare tiers using accepted changes, review time, escaped defects, retries, and premium requests per completed task.

The benchmark set should include small transformations, repository navigation, debugging, multi-file changes, and tests written from an existing contract. Average cost without task mix is not useful.

Reproducibility still needs a pinned path

For everyday assistance, changing the selected model is a feature. For an evaluation, regulated workflow, or regression investigation, it is a variable. Record the chosen model where GitHub exposes it, preserve prompts and repository state when policy permits, and pin a model for tests that must be comparable over time.

Administrators should also decide who controls the tier and which models are eligible. A user-visible preference is not the same as a spending policy. Budget alerts and premium-request limits remain necessary because a router optimizes the objective it was given, not the organization’s entire cost model.

I like automatic routing for low-stakes interactive work. I would not use it as evidence that one named model improved productivity unless the selected-model distribution and task mix were part of the result.

Source

GitHub: configure cost and quality in Copilot auto model selection.