Skip to content AI News: GPT-6.2 Astra and Sol are out: Astra gets cheaper, Sol keeps its price →
AI News · Nov 18, 2026 · OpenAI

GPT-6.2 Astra and Sol are out: Astra gets cheaper, Sol keeps its price

OpenAI released GPT-6.2 Astra and GPT-6.2 Sol on November 17. Astra is the model for the hardest projects and now costs 20% less per token than GPT-6 Astra; Sol, the everyday model, keeps GPT-6.1 Sol's price. Both are in ChatGPT Work and Codex on Plus and higher plans, in the API and in GitHub Copilot.

WhatNew models: GPT-6.2 Astra, Sol
WhoPlus and up (Work, Codex), API, Copilot
API priceAstra $8/$40, Sol $2/$10 per 1M
Try it1 prompt
GPT-6.2 Astra and Sol are out: Astra gets cheaper, Sol keeps its price

What happened

OpenAI released GPT-6.2 Astra and GPT-6.2 Sol on November 17, 2026. Its ChatGPT release notes point Sol at everyday coding, writing and multistep workflows, and Astra at the hardest jobs, such as complex code changes or a slide deck built from your template.

Where you can use them

Price

API, per 1M tokensInputCached inputOutput
GPT-6.2 Astra$8$0.40$40
GPT-6 Astra$10$1$50
GPT-6.2 Sol$2$0.10$10
GPT-6.1 Sol$2$0.10$10

Past 272K input tokens the rates rise to $16/$60 for Astra and $4/$15 for Sol. Astra now lists at the same per-token price as Claude Fable 5.2.

The claims

In its announcement, OpenAI says Astra finishes work at less than a third of the cost per task of GPT-6 Astra. Sol, it says, nearly matches Astra on FrontierCode 2.0 at about one-fifth the cost. GitHub's own testing found Sol caught nearly twice as many real issues in code review as GPT-6.1 Sol. OpenAI also launched both with tighter safeguards for higher-risk cybersecurity help.

What it means for you

  1. In ChatGPT Work or Codex: start on Sol. Move a task to Astra after Sol gets it wrong.
  2. On GPT-6.1 Sol in the API: same price, so switch the model ID and rerun your tests.

Plans and Codex limits are in our Codex review; for the cheaper model below Sol, see GPT-6.1 Terra.

Try it

Give Sol a code review before you merge
Act as a code reviewer. Don't edit any file.
Change to review: [branch name, commit range, or paste the diff]
What the change is meant to do: [one or two sentences]

1. List every problem you find, most serious first: file and line, what breaks, and the input that breaks it.
2. Mark each one as a bug, a missing test, or a style note.
3. Skip style notes if there are more than three bugs.
If you can't point to a line, don't report it.

Sources

Weekly

New prompts in your inbox

One email a week: the best new prompts and one short guide. Confirm by email and get the free Prompt Cheat Sheet (PDF). Unsubscribe any time. Privacy policy