WORLD ACTION MODELS · REAL-TIME INFERENCE

RealtimeWAM: How Fast Can I RunMy World Action Model?

Parallel execution and adaptive computation for responsive robot control. No additional model training.

Huanan Liu1 Ye Li1 Kangye Ji1 Xiaoyu Chen1,* Hanyun Cui1 Yutian Shen1 Yuan Meng1 Chenglei Wu2 Jingyan Jiang1 Bo Li3 Zhi Wang1,†

1 Tsinghua University2 YuanxingGuangnian Robotics3 Nanjing University

* Work done during an internship at Tsinghua University.   † Corresponding author.

01 / REAL-WORLD MANIPULATIONThree shuttlecocks · moving conveyor
React as the scene changes.Conveyor speed: 1 m/min
8.90×

FastWAM speedup

24.09 ms average inference
10.67×

OpenWAM speedup

63.09 ms average inference
+37.2pp

OpenWAM real-world success

33.6% → 70.8% across five tasks

Simulation speedups relative to original Native execution, averaged across four settings. Real-world success is averaged separately over five tasks.

THE IDEA

Compute where it matters.
Overlap what can run together.

World action models predict actions—and sometimes future video—from the current observation. Their inference cost can leave a robot waiting while its environment continues to move.

RealtimeWAM coordinates three decisions: when each branch runs, which observation tokens need fresh features, and how many full Transformer evaluations a prediction receives.

We evaluate the framework on FastWAM and OpenWAM across RoboTwin, LIBERO, LIBERO-Plus, and five real-world tasks.

IN ACTION

Five tasks. Changing scenes.

Recorded task demonstrations.
Videos retain their source playback timing.

02

Carrot to plate

Pick and place from a moving conveyor.

03

Hang a mug

Place the handle onto a rack on a level tabletop.

04

Tennis ball to bowl

Transfer a ball from the conveyor into a bowl.

05

Intercept a rolling can

Catch and place a can on an inclined tabletop.

Each task was evaluated over 50 trials per backbone and inference configuration. These videos illustrate individual executions.

METHOD

One coordinated inference pipeline.

The execution schedule and the amount of fresh computation are designed together.

Method overview: parallel observation and prediction branches, selective token refresh, and adaptive two- or four-evaluation refinement.
RealtimeWAM combines parallel execution, observation-token reuse, and motion-adaptive predictive refinement.
01

Overlap execution

Release observation keys and values layer by layer, allowing prediction to overlap the remaining observation computation.

02

Refresh selected tokens

Use RGB and feature changes to select observation updates. Fill available execution capacity with informative tokens.

03

Adapt refinement

Decode a coarse action after two full evaluations. Predicted displacement determines whether to add two more.

Explore the execution schedule and token selection +
Native and parallel schedules for action-only and joint video-action architectures.
Parallel schedules for the two architecture families.
RGB-required tokens, feature selection, and the resulting refreshed tokens.
Observation changes guide which cached features are refreshed.

EXPERIMENTS

Success and latency, together.

FastWAM · success rate (%) and measured mean latency
MethodRoboTwin
Clean
RoboTwin
Random
LIBEROPlusAverage
success
Latency
(ms)
Speedup
Native91.8891.7897.6049.8082.77214.331.00×
VLA-Cache80.0083.2097.0048.6077.20115.551.85×
TeaCache81.4290.8697.0549.2079.6349.284.35×
ToCa91.3591.2494.5549.1581.57102.662.09×
BAC91.6789.5397.5051.5582.5667.143.19×
RealtimeWAM (Ours)92.0490.5097.2551.2082.7524.098.90×
OpenWAM · success rate (%) and measured mean latency
MethodRoboTwin
Clean
RoboTwin
Random
LIBEROPlusAverage
success
Latency
(ms)
Speedup
Native93.6494.0699.3064.7587.94672.831.00×
VLA-Cache93.3689.9498.4062.7086.10400.261.68×
TeaCache90.4294.1298.6063.8086.74245.992.74×
ToCa93.4293.9898.1063.7087.30440.421.53×
BAC93.5291.9698.9066.7087.77305.082.21×
RealtimeWAM (Ours)92.7894.0299.0063.8587.4163.0910.67×

Averages weight the four settings equally. Caching baselines use compilation and CUDA Graph replay. Speedups use original Native latency as the reference. Hardware: a modified 48 GiB RTX 4090.

REAL-WORLD SUCCESS

Largest gains in dynamic tasks.

Across five tasks, average success improves by 17.2 percentage points on FastWAM and 37.2 points on OpenWAM.

NativeRealtimeWAM
FastWAM
35.6%
52.8%
OpenWAM
33.6%
70.8%

TASK-BY-TASK RESULTS

Success and inference latency on the robot.

FastWAM · five real-world tasks
TaskNativeRealtimeWAM
Success (%) ↑Latency (ms) ↓Success (%) ↑Latency (ms) ↓
Three shuttlecocks24.0210.3640.024.33
Carrot to plate46.0209.7474.021.86
Hang mug72.0211.0870.025.07
Tennis ball to bowl26.0210.5234.023.24
Rolling can to bowl10.0211.8546.024.11
Average35.6210.7152.823.72
OpenWAM · five real-world tasks
TaskNativeRealtimeWAM
Success (%) ↑Latency (ms) ↓Success (%) ↑Latency (ms) ↓
Three shuttlecocks4.0640.2868.068.61
Carrot to plate66.0638.5696.062.12
Hang mug82.0642.1582.065.36
Tennis ball to bowl16.0639.4776.064.85
Rolling can to bowl0.0643.8932.065.43
Average33.6640.8770.865.27

50 trials per task, backbone, and inference configuration. Latency is measured during local inference; averages weight the five tasks equally.

COMPONENT ABLATIONS

Where the gains come from.

OpenWAM on RoboTwin. Each variant changes the indicated component of the full method.

Success rate and measured latency
ConfigurationSuccess (%) ↑First forward (ms) ↓Request (ms) ↓
Ours (full)93.430.9663.76
w/o token reuse93.837.4172.10
Random tokens91.330.7562.32
w/o capacity filling92.130.7661.78
Random gate91.131.0264.77
Fixed 2F89.631.1154.70
Fixed 4F93.730.8795.26

Request is the mean inference latency measured over complete rollouts. Fixed 2F and 4F retain the normal token policy; the random gate preserves the adaptive gate’s budget proportions.

A CLOSER LOOK

Computation changes throughout a rollout.

Observation updates and predictive refinement vary across successive action requests.

Fifty requests from an OpenWAM block-sorting rollout, with observation frames, predicted motion, evaluation counts, and token allocation.
A complete 50-request OpenWAM rollout showing both evaluation budgets and all three token capacities. The illustrated episode ends in task failure.

OPEN SOURCE

Run RealtimeWAM on OpenWAM.

All three components are available as a compact external runtime. Use the original OpenWAM model and weights without editing upstream source.

01 / DEFAULT

Parallel execution

Overlap independent branch computation, with compiled phases, fused operators and CUDA Graph replay.

02 / OPTIONAL

Observation FFN reuse

Refresh selected observation positions and reuse the remaining FFN outputs across requests. Enable with reuse_tokens=True.

03 / OPTIONAL

Adaptive 2F / 4F

Select two or four full Transformer evaluations while retaining ten Euler updates. Enable with adaptive_2f4f=True.

Parallel execution is enabled by default. Token reuse and adaptive refinement introduce approximation and are disabled by default. This release covers OpenWAM; FastWAM and the full closed-loop evaluation suite are outside its scope. Results above are from the paper.

CITATION

Building on this work?

Please cite the paper if you use RealtimeWAM in your research.

@misc{liu2026realtimewam,
  title         = {RealtimeWAM: How Fast Can I Run My World Action Model?},
  author        = {Huanan Liu and Ye Li and Kangye Ji
                   and Xiaoyu Chen and Hanyun Cui and Yutian Shen
                   and Yuan Meng and Chenglei Wu and Jingyan Jiang
                   and Bo Li and Zhi Wang},
  year          = {2026},
  eprint        = {2610.10079},
  archivePrefix = {arXiv},
  primaryClass  = {cs.RO},
  doi           = {10.48550/arXiv.2610.10079},
  url           = {https://arxiv.org/abs/2610.10079}
}
Download BibTeX ↓

THE PAPER

RealtimeWAM

How Fast Can I Run My World Action Model?

Read the full paper ↗