BoxWAM: Box Trajectories as Compact State Representations for World Action Models

Qinxi YuWenzhou DingGloria X. WangAlbert J. ZhaiShenlong Wang
UIUC  |  CoRL 2026
Rollout
Speed

The brew-button stage includes resets: the soft gripper is slightly offset, which makes pressing the button hard even for a human teleoperator.

Overview
Abstract

What is the minimal future a robot needs to imagine?

World action models (WAMs) are policy models that explicitly predict both actions and future world states, and have been shown to outperform action-only models across robotic manipulation tasks. However, representing the future with full-frame video prediction is computationally expensive during both training and inference. This raises a central question: what is the minimal state representation that preserves the planning and supervision benefits of future prediction? We propose BoxWAM, which replaces dense future frames with oriented bounding-box trajectories of task-relevant objects. By explicitly imagining object-centric future motion, our method provides a lightweight prediction target that captures the key physical changes induced by robot actions. Box-trajectory prediction substantially reduces computational cost while improving action-prediction performance, suggesting that object-centric compact states are an efficient alternative to video-based world action modeling for manipulation.

Method

Each object's future is the image-plane location of the 8 corners of its minimum-volume oriented 3D bounding box: a 16-dimensional vector per object that keeps coarse shape and motion while discarding background texture, lighting, and shadows.

Object-centric box states

The whole future state is the box trajectory of the actively manipulated object: the one the gripper is touching, or about to touch. The active box automatically shifts across task stages (e.g. pod → machine → mug).

Flow matching

A flow-matching DiT jointly denoises future box tokens and action tokens. Frozen DINOv3 encodes the scene + wrist views into context; proprioception & flow-time enter via adaptive layer-norm.

Causal attention

A causal mask lets actions attend to imagined future boxes, but stops boxes from attending to future actions, so the box trajectory acts as an object-motion plan that steers, not follows, the action chunk.

Inference pipeline

STEP 1
Encode
Scene + wrist images → DINOv3 visual context tokens.
STEP 2
Imagine
Denoise H future box tokens, the object-motion plan.
STEP 3
Act
Action tokens attend to boxes & context to denoise the chunk.
STEP 4
Execute
Run the chunk on the robot, then replan.
Simulation

Predicted boxes across all 50 RoboTwin2.0 tasks

One successful clean-setting rollout per task from the multi-task π0.5 + BoxWAM model (50 tasks × 50 demonstrations), with the predicted box trajectory drawn on every frame. Played at 2× speed.

Results

BoxWAM improves action prediction at near-zero extra cost

Across simulation and real robots, predicting compact box futures beats action-only imitation, while adding only a few milliseconds of inference latency compared with the tens of milliseconds that dense video or latent futures cost.

Real-world manipulation

Real-world success rate (SR) and subgoal progress rate (%). 50 demonstrations per task, 50 randomized test scenarios, same execution protocol for every method.
MethodCoffee SRCoffee Prog.Water SRWater Prog.Pokémon SRPokémon Prog.Average
Diffusion Policy10.034.08.09.434.047.023.7
Flow (action-only)24.048.048.054.760.072.051.1
BoxWAM26.054.466.070.770.078.060.85

Single-task simulation on RoboTwin2.0

Success rate (%) per task, 50 demonstrations per task. BoxWAM and Flow (action-only): 3 seeds × 100 trials. Other baselines from the RoboTwin2.0 leaderboard; π0 is pretrained. Scroll sideways for all nine tasks.

MethodObs.Avg.Adjust BottleBeat HammerClick AlarmGrab RollerHandover MicLift PotOpen LaptopPick Dual BottlesTurn Switch
Clean setting
DP1× RGB55.497.042.061.098.053.039.049.024.036.0
ACT3× RGB60.497.056.032.094.085.088.056.031.05.0
DP3 (uses depth)1× RGB-D81.299.072.077.098.0100.097.082.060.046.0
π03× RGB71.490.043.063.096.098.084.085.057.027.0
Flow (action-only)1× RGB73.299.763.090.399.758.369.381.047.750.0
BoxWAM1× RGB78.397.767.795.0100.065.384.380.062.052.3
Randomized setting
DP1× RGB0.70.00.05.00.00.00.00.00.01.0
ACT3× RGB6.323.03.04.025.00.00.00.00.02.0
DP3 (uses depth)1× RGB-D5.13.08.014.02.03.00.07.01.08.0
π03× RGB33.156.021.011.080.013.036.046.012.023.0
Flow (action-only)1× RGB32.672.318.717.777.71.06.343.318.338.0
BoxWAM1× RGB37.888.729.329.378.30.022.740.316.734.7

BoxWAM has the best randomized-setting average, and the best clean-setting average among RGB-only methods (only depth-based DP3 scores higher).

Multi-task generalist on RoboTwin2.0

2,500 demonstrations (50 tasks × 50) · joint-position control

Multi-task fine-tuning on 50 tasks × 50 demonstrations (2,500 total), joint-position control, 30k training steps for both models. Success rate (%); latency at π0.5's default 10 denoising steps.
MethodCleanRandomizedLatency
π0.552.626.955.3 ms
π0.5 + BoxWAM61.534.057.7 ms

Comparison with existing world action models

27,500 demonstrations · end-effector pose control

A separate, larger protocol from the multi-task table above: π0.5 + BoxWAM is fine-tuned on 27,500 RoboTwin2.0 demonstrations with end-effector pose actions for 35k steps (predict 50 actions, execute 36), and compared against existing WAMs. Latency on an RTX Pro 6000.

Scatter plot of mean Easy/Hard success rate versus policy latency (log scale). BoxWAM reaches about 88% at roughly 65 ms with a 3B model, near pi0.5's latency; Fast-WAM, LingBot-VA and Motus reach 88–93% but at 82–320 ms with 5–8B models and heavier training.
Mean Easy/Hard success rate vs. latency. Marker size: parameters; color: estimated training GPU-hours (not hardware-matched).

BoxWAM stays within a few milliseconds of π0.5 while closing most of the gap to much larger, slower WAMs. For reference, a differential-IK baseline (Mink + M2T2) given ground-truth task plans, poses, depth and masks reaches 26.78% Easy / 26.30% Hard.

Why boxes? Future-state representation ablation

Future-state representation ablation on 9 single-task RoboTwin2.0 tasks (3 seeds × 50 trials). Success rate (%). Latency on the real-world two-camera setup (scene + wrist), 50 denoising steps.
Future stateLatencyCleanRandomized
Action only168.3 ms73.232.6
Dense video (Wan2.2 VAE)250.5 ms80.134.5
Latent (DINOv3 ViT-L)251.4 ms69.929.0
6D object pose≈ box73.232.1
2D OBB≈ box74.230.7
Functional keypoints≈ box75.327.8
End-effector trajectory≈ box74.032.6
Box trajectory, projected 3D OBB (ours)172.4 ms78.337.8

Box futures add just +4.1 ms over action-only and outperform every other compact state in both settings. Dense VAE scores highest on clean but costs ~82 ms more, and needs 15k training steps vs. 6k for the compact variants. "≈ box": same latency as the box variant.

Attention ablation

How future-state and action tokens should interact during generation (% success). Arrows indicate information flow.
DesignAttentionCleanRandomized
Flow (action-only)N/A73.232.6
Fully separate predictionState ⟂ Action76.637.4
Fully joint predictionState ⇔ Action76.732.9
Action then futureState ← Action76.135.5
Future then action (BoxWAM)State → Action78.337.8

BoxWAM works best when actions can attend to imagined future boxes, but boxes cannot attend to future actions. In other words, the box plan leads. All runtimes measured on an RTX Pro 6000 Blackwell GPU.