GitHub Adds GPT-5.6 Models To Copilot
GitHub said on July 9, 2026 that OpenAI's GPT-5.6 Sol, Terra, and Luna are rolling into GitHub Copilot across IDE, CLI, mobile, cloud-agent, and web surfaces. The practical change is model routing inside a coding platform teams already govern: Sol is framed for complex codebase reasoning and long-running agentic work, Terra for everyday interactive and agentic coding, and Luna for lower-cost smaller tasks. GitHub says Copilot Business and Enterprise administrators must enable the GPT-5.6 policy before users can select the models, so the rollout is tied to existing enterprise controls rather than unmanaged model switching.
For practitioners
GitHub's rollout turns GPT-5.6 from a model-launch headline into an operational developer-tool choice. For teams already standardizing on Copilot, the useful decision is not simply whether the newest OpenAI model is available, but which coding jobs should be routed to higher-reasoning, balanced, or lower-cost model tiers inside existing IDE, CLI, mobile, and github.com workflows.
What happened
GitHub's July 9 changelog says OpenAI's GPT-5.6 Sol, Terra, and Luna are rolling out in GitHub Copilot. GitHub describes Sol as the highest-reasoning option for complex codebase work and demanding long-running agentic tasks, Terra as the balanced everyday model, and Luna as the lightweight lower-cost option. The listed surfaces include VS Code, Visual Studio, Copilot CLI, the Copilot cloud agent, the Copilot app, github.com, GitHub Mobile, JetBrains, Xcode, and Eclipse.
Technical context
OpenAI's launch material positions GPT-5.6 as a three-tier family, with Sol, Terra, and Luna carrying different capability and price profiles. GitHub's supported-models documentation adds the platform detail that these models appear as Copilot options rather than separate API-only choices. That matters because model selection now intersects with repository context, agentic coding sessions, usage-based billing, and organization-level model policies.
What to watch
The main implementation question is whether teams create explicit routing guidance. Sol is the likely fit for repository-scale reasoning, migration planning, difficult debugging, and long-running agent sessions. Terra fits day-to-day coding assistance where quality and latency both matter. Luna is more appropriate for lightweight edits, explanations, and high-volume assistance where cost control is more important than peak reasoning.
Key Points
- 1GitHub says GPT-5.6 Sol, Terra, and Luna are rolling into Copilot across IDEs, mobile, CLI, and github.com.
- 2Copilot Business and Enterprise administrators must enable the GPT-5.6 model policy before users can select the new models.
- 3The rollout makes frontier coding models a governed platform choice, not only a direct OpenAI API decision.
Scoring Rationale
This is a notable developer-platform rollout because GPT-5.6 becomes selectable inside GitHub Copilot across many coding surfaces. It is below a base-model launch in impact, but it directly affects enterprise AI coding workflows, admin policy, and model-cost routing.
Sources
Public references used for this report.
Practice interview problems based on real data
1,625 SQL & Python problems across 15 industry datasets — the exact type of data you work with.
Try 250 free problems
