Sol and Ultrafast Rumor Follow-up: What DevDay Confirmed

September 29: confirmed release and remaining access limits

OpenAI now identifies the new model as GPT-6.1 Sol, with API identifier gpt-6.1-sol. Its September 29 announcement lists access in ChatGPT Work and Codex for Plus, Pro, Business, Enterprise and Edu, as well as the API. It explicitly says the model is not yet available in Chat. That narrows the earlier access speculation: a successor launch does not establish the predicted Chat rollout. Official model announcement.

The announced standard API rates are $2 per million input tokens, $0.10 per million cached input tokens and $10 per million output tokens. These are the stated standard rates, not a quote for an Ultrafast request. OpenAI describes improved coding, computer-use and professional-task capability; we have not independently tested those claims. Pricing and availability.

The DevDay recap separately lists GPT-6 Astra Ultrafast as available in the API and in Work and Codex on Pro 500 and Enterprise plans. GPT-6.1 Sol Ultrafast is coming soon. For Astra Ultrafast, the recap cites up to 300 tokens per second in Codex, not the earlier 750-token rumor. Treat these as provider statements with model and interface labels attached, not measured results from DualView. Official DevDay recap.

For readers, the practical change is a new model to evaluate where documented access exists. Keep the announced model version, interface and speed tier together when planning a test. The earlier public claim contained several separable predictions; confirmation of one announcement does not authenticate the original image or prove every prediction. This update does not settle the separate GPT-6.1 Astra delay report. Announcement context.

September 29 follow-up: AP reports an Astra delay

AP reports that OpenAI delayed GPT-6.1 Astra over security concerns, citing a statement from safety-systems head Saachi Jain. Its September 29 report says the Journal broke the story. We read the indexed AP report through search; direct page retrieval failed. This adds attributed provider comment, not a new release date. Public account citing WSJ AP delay report (indexed text)

The reported model is GPT-6.1 Astra. It is not the GPT-6 Sol model named in the earlier Chat rumor, nor the GPT-5.6 Sol model attached to the official Ultrafast preview. Our reading is therefore narrow: the report introduces a separate release concern, but supplies no confirmation or cancellation of the specific Sol-in-Chat and wider-Ultrafast claims discussed below. It also does not establish removal of the existing GPT-6 Astra service. Public account citing WSJ

For someone planning a model evaluation, keep those questions on separate lines: which model exists, which product exposes it, and which speed tier is offered to the account. A claim about an unreleased successor should not silently change a working endpoint’s status. Check subsequent provider documentation and the conference announcements before updating access assumptions. We have not inferred a replacement date, new performance figures or an explanation beyond the attributed report. Public account citing WSJ

Our earlier update relied on a September 28 Reddit account describing the release as scrapped. The newer source uses delay, so that is the wording used here. The Journal original remains inaccessible to this review. We have not established whether the two reports describe identical plans or obtained a primary statement directly; readers should not infer permanent cancellation from the earlier wording. AP report; earlier public account.

Separate the model, speed tier and access claim

What the public rumor actually says

The accessible headline places two ideas together: Ultrafast around 750 tokens per second and GPT-6 Sol in Chat. It does not supply a verified technical relationship between them. Public discussion.

The discussion contains conflicting interpretations of what Chat means and whether the information deserves to be called a leak. These reactions establish neither access nor a timetable. We are reporting a public claim that exists, not vouching for the poster’s access to inside information. The fetched page showed a relative age; September 27 is our observation date, not an independently authenticated timestamp for an original leak. Public discussion.

That limited provenance is relevant even when the possible impact is large. A repost can preserve a genuine signal, misunderstand an announcement, or combine guesses with existing facts. Without an authenticated origin, the report cannot distinguish those explanations. Treat the claim as a question to investigate. Repetition across social accounts would add reach, but would not by itself add a second source with independent knowledge.

What OpenAI has already put on the record

The official Sol and Luna announcement lists GPT-6 Sol access through Work, Codex and the API, and says the models were not yet available in Chat in that announcement. Official Sol announcement.

This gives the rumor a specific interpretation: an additional interface rollout, rather than the first existence of Sol. The announcement is the dated baseline we checked, not proof that every account’s present interface is identical. A staged rollout or later change would need its own supporting record. The public rumor alone cannot resolve account-level availability.

For readers, the distinction prevents a misleading new-model headline. You can ask whether an interface would make a model easier to use without assuming its underlying behavior has changed. Keep four fields separate in your notes: model identity, interface, access status and observation date. An update to one field should not silently overwrite the other three. This also makes a later correction precise: the access prediction might fail while the existing model remains real.

Why the Ultrafast number needs its own model label

OpenAI’s August 13 announcement describes a limited GPT-5.6 Sol preview powered by Cerebras, with up to 750 output tokens per second and up to 14 times Standard processing speed. Those are vendor claims for that stated version. Official Ultrafast preview.

The overlap between an older published number and a new rumor does not establish a new combination. A future announcement could extend a service tier, change which model it serves, or say something entirely different. Until the model and tier are explicitly linked, there is no basis here to write a GPT-6 Sol speed specification. Nor have we independently timed the earlier preview.

In general, output throughput describes only one part of a language-model interaction. A user also waits for processing before the response starts, possible reasoning, tool requests and any corrections after the first answer. A quickly streamed but unusable response can require another attempt. This is why a speed headline should prompt a targeted evaluation rather than an automatic conclusion about the total time needed to finish a task.

Why broader access could matter if the rumor is true

The potential impact comes from reducing friction in reaching a particular language model. That is an editorial interpretation of the rumor, not a prediction that the rollout will happen.

Consider a writer who wants to revise a brief through a short conversation. A model exposed in the interface they already use could reduce switching between contexts. An engineer evaluating the same model through an API might care much less about that interface change. Both could be using the same underlying model while experiencing a different practical benefit. This makes the audience for an access update narrower and clearer than a claim of universal model superiority.

A speed-tier change would raise a different decision. A person making repeated small revisions may value responsiveness, while someone reviewing a difficult answer may spend more time checking its content than waiting for text. Neither case can be settled by the rumor’s number alone. The useful follow-up is to identify the actual bottleneck in a representative task, then see whether a documented change addresses it.

How to evaluate a later announcement without mixing claims

Keep the access question and the performance question in separate rows of any future comparison. Both may matter, but they require different evidence.

For access, record the named model, account tier, region, interface and date on which the feature appears. For performance, use the same task and a clearly described setup. Distinguish time until the first visible response from time until an acceptable answer is ready. If tools are involved, record their contribution instead of crediting every delay or improvement to the language model. This is a proposed evaluation method; it is not a description of tests conducted for this report.

For answer quality, preserve the prompt and outputs and judge them against the original requirements. A polished response can still omit a requested constraint. A shorter answer can be more useful than a longer one, so token count alone is an unsuitable success criterion. Repeat representative tasks before drawing a broad conclusion, and keep any measured result separate from provider demonstrations or social claims.

What would confirm, narrow or disprove this report

The official DevDay page gives September 29, 2026 as the event date. That makes it a concrete follow-up point; it does not certify the contents of an alleged leak. Official event page.

A clear confirmation would name the model, the interface receiving it and the availability conditions. A separate technical statement would be needed to attach a speed tier to a specific version. If an announcement discusses only one of those elements, only that part of the rumor should be marked confirmed. Silence at an event is not proof that a feature can never exist, but it would leave the event-specific prediction unsupported.

We will preserve this report’s original date when adding a visible correction or update. The record should show what was claimed, what could be checked at the time and what later evidence changed. For now, the reader decision is straightforward: watch the access details and exact version names, while keeping existing working arrangements intact. There is no verified new specification, subscription entitlement or independently measured speed result in this rumor report.

FAQ