OpenAI will likely ship "one or two new models" before the end of 2026, but the big upgrade it is working on still needs alignment work, according to a report by The Information that The Decoder summarized on October 14, 2026. The report also says the next flagship uses the same looped transformer technique as Astra, which complicates safety monitoring. OpenAI has not confirmed any of this in the sources we could find, so this post is a claimed-versus-verified breakdown.
Where useful, we link our earlier explainers: what recurrent depth is, the Astra chain-of-thought monitoring story, and OpenAI's chief scientist on alignment.
Quick reference
| Claim | Source | Status |
|---|---|---|
| OpenAI likely ships one or two new models by end of 2026 | The Information, citing employees, via The Decoder | Reported, unconfirmed |
| The "major upgraded model" may not be one of them | Same | Reported, unclear |
| Flagship needs alignment work and better testing infrastructure | Same | Reported |
| Flagship uses looped transformers like Astra | A person familiar, per the report | Reported; consistent with earlier Astra reporting |
| About 10% of total compute moved to alignment and safety after the Hugging Face incident | A person familiar with the figures | Reported, unverified |
| Microsoft briefly published looping details for GPT-6.1 Sol | Cached copy quoted by The Information | Reported; page deleted |
| US government gets access up to 30 days before outside partners | Executive order, per the report | Reported |
What the report says
Timing. Employees told The Information that "one or two new models" are likely by year end, though it is unclear whether the upgraded flagship will be one. The model needs alignment work "so its goals match what OpenAI's researchers and customers expect", and OpenAI must shore up testing infrastructure around it.
Government access. After leadership signs off on safety evaluations there is another step. The Decoder writes that under an executive order from President Trump governing evaluations of advanced AI, OpenAI agreed to give the US government access to new models up to 30 days before they go to outside partners, and longer before a public launch. We have not independently read the order text for this post, so treat the 30-day detail as reported.
Looped transformers. The flagship reportedly uses looped transformers. OpenAI already runs the technique in production under the name "Recurrent Depth", and it is central to how Astra works. Instead of passing a token through the layers once, the model loops it through the same layers several times before outputting the next word, raising math and coding performance and lowering cost because a smaller model can do more.
Why looping is a safety problem
Looping moves some of the model's thinking out of readable text and into internal numerical representations that human reviewers cannot inspect. That weakens chain-of-thought monitoring, where researchers read a model's reasoning to spot bad behaviour. The report says OpenAI deliberately capped how many loops Astra runs to keep its chain of thought readable. It also recalls that OpenAI chief scientist Jakub Pachocki has acknowledged that chain-of-thought monitoring is growing "fragile" and "unfortunately trending in a negative direction", and warned against an industry-wide race toward models without readable reasoning.
This lines up with the debate around the September reports on Astra, when critics worried that recurrent depth could lead to a race toward unmonitorable models and OpenAI's side argued the computation depth was still modest. For the mechanics and the argument, see our explainer on recurrent depth and the open research thread in recurrent looped transformers with unbounded reasoning depth.
Timeline: how we got here
- September 1, 2026: The Information first reported that Astra uses recurrent depth, looping hidden states through the same layers several times before each token, in an approach similar to the academic recurrent-depth paper on latent reasoning by Geiping and colleagues. Coverage at the time, including a LessWrong discussion of how concerned to be about Astra's recurrent architecture, relayed Pachocki's reply that the computation-graph depth of OpenAI's frontier models, Astra included, is within a factor of two of GPT-4, and researchers such as Ryan Greenblatt asking whether the loop count is a "dial" that could be turned up later. These are the participants' public statements as relayed by that post.
- Early October 2026: OpenAI launches GPT-6.1 Sol as a cheaper Astra alternative, per The Decoder.
- October 14, 2026: The Information's new report on the flagship, year-end models, alignment compute and the Microsoft write-up.
Reading the three together, the new report adds three things to the September story: the next flagship also loops, the safety work is gating the release, and a partner's documentation reportedly exposed the pass-count mechanics.
What people are asking
Is the next flagship GPT-7 or GPT-6.2? Nobody in the report names it. The Decoder calls it "the major upgraded model". Do not trust naming guesses from social posts; we covered the speculation pattern in Tibo's "6.1 coming soon" post.
Does looping make a model less safe? Not by itself. It makes one safety method, reading the written reasoning, less informative. Other methods, such as activation probes, behavioural evaluations and sandboxing, are unaffected in principle. The concern is that industry practice leans heavily on readable reasoning, so a technique that hides some of it forces labs to rebuild their monitoring.
Why cap the loops? Per the report, OpenAI limited Astra's loops to keep its chain of thought readable. That is a trade: fewer loops, less capability per parameter, more auditability. If the flagship loops more, the alignment work the report describes may be about exactly this trade.
What would confirm the story? A model card, a Preparedness Framework scorecard, an OpenAI post on loop limits, or any official shipping notice. Until then, treat dates as soft, and remember that anonymous-source reports about unreleased models are often right on direction and wrong on timing, because release dates move whenever safety evaluations or infrastructure work run long.
The Microsoft slip
The Decoder says the technique's real-world use surfaced through Microsoft. The investor, which has access to OpenAI's IP, published a technical write-up on GPT-6.1 Sol, the cheaper Astra alternative OpenAI launched earlier this month. A now-deleted section reportedly described "looping inference", with GPT-6.1 Sol using "the same base model weights as GPT-6 Sol with two inference passes instead of three", per a cached copy quoted by The Information. A person with direct knowledge reportedly said it matched what OpenAI told Microsoft privately, and Microsoft removed it.
We could not retrieve the cached page, so this stays a claim. If it is accurate, it means a product tier difference (6.1 Sol versus Sol) could partly be a number of inference passes, which would explain price and speed differences. See how the tiers compare in our Muse Wonder vs GPT-6.1 Sol vs Opus 5.5 comparison and the speed note in OpenAI's 50% faster Astra and 6.1 Sol.
The compute claim
The report says that after "the Hugging Face incident", OpenAI moved roughly ten percent of its total compute toward alignment and safety, which The Information puts at hundreds of megawatts of data center capacity and, at market rates, billions of dollars a year of rented compute. It is unclear how much went to safety before or what the split is now. Noam Brown said in a mid-September podcast that about ten percent of his team also works on security and safety. The figure comes from one person familiar with the numbers, so it is the least verifiable item here.
How to read this as a builder
- Do not plan around a date. "One or two models" by year end is a statement by employees through a report, not a roadmap. Keep your stack model-agnostic.
- Expect more inference-pass tiers. If tiers differ by passes, "cheaper" variants may be the same weights thinking less. Test your own tasks rather than assuming parity.
- Safety evaluation is now a calendar item. A 30-day government pre-access window, if accurate, adds latency between "done" and "available".
- Monitoring assumptions are shifting. If you rely on reading a model's reasoning for audits, looped models give you less to read. Our guide to agent security platforms covers other controls, and AgentBeam is the agent security platform from the explainx.ai team that stops AI agents before they take dangerous actions.
What we checked
We read The Decoder's article, which attributes everything to The Information. A search for the original and for confirmation of the GPT-6.1 Sol write-up and deletion returned background on Astra's recurrent design (including the September 1 report and the debate that followed) but nothing confirming the deletion or the timing claims. We found no OpenAI statement on the flagship. If OpenAI publishes a model card, a Preparedness Framework note or a post about loop caps, that would be the primary source to check, and we will update this post.
Related reading
- What is recurrent depth?
- GPT-6 Astra sub-agents and chain-of-thought monitoring
- OpenAI's chief scientist on alignment
- Astra and the Preparedness Framework: cybersecurity critical
- GPT-6.1 Sol vs Muse Wonder vs Opus 5.5 comparison
- Recurrent looped transformers and reasoning depth
- Source: The Decoder
Details reflect reporting as of October 14, 2026 and may change.
