Check Copilot policies before GPT-5.6 agents start spending AI credits

GitHub Copilot is now rolling out GPT-5.6 Sol, Terra, and Luna. Confidence level: confirmed for GitHub's Copilot rollout and admin-policy requirement; availability remains gradual by plan and product surface. This is a Copilot operations story, not just another GPT-5.6 launch note, because model access now sits next to usage-based billing and enterprise policy controls.

What changed

GitHub says GPT-5.6 is rolling out in Copilot across Visual Studio Code, Visual Studio, Copilot CLI, GitHub Copilot cloud agent, the Copilot app, github.com, GitHub Mobile, JetBrains, Xcode, and Eclipse.

Sol is aimed at complex reasoning over large codebases and long-running agentic work. Terra is the balanced everyday coding option. Luna is the lightweight, lower-cost option for faster tasks.

Why this is early

The primary signal is GitHub's July 9, 2026 changelog entry. It is official, but the rollout language matters: teams may not see every model in every surface at the same time.

The independent context is that GPT-5.6 became broadly available on the same day. For Copilot users, the practical question is narrower: which plans can use each model, where the picker appears, and whether admins have enabled the policy.

Key takeaways

• Copilot Business and Enterprise admins must enable GPT-5.6 model access in Copilot settings.
• Sol is restricted to Pro+, Max, Business, and Enterprise; Terra and Luna reach Pro and higher.
• The models are billed under GitHub Copilot Usage Based Billing at provider list pricing.
• Rollout is gradual, so absence from the picker is not proof that a plan is ineligible.
• Teams should map Sol to high-value agent work and use Terra or Luna for routine tasks where cost matters.

Availability and access

GitHub says GPT-5.6 Sol will be available to Copilot Pro+, Max, Business, and Enterprise SKUs. GPT-5.6 Terra and Luna will be available to Pro, Pro+, Max, Business, and Enterprise SKUs.

Business and Enterprise administrators need to enable the GPT-5.6 policy before users can select the models. GitHub says the policy is off by default. Developers should also check the exact product surface, because IDE, CLI, mobile, and cloud-agent rollout can lag during a gradual release.

Practical LinkLoot angle

Treat GPT-5.6 in Copilot as a routing decision. Sol should be reserved for work where deeper reasoning, longer context, and agent persistence are worth the credit burn. Terra and Luna are better candidates for everyday completions, smaller fixes, and quick code explanations.

For team workflows, this belongs next to model policy, repository permissions, cost-center budgets, and review rules. If your agents can open pull requests or run cloud sessions, model choice is now part of engineering governance.

For related tooling decisions, see LinkLoot's guide to AI agent tools.

What to verify before you act

• Confirm which Copilot plan each team uses.
• Check whether GPT-5.6 policy access is enabled for Business or Enterprise.
• Review GitHub's current model and request pricing before moving long-running agents to Sol.
• Watch AI credit usage after rollout, especially for cloud agent and CLI sessions.
• Confirm whether your IDE or Copilot surface has received the gradual rollout.

Source check

Confirmed by:

• GitHub's July 9, 2026 changelog says GPT-5.6 Sol, Terra, and Luna are rolling out in Copilot and lists eligible SKUs and product surfaces.
• GitHub's changelog also states that Business and Enterprise admins must enable the GPT-5.6 policy and that billing follows Usage Based Billing at provider list pricing.

Early signal / context:

• Techzine independently reported the broader GPT-5.6 availability on July 9, 2026, which corroborates the model family's public rollout but does not replace GitHub's Copilot-specific access rules.