Speaking at the ADIPEC energy conference in Abu Dhabi on November 2, OpenAI CEO Sam Altman said the September run in which 10,000 agents collaborated for about four days used "the model that is going to be released soon, the next GPT," stressing that the agents had no hierarchy and were fully decentralized. It is the first public statement tying the internal model behind OpenAI's September Navier-Stokes proof to its next flagship, though OpenAI has given no name, release date or price.
Key Takeaways
- ✓Quote (ADIPEC keynote video): "It was 10,000 agents of the model that is going to be released soon, the next GPT, working for about four days, nonstop."
- ✓OpenAI's September 8 blog post: about 10,000 concurrent agents reached the result in about 88 hours, and GPT-6 Astra took another 17 hours for Lean formalization and verification.
- ✓Scale (OpenAI figures): 2.7 million agent messages and about 130 billion output tokens for Navier-Stokes alone; 4.9 million messages and about 300 billion output tokens across all attempted problems.
- ✓The Lean proof is public at openai/NavierStokesAndEuler and establishes statements C and D of the official Clay formulation (breakdown with smooth forcing).
- ✓Not disclosed: the next GPT's name, release date, price or benchmarks; names like "GPT-6.2 Astra" circulating on X are speculation.

Key Decision Metrics at a Glance
Turn your technical choice into a development budget
Compare 40 dev plans & simulate token costs vs $20/mo subscriptions
Project Links & Resources
Direct AccessIn-Depth Technical Analysis
Core Background and Industry Pain Points
On September 8, OpenAI said an unreleased internal model driving roughly 10,000 concurrent agents produced a solution to the Navier-Stokes Millennium Prize problem in about 88 hours, along with a Lean formalization. At the time OpenAI said only that the model was significantly more capable than GPT-6 Astra, not whether or when it would ship. On November 2, in his opening keynote at the ADIPEC energy conference in Abu Dhabi (where OpenAI also announced partnerships with ADNOC, G42 and others), Sam Altman filled that gap: the 10,000 agents were running "the model that is going to be released soon, the next GPT." For developers, that suggests the next flagship's pitch will lean on large-scale, long-running autonomous multi-agent work, not just single-turn chat ability.
Architecture Highlights and Underlying Mechanism
On stage, Altman said the agents worked for about four days nonstop with no hierarchy and no bosses, fully decentralized, choosing their own directions and sharing progress. OpenAI's September post is more specific: agents could read a cached copy of the internet and run code, were split into groups that communicated internally, and different groups tried different formulations of the problem; Codex was then used to consolidate the most useful insights across groups. Altman's "about four days" differs slightly from the blog's "about 88 hours"; the blog is the more precise figure.
Authoritative Benchmarks and Measured Results
OpenAI has not published benchmarks for the next GPT. The only citable numbers are vendor figures from the September post: 2.7 million agent messages and about 130 billion output tokens for Navier-Stokes alone; 4.9 million messages and about 300 billion output tokens across all attempted problems; and 17 more hours for GPT-6 Astra to complete the Lean formalization. Quanta Magazine quoted OpenAI's Sebastien Bubeck estimating the compute cost at several million dollars. The proof covers the case with smooth forcing (statements C and D in the Clay formulation), and mathematicians are still debating its significance.
Developer Playbook and Getting Started
Three things you can do now. First, read openai/NavierStokesAndEuler on GitHub and run lake build locally with Lean 4 and Mathlib to see a model-generated, machine-checked workflow end to end. Second, borrow the structure for your own agent systems: parallel groups, in-group communication and periodic consolidation, plus an automated verifier that can say no, such as tests, type checks or formal checks. Third, reserve evaluation budget for the new model and test long tasks and multi-agent setups first once it ships. Names such as "GPT-6.2 Astra" and release dates circulating on X have no official source, so do not plan around them.
Benchmark side-by-side against alternatives, or calculate monthly token cost vs subscription break-even.
Discussion & Comments
0Sign in to join the discussion
Connect with AI developers to exchange benchmark insights.