GPT-6 Astra Is Now Generally Available in GitHub Copilot

GPT-6 Astra, OpenAI's new general-purpose model for long-horizon autonomous coding, is now generally available in GitHub Copilot as of September 4, 2026, according to GitHub's changelog announcement. Copilot Pro+, Max, Business, and Enterprise users can select the model in the picker on every major Copilot surface — from Visual Studio Code and JetBrains IDEs to the coding agent, the command line, github.com, and GitHub Mobile — and GPT-6 Astra is billed at provider list pricing under usage-based billing.

What GPT-6 Astra Is Built For

GPT-6 Astra is OpenAI's latest general-purpose model, with a stated design focus on long-horizon, autonomous coding and agentic tasks — work that stretches across many steps, files, and verification cycles instead of a single quick edit. In practice that means multi-file refactors, bugs that must be reproduced before they can be fixed, and agent sessions that run unsupervised for a while. If you are still building intuition for delegating that kind of work, our practical guide to AI coding agents covers the patterns.

What stood out in GitHub's internal testing was the model's process, not just its output: GPT-6 Astra works from a plan and validates as it executes, runs diagnosis and verification together in batches, and confirms results on its own before declaring a task complete. GitHub reports that this behavior produced stronger results on long-horizon coding tasks while taking fewer steps than earlier OpenAI models.

Treat that claim as vendor-reported. The changelog publishes no benchmark suite, scores, or task set, and the comparison baseline is prior OpenAI models only — for why that framing matters, read why vendor benchmark scores mislead. Nothing in the announcement claims an edge over Claude, Gemini, or any other vendor's models.

Where You Can Use It

GPT-6 Astra is available to Copilot Pro+, Max, Business, and Enterprise users across the ten Copilot surfaces GitHub lists, with a gradual rollout underway.

Which plans get access

Four plans can use GPT-6 Astra: Copilot Pro+, Copilot Max, Copilot Business, and Copilot Enterprise. On the individual plans the model simply appears in the picker; on Business and Enterprise, an administrator's model policy can also gate access, covered below.

Which surfaces it covers

Five of the ten surfaces are integrated development environments (IDEs) or editors; the rest cover the command line, the web, mobile, and autonomous coding:

Category	Surfaces where you can select GPT-6 Astra
IDEs and editors	Visual Studio Code, Visual Studio, JetBrains IDEs, Xcode, Eclipse
Command line	GitHub Copilot CLI
Web	github.com, GitHub Copilot app
Mobile	GitHub Mobile on iOS and Android
Autonomous coding	GitHub Copilot coding agent

That is the complete list from the changelog — wherever you currently pick models in Copilot, GPT-6 Astra is slated to appear there.

Rollout timing

GitHub describes the rollout as gradual and tells users who do not see the model yet to check back soon, per the changelog entry. On Business and Enterprise plans, a missing model can also mean an administrator has restricted it through the model policy rather than a rollout gap.

How GPT-6 Astra Is Billed

GPT-6 Astra is billed at provider list pricing under GitHub Copilot's usage-based billing — that is the entirety of what the changelog says about cost. Two things follow:

• No rates in the announcement. GitHub points to its "pricing for GitHub Copilot models and requests" documentation for the actual numbers, so do not infer GPT-6 Astra's Copilot price from other providers' lists.
• Model choice is a spend decision. Under usage-based billing, switching a team's default model changes the bill, not just the experience. Our GitHub Copilot usage-based billing guide breaks down the mechanics, so we will not repeat them here.

What Business and Enterprise Admins Need to Check

Access to GPT-6 Astra in Copilot Business and Enterprise organizations is controlled through the model policy in Copilot settings, and new models are enabled by default. Under default model enablement, a new model turns on automatically unless an administrator has turned off the global default or explicitly disabled that model.

Model policy state	Effect on GPT-6 Astra
Defaults untouched (typical org)	Enabled automatically
Global default for new models turned off	Not enabled automatically
GPT-6 Astra explicitly disabled	Blocked for the organization

To manage it:

1. Open Copilot settings for the Business or Enterprise organization.
2. Review the model policy, including the default model enablement option.
3. Decide, then act: if GPT-6 Astra should not be selectable, disable it explicitly — silence means on.

The practical consequence is that GPT-6 Astra arrived enabled by default. Organizations with approval processes or budget caps around new models have exactly one lever, the model policy, and no action deadline — the default already applies unless someone changes it.

GPT-6 Astra vs. Claude Opus 5: What's Actually Known

The changelog contains no head-to-head data between GPT-6 Astra and Claude Opus 5. GitHub's only comparison is against prior OpenAI models, where GPT-6 Astra reportedly completes long-horizon coding tasks more successfully and in fewer steps. For Anthropic's side of the ledger, see our Claude Opus 5 pricing and benchmarks guide; stitching the two vendor-reported stories together is the closest thing to a comparison that exists today.

Question	Confirmed	Not published
Long-horizon coding	Stronger than prior OpenAI models, in fewer steps (GitHub internal testing)	Benchmark suites and scores
Versus Claude Opus 5 or Gemini	—	Any head-to-head result
Cost inside Copilot	Provider list pricing under usage-based billing	The per-model rates (in GitHub's pricing docs)
Outside Copilot (OpenRouter, Vercel AI Gateway)	—	Not mentioned in the changelog at all

Context worth knowing: Astra lands in a crowded picker. Claude Fable 5.1 went generally available in Copilot on September 1, Gemini 3.8 Flash arrived September 3 (pricing and migration details), and GitHub flagged upcoming deprecation of selected Copilot models that same day. A default you chose a month ago may no longer match today's menu.

What to Do Next

On Copilot Pro+ or Max

1. Open the model picker in your usual surface and select GPT-6 Astra.
2. Test it on a genuinely long task — a multi-file refactor or a reproduce-then-fix bug — because long-horizon work is what the model is built for; the announcement supports no claims about short edits either way.
3. If it is missing, wait. The rollout is gradual and there is nothing to configure on individual plans.

Administering Copilot Business or Enterprise

1. Decide whether a new OpenAI flagship should be selectable, because default enablement puts GPT-6 Astra in front of everyone as the rollout completes.
2. Disable it explicitly in the model policy in Copilot settings if the answer is no.
3. Announce it if the answer is yes — otherwise the model will quietly appear in people's pickers.

If cost is the constraint

Check what a flagship model does to spend before standardizing on it, since usage-based billing at list pricing makes model choice a line item, not a preference. And because the changelog says nothing about GPT-6 Astra outside GitHub Copilot — for example on OpenRouter or the Vercel AI Gateway — verify with those providers directly rather than assuming Copilot's terms transfer.

The short version: GPT-6 Astra's pitch is process quality on long, unsupervised runs — plan, verify, and confirm before declaring a task done. If your Copilot usage is mostly short completions and quick questions, the announcement offers no evidence either way; if you live in agent sessions, GPT-6 Astra is the model to test head-to-head against your current default this week.