Two different models top the ATLAS long-context benchmark at 128K and at 1M tokens
ATLAS, a 26-model long-context benchmark, has Gemini 3.1 Pro Preview leading at 128K tokens and Claude Opus 4.6 leading at 1M. A shortlist drawn at 128K cannot be assumed to hold for prompts near 1M.
The Engineer · Build desk

Key figures: 7 models changed ranking position by at least two places when the ATLAS evaluation expanded from the 8K-128K range; 26 models were evaluated; inputs ran up to 1M tokens.
| Figure | Value | Note | Claim |
|---|---|---|---|
| Models moving at least two ranking places past 8K-128K | 7 models | 9 | |
| Models evaluated | 26 models | 2 | |
| Longest input tested | 1,000,000 tokens | 2 |
What happened
- The 6,438 evaluation instances span eight capability dimensions and input lengths from 8K to 1M tokens.
- The aggregate, ATLAScore, is a harmonic-mean-based score across capability categories, intended to penalize highly imbalanced profiles.
- Once the evaluation grew past the 8K-128K range, seven models moved two or more places in the rankings.
Why it matters
- decision A team whose prompts run between 128K and 1M cannot read either leader off the result, and has to replay its own prompts at its own lengths to choose.
- constraint A retrieval-only pipeline gets little from an aggregate built to punish imbalance, because the model that tops ATLAScore may not top the one category that pipeline runs.
- exposure A shortlist built on 8K-128K results is exposed to reordering once longer prompts enter the test.
ATLAS scores each model across a predefined grid of context lengths, from 8K to 1M tokens, instead of at one prompt size [5]. That design is how two models can each hold a lead. Gemini 3.1 Pro Preview led at 128K [3] and Claude Opus 4.6 led at 1M [4]. The two lengths are about eight times apart [14], so the lead changed hands somewhere between them [15]. The post does not report the scores, the margins, the uncertainty intervals or where the crossover falls.
The paper's stated motive is two weaknesses in older evaluations. Performance can deteriorate as input length increases, and success on foundational tasks such as retrieval does not necessarily transfer to complex application workloads [12]. ATLAS therefore separates foundational operations from downstream workloads [6]. The post puts the old question this way: the issue is no longer whether a model accepts a million tokens but how much of that context it can use correctly [13]. Acceptance is the easy part. The API takes the tokens and answers confidently either way, according to the post.
The aggregate is built for general ranking. ATLAScore is designed to penalize imbalanced capability profiles [7], and the framework propagates uncertainty into the final score [8]. Both are sound choices. The second lets a reader ask whether a gap between two models is larger than noise.
For either leader to transfer to your system, your prompts have to land near that length and your task mix has to resemble the eight ATLAS capability dimensions [2]. The lead also has to exceed the noise.
The post itself warns against the broad reading. It says the result does not make Claude universally better than Gemini, and that it means only that the relative ranking changes under the evaluation conditions ATLAS used [10]. We agree. In our view the useful test is a replay of a sample of your real prompts, at your real lengths, against two or three candidates.
This is a secondhand read. The post says it analyzes published research, is not an independent benchmark, and that its author did not personally test all 26 models [11]. The paper is arXiv 2605.28079, by Deli Huang and colleagues, published May 27, 2026 [1].
What to watch
- The paper's own tables at arXiv 2605.28079: per-length scores, uncertainty intervals and where the lead passes from Gemini 3.1 Pro Preview to Claude Opus 4.6.
- Whether the seven rank changes show up when a team replays its own production prompts at 128K and at 1M.
- Whether model vendors begin to publish per-length curves instead of a single headline context window.
Clarity's read
What the record supports and how the coverage leans. The claims behind it follow.
Reality
- Evidence50
- Adoption
- Insufficient
- Hype gap−10
- Incentives
- Insufficient
- Confidence45
Claim ledger
Ranked by verification strength, evidence, and original report placement.
- [1]
The paper is 'ATLAS: All-round Testing of Long-context Abilities across Scales', by Deli Huang and colleagues, published May 27, 2026, at arXiv 2605.28079.
- [2]
The researchers evaluated 26 models on 6,438 instances across eight capability dimensions, with input lengths from 8K to 1M tokens.
- [3]
Gemini 3.1 Pro Preview led at 128K.
- [4]
Claude Opus 4.6 led at 1M.
- [5]
Instead of measuring performance at only one input size, ATLAS considers scores across a predefined context-length grid from 8K to 1M tokens.
- [6]
ATLAS distinguishes foundational operations from downstream workloads, because retrieving information and applying it correctly are different capabilities.
- [7]
ATLAScore is a harmonic-mean-based aggregate across capability categories, intended to penalize highly imbalanced capability profiles.
- [8]
The ATLAS framework includes uncertainty propagation when computing its final aggregate scores.
- [9]
Seven models changed position by at least two ranking places when the evaluation expanded from the 8K-128K range.
- [10]
The post says the result does not mean Claude is universally better than Gemini, nor that Gemini is inherently unreliable; it means the relative ranking changes under the specific evaluation conditions used by ATLAS.
- [11]
The post states that it analyzes published 2026 research, is not an independent benchmark, and does not claim the author personally tested all 26 models.
- [12]
The ATLAS researchers investigated two weaknesses in traditional long-context evaluation: model performance can deteriorate as input length increases, and success on foundational tasks such as retrieval does not necessarily transfer to more complex application workloads.
- [13]
The post argues the question in 2026 is no longer whether a model can accept a million tokens but how much of that context it can use correctly, and describes a model accepting a full repository without complaint and confidently providing an answer.
- [14]
The 128K and 1M context lengths are about eight times apart.
- [15]
Because the leader at 128K differs from the leader at 1M, the lead changes hands at some context length between 128K and 1M.
Get this ledger inside ChatGPT. Ask about any of our stories and the answer brings its figure, each claim’s verdict and the sources. Free, no account.
Sources
1 independent publisher whose own reporting we read for this story.
- dev.toClaude vs Gemini vs GPT: What a 2026 Study of 26 AI Models Reveals About Long Context
1 article · October 14, 2026
Topics and entities
Follow any of these and your For You feed starts watching them — no settings page required.
Topics
- Long-Context EvaluationFollow
- LLM benchmark resultsFollow