GPT-6.1 Sol in GitHub Copilot: plan, policy and usage checks
The model rolls out to named paid plans. Check the model picker, administrator policy and usage billing before troubleshooting missing access.
In brief
GitHub announced GPT-6.1 Sol for Copilot Pro+, Max, Business and Enterprise, with gradual rollout. If you do not see it, check the plan, supported client and organization model policy first.
This avoids treating an account entitlement or administrator restriction as a broken IDE installation.
Find the access condition
Use the official supported-client and plan list. Business and Enterprise model policy can control availability. Do not reinstall an IDE repeatedly when the account or administrator setting is the real limit.
Check the cost before a long run
The announcement points to usage-based model pricing. Read the current Copilot billing documentation and usage view instead of assuming another model’s multiplier or an older allowance applies. Track real task usage and retries.
Evaluate a bounded code change
Provide a reproducible bug, expected behaviour and the project’s relevant checks. Inspect the diff and output, including tests not run. A new model appearing in the picker does not validate the generated change or authorize publishing it.
Before you act
Current plan and billing rules can change. The provider’s efficiency statement is not a guaranteed saving or a test performed on your codebase.
What to do next
- Check your Copilot plan and the client’s current model picker.
- Confirm organization model policy if the account is managed.
- Review current usage billing, then test one bounded code task and its actual checks.
