The September 14, 2026 hands-on evaluation of GPT-6 Astra points to a clear but narrower verdict than the launch-era AGI talk: OpenAI’s model is stronger than GPT-5.6 for some coding, computer-use and multi-step workflows, yet it still makes serious mistakes, requires supervision and can burn through paid usage limits quickly. It is a powerful agentic tool—not demonstrated artificial general intelligence.

The verdict in one minute

GPT-6 Astra is most interesting when the job involves several connected steps: inspecting files, operating software, reviewing code, testing an artifact or coordinating a longer workflow. For routine questions and ordinary chatbot tasks, the practical improvement was much less obvious.

That distinction matters. An agent can perform more actions on your behalf without reliably understanding the whole problem. Astra’s strongest use case is supervised execution, not handing over a project and walking away.

Where Astra beats the previous generation

The clearest comparison comes from demanding technical work. A code-review evaluation reported that GPT-6 Astra found approximately 4% more actionable labeled bugs overall than GPT-5.6 Sol, with a 20% advantage on a harder cross-file subset. Those figures describe that evaluation’s review task; they are not a universal ranking of every kind of programming.

A separate hands-on assessment found Astra identifying a formatting mistake in a GPT-5.6 workflow for a Crimson Desert mod and recommending an ASI format that ultimately worked. That is a useful example of the model acting as an operator: it can inspect an existing process, spot a problem and suggest a workable correction.

Launch demonstrations also show Astra being used for browser and application workflows, software engineering, scientific work and 3D or CAD-style tasks. A successful demonstration, however, says more about what the system can sometimes do than about how reliably it will do it on an unfamiliar project.

The supervision bottleneck

The same hands-on assessment that found useful coding gains also found a game-breaking bug introduced by Astra. Locating the error required hours of high-intelligence prompting. That is the practical fault line running through the entire model: impressive local decisions do not guarantee sound global understanding.

Astra can therefore be a force multiplier for a developer who checks its work. It is a poor fit for the fantasy of an unsupervised digital employee that handles every dependency correctly. In complex projects, review is not a ceremonial final step; it remains part of the workflow.

This is also why the AGI label goes too far. OpenAI’s launch material reports a 99.9% result for GPT-6 on ARC-AGI-3, a benchmark designed around agents solving unfamiliar interactive tasks. That is a notable benchmark claim, but it is attributed to OpenAI rather than presented as an independent measurement. A high score on one benchmark cannot erase observed bugs, prompting requirements and the need for human oversight.

Usage costs: API rates versus plan limits

Watch the practical demonstration of Thinking Level controls and file-based workflows

OpenAI lists standard API pricing of $10 per million input tokens and $50 per million output tokens. These are token-based API rates, not a monthly subscription price for Astra.

The economics become more complicated when reasoning intensity and multiple agents enter the picture. In one hands-on account, maximum-intelligence settings combined with several agents consumed a week’s usage on a $100-per-month Pro 5x plan in roughly one or two hours. That is an individual usage observation, not a universal allowance for every plan or market, but it illustrates the central trade-off: more elaborate work can spend access rapidly.

A practical workflow demonstration shows a Thinking Level control ranging from Light to Ultra and connects ChatGPT Work to local folders for project tasks. Its useful lesson is simple: reserve heavier reasoning for work that genuinely benefits from it, and use less intensive models for routine operations.

Should you use GPT-6 Astra?

Use GPT-6 Astra when the task benefits from persistence, software operation, code review or coordination across multiple steps—and when you can inspect the result. Developers working across several files may see more value than people using an AI mainly for ordinary chat.

The standard API rates also make task selection important. A model that finds more issues or completes a difficult workflow may justify its cost in a high-value engineering task, but sending every small request through the most intensive setting can consume an allowance quickly.

GPT-6 Astra is best understood as a more capable operator that still needs a supervisor. Its advantage is practical and conditional: it can connect more steps, handle more software interactions and outperform GPT-5.6 in selected workflows. The human who defines the task, checks the output and decides when the extra cost is worthwhile remains firmly in the loop.