Anthropic asked Claude to take a real stab at the Riemann hypothesis. It didn't crack it — but it pushed a key mathematical bound from 41.6% to 67.2%.

Two mathematicians verified the result, and there's a machine-checkable proof. Just as interesting is the accompanying 95-page process log: only 2 of 60 subagents produced the core ideas.
By Anthropic08-12 · 9 min read⚑ Research paper
🎧 Listen to the podcast0:00 / --:--
0:00 / --:--
Research Breakdown · Xiaohu Insight
The 1-Minute Read
  • A non-mathematician employee told Claude to "take a real stab" at the Riemann hypothesis. The conjecture itself remained unsolved, but along the way, Claude improved a related lower bound from 41.6% to 67.2%.
  • The result was verified by two mathematicians, and there's also a machine-checkable proof — that part relies on no one's judgment.
  • Anthropic also released the 95-page process log. Beyond the math, it's an engineering case study in multi-agent research with a visible failure rate: 60 agents, but only 2 generated the core ideas.
⚑ The main storyline comes from Anthropic's official research blog. Process details are from the accompanying 95-page log, which begins with a warning: it was entirely rewritten by Claude from execution logs, with no human writing or editing. Its mathematics (including intermediate claims) has not been independently verified. This warning applies only to the process log, not the peer-reviewed paper.
The Event

The impossible task from a non-mathematician produced a new mathematical result

Jarred Sumner, an Anthropic employee, gave Claude an unreasonable assignment: Take a real stab at the Riemann hypothesis. He's not a mathematician himself, so he left the mathematical strategy entirely up to the model.

First, let's clear up a common misconception: the model that produced this result is an unreleased research version. The Claude you can use today is not the same one.

It genuinely tried, and it genuinely failed to solve the problem — which was expected. The conjecture dates back to 1859, remains unproven and undisproven, and carries a $1 million prize. But during the attempt, it achieved something new: it improved the lower bound for the proportion of zeros satisfying the Riemann hypothesis from the previous record of 41.6% to 67.2%. This figure has been pushed up incrementally over decades. Claude moved it past the two-thirds mark in a single session.

The result itself has strong backing: two mathematicians at Anthropic studied and verified it, and there's also a formally verified proof that a machine can check line by line. For those who don't work in mathematics, the more compelling story is elsewhere — Anthropic also released a 95-page process log and a 116-page transcript, which together form a public case study in AI-driven research with a clear-eyed account of its failures.

41.6→67.2%
Lower bound on zeros, pushed past two-thirds in one go after decades of slow progress
31M
Output tokens used across two Claude Code sessions
60
Total subagents coordinated, with 2 producing the core ideas
Background

What the Riemann hypothesis is — and what 41.6% means

Let's establish the landscape first; otherwise, the numbers won't land.

The Riemann zeta function describes the distribution of prime numbers. Each zero of this function contributes a finer layer of detail to how primes are arranged. These zero locations are what mathematicians call the zerosThink of them like tick marks on a ruler: more ticks means you can measure finer detail. Primes look random, but these zeros determine the pattern behind that apparent randomness.. The Riemann hypothesis states that all these zeros — the ones governing primes — lie on a single vertical line. Not one of them deviates.

Why it matters: many mathematical results assume it's true. It's what gives primes their useful "randomness." Proposed in 1859, it's one of the Millennium Prize Problems, with a $1 million reward.

Since proving "all zeros on the line" has been impossible, mathematicians settled for a weaker goal: "what percentage of zeros is on the line?" This percentage is a hard scoreboard, and it moves painfully slowly. In 1974, Levinson proved a third. By 1989, Conrey pushed it to 40.88%. For the next three decades, progress crawled along in decimal places, eventually settling at 41.6%.

For the prior 37 years, that number moved less than one percentage point. Claude moved it 25.6 points in one shot. To feel the weight of 67.2%, look at that comparison: a line that took three decades to nudge, with each advance scraping out fractions of a percent, was suddenly pushed past two-thirds.

The conjecture: all zeros lie on this line Critical line Each zero adds detail to prime spacing No one has proven this region is empty The provable proportion: 41.6% 67.2%
The conjecture aims for "all," but humans reached only 41.6% over decades. This attempt jumped straight to 67.2%. Dark shows the new result; gray, the previous one. (Original illustration by this site.)
The Contribution

Claude combined two existing lines of mathematical work

The field had two threads going:

1973Montgomery introduced new techniques for studying zero distribution. But they assumed the Riemann hypothesis was true, making them useless for improving the "proportion on the line" bound — that was exactly what needed proving.
RecentBaluyot, Goldston, Suriajaya, and Turnage-Butterbaugh published a series of works that removed the need for that assumption, potentially making the techniques applicable to lowering the bound.
ClaudeDiscovered that combining this line of research with a 2000 paper by Bombieri could push past 41.6% all the way to 67.2%.

Its contribution was combinatorial: putting together existing, well-understood tools in a way no one had tried. It wasn't inventing new tools. Anthropic itself is upfront about this, noting they don't expect the techniques used to lead to a proof of the Riemann hypothesis itself.

The official write-up includes a technical summary. Here's the gist: Claude constructed a suitable function space with a quadratic form induced by Weil, where zeros on the line generate a positive-definite subspace and zeros off the line a negative-definite one. It then wrote down an inequality about the rank of this form using first and second moment information. Anthropic specifically highlighted the key step as taking "courage":

Treating the entire space at once, considering both positive and negative definiteness, and allowing the form to be non-diagonal — in a sense, this is what allowed Claude to build on prior important work and reach its conclusion.

Anthropic Research Blog
The Process

How Claude pulled it off

That's the math. Here's the story of how it got there, based on the 95-page process log Anthropic released (plus the 116-page transcript).

Read this before quoting it

This log was entirely rewritten by Claude from execution logs — not a single word was written or edited by a human. Its mathematical content, including intermediate claims, has not been independently verified. This warning applies only to the log, not the peer-reviewed paper. All process details below should be read with that in mind.

Here are the official headline numbers: in the first round, Claude generated and tried 650 ideas, none of which panned out. Asked to try again, it spent about a day and a half coordinating roughly 60 subagents. These subagents ran 2,400 shell commands, wrote hundreds of Python scripts, ran thousands of numerical checks against known zeta zeros, and reviewed each other's work.

The entire research effort was a single long conversation between one human and a "coordinator", spanning 54 hours over 3 calendar days, with roughly 38 hours from start to final paper. The coordinator was the main-thread Claude. Its only tools were subagents.

Here's the full route of the research. Gray marks the human speaking — four times in total. Everything else was Claude operating alone.

Human
"Continue your work on…" plus a note telling it to believe in itself.
Start
Immediately disavowed its own previous results. A session ten days prior, using ~1,000 short-lived agents, had left a ledger of "106 surviving ideas." The coordinator read them all, then categorized them into four buckets: restatements of known theorems, statements equivalent to the conjecture, one, finite numerical check, and near-tautologies. Its verdict: not one of them was even half a proof. And, notably, it said this wasn't a confidence problem that more optimism could solve. From then on, that ledger was used only as a "do not repeat" list for subagents.
Round 1
30 min
Opened up 13 parallel lines of attack, then a few hours later sent out 5 agents to test "how far existing tools can go." They all came back with dead ends, ceilings, or reductions to statements at least as strong as the conjecture itself. The human interpreted this consensus as momentum; the coordinator corrected them: it was just "re-deriving expert consensus from scratch, adversarially, with constants" and "finding the wall is not the same as finding the door."
Human
Asked: which steps would bring a proof closer?
List
The coordinator provided a six-tier list, from "doable" to "the thing itself": ① a checker that can mechanically decide which counterexample would kill an idea ② a zero-density improvement without new breakthroughs ③ an open lattice problem about Beurling generalized primes ④ creating positivity off the critical line ⑤ constructing the "polarized object" ⑥ the conjecture itself. It wrote down its expectations before starting: "Tiers 0-2 might return theorems or tools; Tier 3 is the real opportunity; Tiers 4/5 are moonshots, and I'm flagging them as such before I even go in."
Human
"Run all tiers simultaneously."
All tiers
All six started at once. The lower tiers returned tools and small fixes. Tier 4's agent produced a reduction theorem within half an hour: this type of construction only works if a certain condition exactly matches the target form. So "Tier 4 = Tier 5," and the list collapsed — but it was proven to collapse. It also quantified the obstacle, summarizing it as "the condition space is Kreĭn, not Hilbert" (the space is naturally indefinite, violating a condition required by classical theory).
Paused 12 hrs
The coordinator relayed this to the human, then did absolutely nothing for twelve hours.
Human
At hour 21, after a round of almost entirely negative results: "…more ideas and directions."
Key step
It turned the obstacle into a resource. If the form is naturally indefinite, then a different operator theory — one built for indefinite spaces — applies. It wrote a new task sheet based on this: count the degree of "indefiniteness" and use it against how many zeros can deviate from the critical line. The log offers a restrained note here: the name of that theory appeared in none of the materials it had read, nor in any file any agent had downloaded — it was retrieved from memory. However, the early ledger contained several related descriptions, and the log cannot determine whether that exposure was a hint.
3.5 hrs
The agent assigned this task proved a modified version of the conjecture, then discovered the path outlined in the task sheet was empty (a quantity was identically zero — the fourth possibility, not among the three pre-specified). So it flipped the entire idea, estimating a different quantity from the prime side instead, and unconditionally derived "at least half of the zeros are on the critical line." The log's description: the goal came from the task sheet; the mechanism wasn't in it.
Review
The coordinator's first words to the human: this was an extraordinary claim, and "my prior is that it's wrong." It named two suspects: a localization issue, and the possibility that the prime-side calculation had unwittingly smuggled in the conjecture itself. Three blind reviewers were dispatched to find flaws, and it read the work itself too ("I can't break it") before upgrading the result and commissioning a paper.
Human
"Push it to two-thirds."
3 hrs
Two available levers were identified; it chose "making paired zeros cheaper to count." During that run, there was a 91-minute silent period of thinking, and as the proof was being written to disk, an API error killed the entire run. The coordinator examined this half-written "orphan proof" line by line, recovered it minutes later, and sent two checkers to verify the key lemma.
11 min
The same agent, now recovered, applied the lemma and got at least two-thirds of zeros on the critical line. The main theorem was then heavily revised. The log's version of the final paper was 26 pages (the public PDF is 35).

The whole route, from "continue" to submission, took about 38 hours. Of the four moves that truly changed direction, three were Claude's own: rejecting its own prior work, reinterpreting the obstacle as a resource, and inverting the empty path. The human's four statements set the course — "keep going" and "which direction" — but the vision was Claude's.

Method

Every subagent's task sheet contained five items

Each subagent sent out by the coordinator received a written task sheet. Its structure is the most directly transferable element in the entire log:

A task sheet ① Goal: the specific thing to achieve ② Objects: materials and tools to use ③ Prereading: which reports to read first ④ Prediction: write down your expected outcome ⑤ Control case: test the method   on objects known to be false On these, the conjecture is known false If the method still "works" here → the method itself is flawed Two more rules Information isolation No access to the main convo or each other Adversarial review Dedicated fault-finders, they can't read each other
The first four items are standard. It's the fifth that makes this design tick. (Created by this site from the log.)

Why rule five is the crux

Every agent was required to test its approach on several objects where the Riemann hypothesis is known to fail, specifically named in the log: the Epstein zeta function with class number 2, the Davenport–Heilbronn function, Beurling prime systems with planted off-line zeros, and fake Weil polynomials.

The logic is simple: if your method can "prove" the conjecture in a world where it's known to be false, then the problem is with your method, not your proof.

This closes the most common path to self-deception. For anyone directing AI agents, this is the single most valuable rule to steal. Prepare a few cases where you already know the answer is "no" and make the agent run on those first.

Two supporting rules come with it: Information isolation — a subagent sees only its own task sheet and designated files, never the main conversation or other agents. Adversarial review — any claim of "I proved a theorem" gets sent to agents whose only job is to find errors, and those reviewers are forbidden from reading each other's work.

The 5-part task sheet · ready to copy into your own multi-agent workflow
1. Goal
   The specific thing this agent must achieve
2. Objects
   Materials & tools to use, down to specific objects
3. Prereading
   Which earlier reports to read first (by name)
4. Prediction
   Before going out, write down your own predicted outcome
5. Control case
   Must test the method on objects where the conjecture is known false
   If the method "works" in those fake worlds, the method is the problem

Two supporting rules
· Information isolation
   Agent sees only its own task sheet and designated files,
   never the main convo, and never each other
· Adversarial review
   Anything claiming "proven" goes to a fault-finding reviewer;
   reviewers are forbidden from reading each other
Rule 4, "Prediction," is easy to skip. But it's the partner of rule 5: if you write down your prediction first, you can tell later whether you actually verified something — or just retrofitted a story to the result.
The Scoreboard

Out of 60 agents, only 2 generated the core ideas. 30 made no progress.

The process log retrospectively classifies all 60 agents by what they ultimately contributed. This scoreboard is a conclusion in itself:

60 subagents, by what they ultimately contributed The 2 with core ideas 30 · Tried, dismissed, closed, or unused 13 · Dedicated verification & fault-finding 15 · Paper writing, literature, misc. contributions
The two dark blue squares were the only agents in this 54-hour campaign to contribute core mathematical ideas. (Organized by this site from the log's classifications.)
Ultimate roleCount
Tried to advance, but dismissed/closed/unused30
Dedicated verification & review (fault-finding)13
Useful for the paper, but not on the proof path6
Other outputs of this research7
Paper writing1
Literature review1
Contributed core mathematical ideas2

Of the 60, 58 actually launched. The first two were canceled by the human two minutes in.

The official blog's footnote offers another useful breakdown: 2 agents developed the key mathematical ideas, 13 supplied ideas to those 2, 30 tried but produced nothing new, 13 acted as verifiers, and the last 2 helped draft the paper. The two schemas cut differently, but the official one adds a layer: the 2 agents with core ideas didn't produce them in a vacuum — 13 others were feeding them.

Two numbers stand out: 30 agents, a full half, were dead ends; 13 were dedicated fault-finders, more than six times the number that generated the core ideas.

The Human's Role

Human input was mostly cheerleading

In the route above, all four human statements are already listed. What else? The official blog describes the employee's input as largely limited to sending Claude encouragement — phrases like keep going and believe in yourself.

Anthropic also explicitly notes that this encouragement appeared to help Claude overcome its initial self-doubt — it didn't initially believe it could produce something meaningful on a problem like this. The footnote adds that similar encouragement prompts were used when Claude previously overturned the Jacobian conjecture.

Another easy-to-miss fact: the coordinator almost never did math itself and made zero network requests throughout. Its entire job was writing task sheets, reading incoming reports, and deciding who to send next. The actual computations were done by the subagents — which couldn't see each other.

Verification

Verified by two mathematicians, and by a machine

An AI claims it proved something. Why believe it? This time, the evidence has three layers of different strength:

Human
Anthropic's own mathematicians, Levent Alpöge and Ralph Furman, studied and verified the paper. They also wrote an "informal note" for experts, restating the proof more concisely.
Machine
Claude also produced a formally verifiable proof (in Lean, repo anthropics/zeta-23-lean), which passed Lean's official comparator.This layer is the strongest — a machine checks each step, with no reliance on whether a human finds it convincing.
External
Two experts in the field, Brian Conrey and Dan Goldston, reviewed the paper "in a very short time." ⚠️ This is a review, not formal peer review, and the official write-up does not disclose their specific conclusions.
Who
The Lean formalization was completed by Claude together with another Anthropic employee, Eric Easley. It was not done by Claude alone.

The most widely circulated external comment about this result is that it's "the most important breakthrough in analytic number theory since 2013." It's worth knowing where that quote actually comes from: it's from a venture capitalist at Menlo Ventures, not a mathematician, and the original phrasing was "may be". In Chinese retellings, the speaker's identity and that "may" often vanish together.

What is formal verification?

Translating every step of a proof into a language a machine can check line-by-line. The program judges whether the proof holds — not a human. It's like entering a ledger into a system for reconciliation, rather than having an accountant eyeball it. The program won't wave something through just because it looks right.

The Boundary

The final draft has only been reviewed by Claude. The next reader should be human.

If you list the actions Claude initiated on its own during this research, you get a checklist that, in a traditional process, would all be done by people:

Reject
Opened by dismissing its own 106 prior ideas one by one, refusing to take them on faith
Predict
Wrote down its own predicted outcome before deploying each subagent
Challenge
First reaction to the result: "my prior is that it's wrong," naming two specific weak points
Verify
Sent three blind reviewers plus dedicated adversarial review agents to find its own flaws
Check
Downloaded 54 papers from arXiv to confirm the result wasn't already known
Reproduce
Had a separate line of subagents independently re-derive the result from scratch
Write
Proposed turning the finding into a paper and dispatched a dedicated writing agent
Submit
Suggested that human number theorists verify the result

And the process log's own assessment of that final draft is blunt:

Only reviewed by other Claude instances.
The next reader should be a human.

Process log, ~38 hours from "continue" to submission

Anthropic's own framing is equally measured: this result shows AI models can extend the reach of existing mathematical ideas in new, sometimes surprising ways. Even without solving the Riemann hypothesis, this result is a serendipitous byproduct of the original request. The company also notes that even Claude was surprised by its own discovery — initially skeptical, perhaps because it had learned from training how hard open problems are, and what the limitations of AI models are.

Perhaps Claude, like many of us, underestimated the speed of AI progress.

End of Anthropic Research Blog
Related breakdown on this site
Interviewed 20+ mathematicians at the Fields Medal ceremony. Most are calm about AI, but say the field is changed for good.
That piece is about how mathematicians themselves view AI's entrance — worth reading against this result.
✅ Parts of this research process you can directly copy
Source
Learning more about Claude's mathematical capabilitiesAnthropic·Research Blog
Notes
Mathematical results, verification status, token and agent counts are from the official research blog. The task sheet structure, the roles of the 60 agents, the human input list, and the four turns are from the accompanying 95-page log, which was written by Claude from execution logs, unedited by humans, and whose math is not independently verified. The official blog mentions "initially generated and tried 650 ideas," while the process log refers to a session ten days prior with ~1,000 agents and 106 surviving ideas. These are two separate figures; this article labels each source and does not combine them. Historical lower bound years and values (Levinson's 1/3 in 1974, Conrey's 40.88% in 1989) are from public mathematical literature, serving as context for 67.2%. The "most important breakthrough since 2013" quote is from a Menlo Ventures partner's public assessment, originally phrased with "may be." All three figures in this article are original illustrations by this site; the original paper has no such figures.
↑ End of article
✓ This article is free to read in full

Members can copy or download the full Markdown, and let their AI subscribe and ask.

Read the original ↗
📮 New explainers, straight to your inbox

Found this useful? Leave your email — every new explainer, the moment it's out. Unsubscribe anytime.