OpenAI introduced GPT-6.2 Astra and Sol on 17 November 2026. Sol is positioned for regular professional work and Astra for harder tasks. For a business, the useful distinction is how much checking and rework each model leaves behind.

A quick draft can still be expensive if a reviewer has to rebuild it. Before choosing a model for your team, test both on the same work and measure the time it takes to get to an output you can actually use.

Read OpenAI’s launch announcement

Availability at launch

OpenAI lists Plus, Pro, Enterprise and Edu for the launch in ChatGPT Work and Codex, with both models also offered through the API. Check your workspace for access and administrator controls. OpenAI release notes.

Header image: AI-generated editorial illustration for ADJ Systems.

What Astra and Sol are designed to do

OpenAI presents Sol as the everyday choice for work such as writing, analysis and coding. It presents Astra as the higher-capability option for harder projects. Both names refer to models. The product you use them in determines which tools and files they can access.

Start with Sol when the brief is clear

Try it on a structured task such as turning approved meeting notes into an internal action list. Define the format, give it the source material and ask it to mark decisions that still need confirmation.

Try Astra when the review load is high

Test it on a task that requires reconciling multiple sources, explaining conflicting figures or preserving a complex workbook. Give it the same inputs and measure how much additional work the reviewer has to do.

How to compare the models on your own work

Start with a monthly operations pack. Give each model the same anonymised sales export, inventory notes and definition of the metrics. Ask for a one-page summary and a short list of anomalies. Set a rule that each figure must trace back to a named sheet or row, and keep an answer key for the figures that matter most.

1. Use the same brief

Keep the prompt, sample files, tools and output format consistent. Include a messy example with a missing value or a mismatch between sources.

2. Review against the source

Check the totals, units and assumptions. Record unsupported statements and measure editing time. Mark a critical error as a failed task even if the draft reads well.

3. Compare accepted outputs

Compare the share of outputs a reviewer can approve, how long review took and your actual usage cost or plan limits. Repeat on a few examples before making a choice.

See OpenAI’s comparison examples, including a workbook and slide deck

Watch OpenAI’s paper-lamp design video under From CAD to a paper lamp. It follows a single Astra design from reference photos through revisions to a physical prototype.

What benchmarks can tell you

OpenAI publishes evaluation results and example outputs alongside the launch. They show how the models performed on those tasks under those conditions. A clean benchmark spreadsheet can be quite different from a workbook with local naming conventions, missing rows and undocumented formulas. Your own acceptance criteria should decide whether any improvement matters.

What New Zealand businesses can do now

Pick one repeatable job, set a review limit and run a small trial with approved material. If Sol meets the standard, use it for similar work. If Astra consistently reduces review time or errors on complex cases, reserve it for those jobs. Keep a person responsible for approvals and check that your workspace settings allow the files you intend to use.

Back to the 22 November Weekly Highlights.

Sources