Copilot Auto model selection now available in Visual Studio Code

[nhu-do]

Introducing Copilot Auto model selection 🎊

Not sure which model to use? Auto’s got you covered! 🎉

Today, we’re introducing Auto within VS Code’s GitHub Copilot Chat model picker, rolling out to all Copilot Free, Pro, and Pro+ plans, coming soon to Copilot Enterprise and Copilot Business.

When you select Auto, you’ll be routed to the best available model at any given time. Auto brings you:

• Discounted premium request multipliers for Paid Copilot subscribers
• A mix of premium language models
• Transparency around which model is used and what it costs
• Models that are available based on your subscription and model policies

Auto currently optimizes for model availability and reliability. You’ll still get access to premium models like Claude Sonnet 4, GPT-5, and others that perform well on complex tasks. At any point, you can move off of Auto onto your preferred model.

What’s next? 🚀

We’re just getting started on making your experience better every day. Over time, Auto will factor in your specific task, choosing models that are best for your needs based on a set of criteria. We’ll also expand Auto’s availability to more of your favorite IDEs.

Share your feedback ❤️

Join in the comments below to share your feedback on Auto.

Learn more

• About auto model selection
• VS Code August release notes

[VictorMoni]

Nice 😎👌

[KailashSatkuri-warangal]

Nice ,This is a great addition 👏. Auto model selection will definitely simplify the experience, especially for those of us switching between multiple tasks in VS Code.

Some feedback and suggestions for what could come next:

Task-aware routing: would be amazing if Auto could detect context (e.g., debugging, refactoring, writing docs) and pick the model best suited for that workflow.

Customizable preferences: an option to set priorities (e.g., “favor speed” vs. “favor reasoning depth”) could give users more control without manual switching.

Usage insights: a simple dashboard showing which models Auto routed to, how often, and the impact on performance/cost.

Broader IDE support: JetBrains and Neovim would be high on my wish list.

[nhu-do]

Thanks for the great suggestions @KailashSatkuri-warangal!

Task aware routing is currently in progress, we want to get to a point where Auto not only gives you the most available model with the least rate limits, but also models that are best suited for your task.

Keep an eye out on the space, and please continue to share your feedback! Thank you.

[ClineCrowstarTruckTTRV]

please i need a someone to learn from

[Aaisan123]

Thanks for the tip!

…

On Mon, 15 Sept, 2025, 11:29 am Satkuri Kailash, ***@***.***> wrote: Nice ,This is a great addition 👏. Auto model selection will definitely simplify the experience, especially for those of us switching between multiple tasks in VS Code. Some feedback and suggestions for what could come next: Task-aware routing: would be amazing if Auto could detect context (e.g., debugging, refactoring, writing docs) and pick the model best suited for that workflow. Customizable preferences: an option to set priorities (e.g., “favor speed” vs. “favor reasoning depth”) could give users more control without manual switching. Usage insights: a simple dashboard showing which models Auto routed to, how often, and the impact on performance/cost. Broader IDE support: JetBrains and Neovim would be high on my wish list. — Reply to this email directly, view it on GitHub <#173188 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BXKIEMYCZBJ3B64GJBH73ST3SZITZAVCNFSM6AAAAACGIH7OS2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTINBQGAYDGMY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.*** com>

[minhdient49-tech]

Trương Minh Điền

[jennaclarke875]

Nice, thanks for this.