The race for a bigger context window is a race for a bigger invoice. NVIDIA sat down and counted what remembering everything costs. The answer is awkward for the whole industry.
On November 3, 12 NVIDIA researchers posted "You don't need long context" on arXiv. The core claim is blunt: long context is not free luxury, it's a line item. And often you can strike it.
They tested it on agentic tasks. Compress the transcript into a summary as you go, and quality mostly holds.
First they priced it. Every next token in a response costs more than the previous one, because the model recomputes the whole history. On open-weight models the gap reaches 7x.
Then the model-by-model numbers. One generated token at 256K context versus 16K: Z.ai's GLM 5.2 is 3.6x more expensive, Moonshot's Kimi K2.6 is 5.6x, Alibaba's Qwen3 Coder Next is a full 7x.
Then six long-horizon agent benchmarks: SWE-bench Verified, Terminal-Bench 2.1, FRAMES, BFCLv3 and two more. Main subjects: Claude Opus 4.5 and GPT 5.6 Sol.
The industry measures context with a ruler: more means better. This paper attacks that from two sides.
One: it exposes a price asymmetry. The point isn't "context is expensive", it's that late tokens cost more than early ones — and that's a multiplier, not a surcharge.
Two: the authors don't propose cutting the history, they propose rewriting the state. Their idea is a Semantic State Space Model: the model reads a natural-language description of the task state, takes an action, then rewrites that description. For now it's a concept only — the authors say they neither trained nor evaluated such a model.
22 configurations: different full-context limits, different summarization triggers. Only 5 of 22 fell more than 2 points below baseline.
In the "one action per step, pass only the compressed state" mode: Claude Opus 4.5 on coding went 70.0 → 70.2. GPT 5.6 Sol went 84.4 → 82.4, down 2 points.
The surprise sits on 1,600 questions over long documents (LOONG). Full context lost. Claude Opus 4.5 with every document stuffed in: 70.1 average, 38.9% fully correct. With selective reading and context kept under 16K: 79.3 and 53.4%.
Feeding it everything isn't always the smart move. Sometimes it's just more expensive.
Long context has been the headline marketing argument for years. If decent compression does half the job, the window race turns into a summary race.
For agent builders this is straight economics: same result, fewer expensive tokens. For providers it's an awkward customer question: why pay for 256K when 16K with smart memory answers just as well?
And the line from the abstract: "Our findings question the need for long-context language models."
This is a preprint. No peer review.
The main measurements cover two frontier models. And there's a counterexample the authors put in their own appendix: with Qwen3 Coder Next, compression to 16K collapsed coding success from 53.0% to 3.6%. The paper calls it "catastrophically collapses". So compression is no universal pill — on some models it breaks behaviour instead of saving money.
The Semantic State Space Model stays on paper. No training, no evaluation.
1. Is compressing the dialogue genuine savings, or quiet reliability loss? If 5 of 22 configurations did drop more than 2 points, where is the line for "barely worse"?
2. Which number do you trust: the 79.3 vs 70.1 average on LOONG, or the 53.0 → 3.6% collapse on Qwen3 Coder Next? What has to change for both to stop contradicting each other?
3. If long context isn't needed, why do providers keep scaling it — engineering or marketing?
Prediction: Within months, at least one major agent-API provider will sell context compression as a separate feature, priced below the full window.
Disclaimer: preprint, not peer reviewed
Source: arxiv.org · post in Telegram