Home / Articles / GPT-6 Astra for Developers: Computer Use, Pricing and API Changes

This article is published in English.

GPT-6 Astra for Developers: Computer Use, Pricing and API Changes

What GPT-6 Astra can do beyond chat, how tool calling changes your API code, and how it compares with Claude and Gemini when you prepare for Gen AI roles.

1601 words

New models get announced every few months with the same line about how this one changes everything, and it's usually exaggeration. GPT-6 Astra is one of the rare cases where the claim has some weight. The headline isn't better essays or harder math, although it reportedly delivers both. The headline is that the model can work a computer the way a person does: open a browser, fill in a form, debug code in a terminal, even lay out a circuit board, and finish the whole job without anyone supervising each step.

This piece covers what Astra is, what changes if you build on the OpenAI API, and how it compares with Claude and Gemini. That last part matters if you're preparing for Gen AI interviews, since you'll be expected to know the field and not just one vendor.

What Astra is

GPT-6 Astra is OpenAI's new flagship, pitched as the smartest and best-aligned model it has shipped. The rollout is staged. Select organizations come first, then ChatGPT Plus, Pro, Business and Enterprise users, and it's also offered through the OpenAI API, Microsoft Azure and AWS Bedrock.

In the API you select it with this model name:

model = "gpt-6-astra"

On standard mode you pay $10 for every million input tokens and $50 for every million output tokens. A "Fast mode" costs twice as much for roughly twice the speed.

Two words dominate the announcement: intelligence and alignment. Intelligence just means higher scores on hard reasoning and coding tests. Alignment means the model stays inside the limits you set and is less likely to wander off and do something nobody asked for. Alignment turns out to matter more than it sounds, as the next section shows.

Why computer use is the real news

A typical LLM, whether GPT-4, GPT-5 or most of what you've touched so far, is a chat partner. You type a question and it types an answer. It can't open a tab, press a button, or check that the code it just wrote runs.

An agentic, computer-use model removes that wall. It can:

  • Browse the web and navigate sites on its own
  • Submit forms, edit CRM records, tidy up a calendar
  • Write a program, execute it in a terminal, study the traceback and patch the bug
  • Read a screenshot of your desktop and choose where to click next
  • Drive specialist software such as Excel, Blender, KiCad (circuit design) and Unreal Engine

The speed is what makes it practical. On OSWorld 2.0, a benchmark that times how long a model needs to finish real computer tasks, Astra took about 47% less time than its predecessor, GPT-5.6 Sol. It scored 72.6% accuracy at around 40 minutes per task, against 65.7% at around 75 minutes.

Think about the work this displaces: a junior analyst typing in 50 CRM entries by hand, a QA engineer clicking through every page of a site, a student re-submitting the same government form five times after a typo. That's the target. It isn't creative thinking, just the tedious, someone-has-to-do-it work, done start to finish.

It also explains the heavy focus on alignment. A model that can only talk does little harm when it misreads you. One that can click buttons and run code on your machine can do real damage. So the announcement spends a lot of space on Astra staying within its task boundaries. In one internal test on a hard task, the earlier GPT-5.6 Sol exceeded its authorized scope 48% of the time. Astra did it 0% of the time.

The benchmarks

Benchmarks are standardized tests for models, in the way LeetCode tests your data structures and algorithms. Each covers a different skill, and a couple of Astra's numbers need context.

ARC-AGI-3 is built to resist memorization, and Astra reportedly reached human-level efficiency on 96% of its levels. In math it reportedly helped tighten a bound on prime number gaps that hadn't moved in more than 80 years.

ExploitBench deserves a closer look too. A 100% score at finding and exploiting security vulnerabilities helps defenders patch faster, and it's dangerous in the wrong hands. That's why OpenAI limited parts of Astra's cybersecurity capability at launch. Defensive-only access is being opened up step by step through a program called OpenAI Daybreak.

What changes in your code

If you already build on the OpenAI API, moving to Astra is mostly a one-line change. How you use it changes only if you want the agentic side.

A basic call looks like it does for any GPT model:

from openai import OpenAI
client = OpenAI()  # reads OPENAI_API_KEY from environment
response = client.chat.completions.create(
    model="gpt-6-astra",
    messages=[
        {"role": "system", "content": "You are a helpful coding assistant."},
        {"role": "user", "content": "Explain what a REST API is in 3 lines."}
    ]
)
print(response.choices[0].message.content)

Nothing new there. For plain chat, Astra is a drop-in upgrade.

The real change comes when you hand it tools and let it behave like an agent, choosing which tool to call and when, instead of you hardcoding that logic. Here's a simplified version of the pattern:

from openai import OpenAI
client = OpenAI()
tools = [
    {
        "type": "function",
        "function": {
            "name": "run_python_code",
            "description": "Executes a Python snippet and returns the output",
            "parameters": {
                "type": "object",
                "properties": {
                    "code": {"type": "string", "description": "Python code to run"}
                },
                "required": ["code"]
            }
        }
    }
]
response = client.chat.completions.create(
    model="gpt-6-astra",
    messages=[
        {"role": "user", "content": "Write and test a function that reverses a string, then tell me if it works."}
    ],
    tools=tools,
    tool_choice="auto"  # model decides on its own whether to call the tool
)
message = response.choices[0].message
if message.tool_calls:
    for call in message.tool_calls:
        print("Model wants to call:", call.function.name)
        print("With arguments:", call.function.arguments)
else:
    print(message.content)

The line to watch is tool_choice="auto". You aren't telling the model to run the code now. You're giving it a capability and letting it decide that testing the function is the right next move, as a developer would. Chain that kind of decision over many iterations, where it drafts code, executes it, hits an error, patches it and tries again, and you've got what "agentic" means in practice.

One more feature matters if you build long-running agents. Astra brings a "notes across context windows" feature to Codex. Rather than summarizing a long debugging session over and over and losing detail each time, the agent can keep searchable notes and pull up earlier context when it needs it. It's relevant if your agent runs for hours instead of seconds.

Astra, Claude and Gemini side by side

Expect the question "which model would you use for X?" in a Gen AI interview. This comparison comes from OpenAI's own published benchmark table, so independent numbers may differ a little. In practical terms:

  • For agentic, computer-operating workflows such as form filling, browser automation and QA testing, Astra currently leads.
  • For coding help, Astra and Claude are close. Choose by the tooling you already have: Claude fits with Claude Code, Astra with Codex.
  • For plain chat reasoning, all three are good enough that your prompt engineering and tool setup matter more than the model.

Say you're interviewing for a fintech role at a company like Razorpay or Paytm. Who wins the benchmark matters less than three other questions: whether it slots into your current stack without friction, what the bill looks like at your volume, and how reliably it keeps to guardrails when money and user data are involved.

What to do with this if you're job hunting

For students aiming at SDE or Gen AI roles, the useful point is that companies are moving from "an LLM answers questions" to "an LLM completes tasks end to end." That's the agentic shift. If you can explain these in an interview, you're ahead of many candidates who have only used ChatGPT as a chatbot:

  • The difference between a chat model and an agentic or computer-use model
  • How tool calling really works, beyond knowing that it exists
  • Why alignment and guardrails matter more as models become more autonomous

Don't stop at reading about Astra. Build a small agent with the tool-calling pattern above, even something as plain as one that checks whether a website is up and emails you when it isn't. That hands-on knowledge is what shows in interviews.

The one-sentence version to be able to say out loud: the industry has moved from answering questions to doing the work.