Rycode

The claimed math breakthrough was agent scale and token spend

Ten thousand agents is not a genius

OpenAI published a claim that a multi-agent system helped resolve a famous open problem in fluid mathematics. The numbers in that post are large. The lesson is not that a single model woke up as a god. The lesson is that the harness, the tools, and a huge token budget did the work.

What was claimed, in plain English

The Navier–Stokes equations are a set of equations that describe how fluids move. A related Millennium Prize question asks whether solutions to those equations always stay smooth, or whether they can “blow up” in finite time. That question has sat open for decades. OpenAI’s public note says an internal model, still in training and described as more capable than its released frontier line, powered a system of coordinating agents that worked the problem.

An agent here is a program that can use tools, write and run code, and hand work to other programs. OpenAI says the agents could read from a cached version of the internet and run code. They were split into groups that could talk inside the group. The group that produced the Navier–Stokes resolution involved on the order of 10,000 concurrent agents. OpenAI says those agents arrived at their resolution after about 88 hours from launch. Formalization and verification in Lean, a language used to check mathematical proofs by computer, took another 17 hours via GPT-6 Astra.

Navier–Stokes

~10,000

Concurrent agents · NS group

OpenAI accounting. Binding constraint: concurrent agents you can afford.

Wall-clock · NS

~88 hours

NS wall-clock from launch to resolution

From launch to resolution. Separate from Lean verify time.

Verify · Lean

+17 hours

Lean formalization / verification via GPT-6 Astra

After the ~88h NS run. Formalization and verification in Lean.

OpenAI also published resource figures. Across all attempted problems, the agents sent about 4.9 million messages and used about 300 billion output tokens. A token is a small chunk of text the model reads or writes. For the Navier–Stokes problem alone, OpenAI reports about 2.7 million messages and about 130 billion output tokens. Those are OpenAI’s own accounting, not an independent audit.

Messages · all

~4.9M

Messages across all attempted problems

All attempted problems. OpenAI’s own accounting.

Tokens · all

~300B

Output tokens across all attempted problems

All attempted problems. OpenAI’s own accounting.

Messages · NS

~2.7M

Messages on Navier–Stokes alone

NS alone. OpenAI’s own accounting.

Tokens · NS

~130B

Output tokens on Navier–Stokes alone

NS alone. Rest of ~300B across other problems incl. Euler.

A related “easier” fluid question, a blowup question for the Euler equations without viscosity, was also resolved in OpenAI’s telling by nearly 100 agents over about 50 hours. That detail matters for the scale story: one notch harder problem, roughly a hundred times more concurrent agents.

Whether the mathematical community accepts the proof as settled is a separate check from what this essay argues. The publishable claim for Research is what the system actually did as engineering: parallel agents, tools, messages, and tokens.

Brute force at machine scale is not a stroke of genius

The costume that travels online is genius. One mind sees what humans could not. The documented shape of the run is different. Ten thousand agents means ten thousand applications talking, sharing intermediate analysis, and searching a large space of attempts. OpenAI’s own totals put about 130 billion of the roughly 300 billion output tokens on the Navier–Stokes problem alone, with the rest across other attempted problems, including the Euler result that also landed. Automated search at this stage still looks like volume and coordination, not a single private insight. Wall-clock time rose less than two times from the Euler run to Navier–Stokes while concurrent agents rose by about two orders of magnitude. The binding constraint looks like how many agents you can afford to run at once, not a mystical insight no person can read.

Euler · easier notch

~100

Agents on related Euler blowup

Easier fluid blowup question (Euler, no viscosity).

Wall-clock · Euler

~50 hours

Euler wall-clock

Related Euler blowup run. Compare to NS ~88 hours.

Scale contrast

~100×

Concurrent agents, one notch harder

Wall-clock rose less than ~2× (Euler ~50h → NS ~88h). Not mystic insight.

Token share · NS

~130B of ~300B

Output tokens on NS vs all attempted problems

Rest: other problems incl. Euler. OpenAI accounting, not audit.

That is leverage. A human who can design the problem split, the tools, and the verification path multiplies labor. It is not a magical super-intelligence sitting above the work with private motives. Every message between agents is, in principle, readable. The breakthrough, if the math holds, is still a product of organized compute and an agent harness. A harness is the wrapper that gives models tools, memory, and coordination. Confusing the harness for a god model is how a research note becomes a doomer or utopia myth.

What OpenAI says about other researchers’ work

OpenAI’s live note says the researchers and the agents did not see the other team’s work through any means until it was released publicly, and that no specific user data was accessed in order to solve the problem. After an investigation, OpenAI says it confirmed that one outside mathematician’s Codex prompts over the two months before the September 8, 2026 announcement could not have influenced the system in any way, including through training.

That is a stronger clearance than an earlier public rumor cycle suggested. Treat the live page as the primary. The engineering story in this essay follows that investigation result, not older rumor wording.

Control of the stack still matters for sensitive work

Separately from that clearance, buyers who care about method leakage still face a product design choice. Hosted frontier APIs keep logs, caches, and training policies inside the vendor’s walls. A commercial promise labeled zero data retention, ZDR for short, sounds like a hard delete. In practice it is a best-efforts contract term about what a vendor says it will not keep. It is not a substitute for controlling the hardware when the work is sensitive enough that leakage of method would hurt.

If that is your bar, the honest design is sovereign or tightly controlled infrastructure: your own stack, or a vendor arrangement where you understand where weights, logs, and caches live. Keep using frontier APIs for low-sensitivity work if you want. Do not confuse a press clearance on one investigation with a general rule that every chat is forever invisible to every future model.

What to take from the claim

OpenAI’s math announcement is best read as a systems result. Coordinating agents with tools, code, and a huge token budget can grind through search spaces humans cannot afford to grind by hand. That is real. Calling it a genius that transcends the harness is storytelling. Price the breakthrough as leverage plus spend. Price privacy as a stack decision, not as a slogan on a rate card.

How to read this: agents/hours = wall-clock run; messages/tokens = spend; Euler vs NS = scale contrast; source = OpenAI accounting.

Quiet: Not independent audit. Math acceptance separate from engineering claim.

Source: OpenAI’s own accounting (not independent audit).

Whether the mathematical community accepts the proof as settled is a separate check from the engineering claim: parallel agents, tools, messages, and tokens.

A.I. Chat models write strings. System One returns typed decisions.A next-token engine with an RLVR post-train and a tool loop.Grok Bot set a new bar in the AI agent race. Meta's Muse raised the stakes.JevFrontier price meets open-weight, and the IPO clock