GitHub Copilot has added two new GPT‑6.2 models—Astra and Sol—to its roster, making them generally available to Pro+, Max, Business, and Enterprise subscriptions. Both are positioned for agentic coding and code‑review tasks, and early testing reports higher issue detection with fewer tokens than prior GPT‑6 variants. This shift directly touches AI engineers, platform teams, DevOps/SRE, and security practitioners who embed Copilot into development pipelines.
What changed: GPT‑6.2 models are now selectable
The new models can be chosen through the model picker in a range of environments, including Visual Studio Code, Visual Studio, JetBrains IDEs, Xcode, Eclipse, the Copilot CLI, the GitHub Copilot app, and mobile clients. Rollout is gradual, so visibility may vary initially. Administrators on Enterprise and Business plans can control model exposure via the model policy in Copilot settings; by default, the models are enabled unless explicitly disabled.
Why the change matters for engineering workflows
Early testing indicates that Astra catches more code‑review issues than the previous GPT‑6 Astra while using noticeably fewer tokens, and Sol detects nearly twice as many real issues as GPT‑6.1 Sol with comparable accuracy. For teams that rely on AI‑assisted review, this could translate into higher defect detection without proportionally increasing usage‑based costs. The token efficiency also benefits any automated CI/CD step that invokes Copilot, potentially lowering the billable consumption under the provider’s usage‑based pricing.
Operational and policy implications
Integrating the new models requires updating tooling configurations to reference gpt-6.2-astr or gpt-6.2-sol (actual identifiers are not disclosed in the source). Teams should verify that their CI pipelines, IDE extensions, and custom agents are set to the desired model, especially if they have cost‑control policies tied to token usage. Because model enablement can be toggled at the organization level, engineers should coordinate with administrators to ensure consistent availability across development environments.
Related CloudNinjas coverage: AI engineering.
What This Means For Practitioners
- Validate the new models in a sandbox branch before adopting them in production pipelines.
- Monitor token consumption reports to confirm the claimed efficiency gains.
- Review Copilot model policies to align model exposure with security and cost governance.
- Plan for a phased rollout, acknowledging that some users may not see the models immediately.


