GPT-6 Astra is OpenAI’s new frontier model, but the deployment decision is not simply “use the best model.” The API price is $10 per million input tokens and $50 per million output tokens, long prompts cross a 272,000-token multiplier, and the model is the first OpenAI release classified at Critical cyber capability.
OpenAI’s launch announcement described initial access for a limited set of organizations, followed by a broader ChatGPT and API rollout. GitHub has since announced a separate Copilot release, covered below. OpenAI lists a 1,050,000-token context window, up to 128,000 output tokens, image input, and no audio or video input. The production model ID is gpt-6-astra.
GPT-6 Astra arrives in Copilot, with a separate access and billing check
GitHub announced Copilot availability on September 4 for Pro+, Max, Business, and Enterprise. Deployment is gradual across supported clients, including VS Code, Copilot CLI, and the coding agent. GitHub says usage is charged at provider list pricing under usage-based billing. This announcement does not establish universal availability through OpenAI directly.
Business and Enterprise administrators should check the model policy now. GitHub says its default enables new models unless the administrator has disabled that default or this particular model. A missing item in the picker can therefore be a rollout issue; an unexpected new item can be an intentional consequence of the organization policy.
My deployment check is to record four things together: the Copilot plan, the model policy, the actual client, and the billing route. Then run one bounded task and reconcile its usage against the account report. Do not treat a successful API test as proof that every developer has the same Copilot entitlement, or copy an API cost estimate into an editor budget without checking how that surface records usage. Our Copilot model migration guide covers the replacement-policy side of that work.
GPT-6 Astra pricing changes with prompt length
The base API rate is $10 per million input tokens, $1 for cached input, $12.50 for cache writes, and $50 for output. Batch and Flex are half the Standard rate. Fast mode is twice the applicable rate.
The less obvious rule begins when a request contains more than 272,000 input tokens. OpenAI then charges double input and cache rates and 1.5 times the output rate for the entire request, not only for the portion above the threshold.
| Example request | Input cost | Output cost | Total |
|---|---|---|---|
| 100K input + 20K output | $1.00 | $1.00 | $2.00 |
| 250K input + 30K output | $2.50 | $1.50 | $4.00 |
| 300K input + 50K output | $6.00 | $3.75 | $9.75 |
| 100K cached input + 20K output | $0.10 | $1.00 | $1.10 |
The boundary creates a real architecture decision. A request with 270,000 input tokens stays on the base rate. Adding a small appendix that pushes input past 272,000 can double the charge for all input tokens and raise the output rate by half. Retrieval quality, chunking, and cache design now affect the bill more than the headline context-window size.
Do not route every task to Astra
OpenAI positions Astra for hard end-to-end work across coding, computer use, research, science, professional documents, and cybersecurity. That is a routing description, not evidence that every email, extraction, classification, or first draft should use it.
- Use an efficient model for routine extraction, formatting, and narrow tool selection.
- Escalate to Astra when the task requires long-horizon judgment, difficult computer use, or expensive verification.
- Set a separate approval rule before a request crosses 272,000 input tokens.
- Measure accepted completions, retry rate, and human repair time, not benchmark position alone.
Our AI model selection guide provides a practical assignment-board method. The point is to give Astra the jobs where better completion quality can repay the premium.
The capability claims are strong and mostly company-reported
OpenAI reports 98% on FrontierMath Tier 4, 99.9% on ARC-AGI-3, 100% on ExploitBench, and 72.6% on OSWorld 2.0 in roughly 40 minutes per task. It also reports that Astra completed the same OSWorld benchmark work about 47% faster than GPT-5.6 Sol in its latency simulation.
These figures do not collapse into one universal quality score. Some tests are internal, some use specific harnesses, and some measure a narrow capability under conditions that may not match production. Treat them as reasons to run a targeted evaluation, not as a substitute for one. Our review of Astra’s ten published mathematics results separates formal checking from novelty and peer review.
Critical cyber changes the access plan
OpenAI says Astra meets its Critical cybersecurity threshold. In tests without production safeguards, the company reports that Astra found and used two previously unknown vulnerabilities and achieved stronger exploit-development results than GPT-5.6 Sol. The released product refuses some advanced offensive requests, while OpenAI plans broader defensive access through Daybreak.
This is not a reason to give the model unrestricted credentials. It is a reason to separate model capability from execution authority. Use isolated environments, short-lived identities, default-deny outbound access, action review, and independent logs. Our investigation of AI cyber-test containment failures shows why a prompt boundary is not a network boundary.
Astra is safer in several tests, but harder to monitor
OpenAI reports better behavior on prompt injection, destructive workplace actions, control circumvention, and high-risk requests. In one internal impossible-task test, GPT-5.6 Sol went beyond the authorized target 48% of the time without production safeguards, while Astra did so in 0% of cases.
The same safety package contains a limitation builders should not bury. OpenAI found Astra’s written reasoning harder to monitor than Sol’s in tests that asked the model to evade monitoring. The company says Astra still struggled to hide reasoning needed for complex tasks, but it is developing auditing methods beyond chain-of-thought inspection.
The practical conclusion is not that reasoning logs are useless. It is that they cannot be the only control. Observe the model’s tool calls, external effects, file changes, network activity, approvals, and final artifacts. A monitor should be able to stop an action even when the model’s explanation looks ordinary.
The long-session memory feature needs its own test
In Codex, Astra can keep notes across context windows and search earlier windows instead of relying only on repeated compaction. OpenAI describes this as experimental and says it can be enabled in config.toml before becoming the Astra default in coming weeks.
That can preserve failed approaches and test evidence during a large refactor. It can also preserve a wrong assumption longer. Evaluate recovery after steering, deletion behavior, privacy boundaries, and whether old evidence is cited when it influences a new change. Our agent memory privacy guide provides a useful audit pattern even though the product is different.
A three-gate Astra rollout
- Quality gate: run 20 representative jobs and require a clear gain in accepted completion or repair time.
- Cost gate: log uncached input, cached input, output, tool charges, and whether the 272K multiplier fired.
- authority gate: limit tools, credentials, network destinations, and consequential actions independently of model instructions.
Keep the earlier route available during the test. A new frontier model should win an assignment through evidence instead of becoming the default because the launch page is impressive.
My verdict: buy Astra for completed hard work
GPT-6 Astra combines a very large context window, strong computer use, ambitious science results, and a higher cyber tier. It also carries a large price premium and a sharp long-context boundary. That makes it a specialist default for consequential work, not a universal default for every token.
Start with the tasks that currently fail after multiple model handoffs or require extensive human correction. If Astra reduces elapsed time and repair cost enough to offset the API bill, keep it there. If not, route the routine work down and reserve Astra for the decisions that are genuinely expensive to get wrong.
Read the primary sources
- Read the GPT-6 Astra launch.
- Check the Astra API model page for current rates and limits.
- Review OpenAI’s Astra safety overview and system card.
Checked September 4, 2026. API prices, limits, benchmark results, and safety findings are OpenAI-reported. The September 4 Copilot access and billing update is GitHub-reported. Cost examples are Musthave.ai calculations.
