Temporal Backtracking Search for Test-time Generative Video Reasoning

Preprint

Sejoon Jun1, Zheng Ding2, Chloe H. Su3, Weirui Ye4,†, Yilun Du3,†

1Northeastern University  ·  2Independent Researcher  ·  3Harvard & Kempner  ·  4MIT  ·  Co-advisors


Abstract

Generative video models are emerging as world simulators for sequential decision-making: by extracting action plans from generated rollouts, agents can plan and solve complex tasks entirely in imagination. In this setting, the relevant axis for scaling test-time compute is not aesthetic quality but trajectory correctness.

We identify two empirical bottlenecks that make existing test-time scaling paradigms fail. First, video models commit to a high-level spatial trajectory within the earliest denoising steps — adding compute to later steps cannot rescue a wrong plan. Second, reasoning failures cluster heavily in the early temporal stages — root-level Best-of-N (BoN) wastes its budget by repeatedly re-failing at the same bottleneck, discarding valid upstream progress each time.

We introduce Temporal Backtracking Search (TBS), which shifts the search space to the temporal axis via an iterative generate–verify–restart loop: verify the rollout, isolate the first failure, cache the valid prefix, and generate only the remaining suffix. Across algorithmic reasoning, continuous navigation, and robotic manipulation, TBS Pareto-dominates matched-budget BoN. In a strict out-of-distribution setting where single-shot generation collapses (0.7% for BoN-20), TBS achieves 22.7% — every solved episode from a restarted branch.


Why existing test-time scaling fails

Test-time scaling transformed reasoning in language models, but the recipes that work there do not transfer to generative video. The standard moves — searching over denoising steps, or sampling many full rollouts and keeping the best (Best-of-N) — both assume the model can explore alternatives at the point where it went wrong. For video reasoning, neither assumption holds. We trace this to two empirical bottlenecks.

Denoising-step search

The spatial trajectory is committed at the very first denoising step — S1, S5, and S40 all produce the same plan. There is nothing left to search over.

✗ Wrong axis entirely

Root-level Best-of-N

72–78% of failures occur in the first 20% of a rollout. Every independent resample replays the same early bottleneck — discarding the verified-correct remainder each time.

✗ Wastes verified upstream progress

One-shot generation, long horizons

Correctness must hold at every frame simultaneously. On 2D Maze paths of 41+ steps, single-shot BoN-1 reaches only 1.9% — errors compound multiplicatively as the horizon grows.

✗ Collapses with horizon length

Bottleneck 1 — the trajectory is decided early, in the wrong search space. If we decode the same noisy latent at successive denoising steps, the high-level motion plan is already fixed within the first few steps and never changes afterward. So spending more compute on later denoising steps cannot redirect a plan that was wrong from the start — the denoising axis simply has nothing to explore.

Trajectories are determined by the earliest denoising steps.

(a) The same noisy latent at S1, S5, S40: the motion plan is identical throughout — the trajectory is committed immediately. (b) Denoising-step search offers no trajectory exploration. (c) Temporal-step search does, by branching from verified prefixes.

Bottleneck 2 — failures cluster early, so blind resampling wastes the budget. Reasoning errors are not spread evenly along a rollout; they concentrate heavily in its opening frames. Because Best-of-N starts every candidate from scratch, it keeps re-failing in that same early region and throws away the correct frames it had already produced downstream. As the horizon lengthens, the probability that an independent rollout clears the bottleneck shrinks, and exact match collapses.

Density of first-failure location along the trajectory for Maze and Keys-and-Doors BoN rollouts, concentrated in the first 20%.
Failures cluster early. The first failure in a BoN rollout concentrates in the opening fifth of the trajectory — 72–78% fall in the first 20%. Independent resampling re-fails at this same early bottleneck every time, discarding the verified-correct remainder.
Exact match versus path length for BoN-1, BoN-5, BoN-10, and BoN-20, collapsing past 40 steps.
Collapse with horizon length. Exact match holds on short paths but falls off sharply past 40 steps, and adding budget (BoN-1 → BoN-20) only delays it. Correctness must hold at every frame at once, so errors compound multiplicatively as the horizon grows.

Temporal Backtracking Search

Cache the valid prefix. Branch from there. Repeat.

Both bottlenecks point the same way: stop searching the denoising axis, and stop throwing away verified frames. TBS reformulates video reasoning as inference-time search over the temporal axis. Instead of treating a rollout as one indivisible block, it isolates the first failure, keeps the verified frames before it, and spends compute extending that prefix — turning one long-horizon problem into a sequence of short, locally-easy continuations.

Why this is easier — the conditional reuse gap. A root-level generator must synthesize the entire future from frame 1: pθ(v2:T | v1). Prefix repair only has to resolve what remains after a verified prefix of length : pθ(vℓ+1:T | v1:ℓ). Because reasoning errors compound multiplicatively over time, extending a clean partial sequence is far more tractable than generating a long rollout from scratch. TBS exists to exploit that gap.
1

Generate

Sample candidate rollouts. For the first round, start from the initial frame; afterwards, continue from the highest-priority verified prefix anchor in the frontier.

2

Verify

A process verifier scans the rollout, finds the first failure frame, and returns the verified prefix before it plus a priority score — it localizes where the trajectory broke, not just whether it did.

3

Restart

Cache the verified prefix as a restart anchor, then regenerate only the invalid suffix from that anchor. Repeat until a rollout reaches the goal or the budget is spent.

TBS vs BoN: generate–verify–restart.

BoN (top): one error discards everything; restart from frame 1. TBS (bottom): localize the first failure, cache the verified prefix as a restart anchor in a priority frontier, regenerate only the invalid suffix. Full-prefix conditioning (variable-K) preserves the motion context that a single-frame state reset loses entirely.

Three components make the loop work:

K

Variable-K conditioning — the generative engine

Standard video diffusion denoises all frames jointly from a single initial frame, so it cannot resume from an arbitrary prefix. We fine-tune the base model with a per-frame timestep mask: the first K latent frames are held clean while the suffix is noised. A progressive curriculum (K=1 → 20) teaches the model to treat any verified prefix as fixed context and regenerate only the continuation — at constant per-branch cost.

V

Temporal process verification — finding the restart anchor

A process-level verifier returns the first failure frame, a restart anchor aligned to the VAE's latent boundary, and a priority score. It exposes a failure location and a restartable prefix, but never the correct continuation — the generator still has to synthesize the suffix. We instantiate it three ways: exact symbolic rules, a learned trajectory predictor, and a closed-loop physics simulator.

F

Prefix-based search — reallocating the budget

Verified prefixes live in a priority frontier. Each step pops the most promising anchor and samples a few suffix continuations, inserting any new valid prefixes back into the frontier. This best-first search over prefixes spends compute on extending correct trajectories instead of re-rolling from the root — depth-friendly domains repair late drift, width-friendly ones escape early dead states.


Results

We evaluate across three regimes that span the realistic spectrum of process supervision — from exact symbolic rules to a learned noisy predictor to a closed-loop physics simulator. At matched compute budget, TBS Pareto-dominates Best-of-N in every regime.

Regime 1

Symbolic reasoning

verifier: exact game rules

Five rule-based grid-worlds where deterministic rules localize the first failure exactly. The gain tracks horizon length: tiny on already-saturated short tasks, large where rollouts are long. The clearest case is strict-OOD Keys-and-Doors, where every TBS solve comes from a restarted branch.

Exact Match (%) — matched budget
Baseline (BoN) Ours (TBS) Gain
DomainSplit BoN‑1BoN‑20 TBS‑10TBS‑20 TBS‑20 − BoN‑20
2D Maze Overall 51.0 79.0 84.0 90.3 +11.3
Hard 18.3 60.0 68.7 81.0 +21.0
Sokoban Overall 41.5 82.0 77.7 82.7 +0.7
Hard 37.0 78.3 73.0 79.7 +1.4
Sliding Puzzle Overall 39.5 82.2 80.8 86.5 +4.3
Hard 41.3 81.3 81.3 88.7 +7.4
Keys-and-Doors ID Overall 52.3 97.7 96.5 99.2 +1.5
Strict OOD 0.0 0.7 8.3 22.7 +22.0

Where do the solves come from? Of every episode TBS-20 solves, how many were already solved by a root rollout (depth 0) versus only after a restarted branch (depth ≥ 1). The longer-horizon domains lean heavily on restarts — and strict-OOD Keys-and-Doors is decisive: not a single solve comes from a root sample; all 68 come from restarted branches.

Root solves vs. restarted-branch solves (TBS-20)
Domain TBS‑20 EM Root d=0 Restart d≥1 Restart-added EM
2D Maze 90.3% 357 185 +30.8 pp
3D Maze 97.7% 574 12 +2.0 pp
Sokoban 82.7% 448 48 +8.0 pp
Sliding Puzzle 86.5% 405 114 +19.0 pp
Keys-and-Doors 99.2% 510 85 +14.2 pp
Keys-and-Doors OOD 22.7% 0 68 +22.7 pp
Regime 2

Continuous navigation

verifier: learned, noisy trajectory predictor

Target-Bench tests whether the gains survive when the verifier is learned and noisy rather than an exact rule. TBS improves every one of the five trajectory metrics at both budgets, with the largest gains on miss rate and approach consistency — a noisy process signal is still enough to localize where a rollout drifts.

Target-Bench — trajectory metrics
Method ADE ↓FDE ↓MR (%) ↓SE ↑AC ↑Overall ↑
BoN-1 0.5411.07416.700.2680.7300.323
BoN-3 0.3000.7654.050.4070.8170.424
TBS-3 0.2760.6401.730.4960.9360.508
BoN-5 0.2650.6802.700.4660.8720.473
TBS-5 0.2630.6221.560.5080.9360.511
Regime 3

Robotic manipulation

verifier: physics simulator

Generated videos are decoded to robot actions and replayed in a physics simulator. TBS helps when the base video model produces a repairable approach prefix — reusing the verified pre-grasp motion and regenerating only the failed contact window — but gains shrink under heavy visual randomization, where the base policy rarely reaches the target and there is little to repair.

RoboTwin — success rate (%), matched budget
Baseline Budget 3 Budget 5
Setting BoN‑1 BoN‑3TBS‑3 BoN‑5TBS‑5
Clean scenes 35 4650 4953
Randomized scenes 6 1516 1718

Qualitative examples

Each clip shows BoN exhausting its budget and failing, followed by TBS backtracking to the failure point and succeeding from a restarted branch. Grouped by the same three regimes as the results above.

Regime 1

Symbolic grid-worlds

2D Maze

Grid-world BoN-20 ✗ TBS-20 ✓

3D Maze

Grid-world BoN-20 ✗ TBS-20 ✓

Sliding Puzzle

Grid-world BoN-20 ✗ TBS-20 ✓

Sokoban

Grid-world BoN-20 ✗ TBS-20 ✓

Keys-and-Doors — Strict OOD

Grid-world BoN-20 = 0.7% TBS-20 ✓ depth 3+
Regime 2

Continuous navigation

Navigation — Target-Bench

Continuous BoN-5 ✗ TBS-5 ✓
Regime 3

Robotic manipulation

Robotic Manipulation — RoboTwin

Physics sim BoN-5 ✗ TBS-5 ✓

BibTeX

@article{jun2026temporal,
  title   = {Temporal Backtracking Search for Test-time Generative Video Reasoning},
  author  = {Jun, Sejoon and Ding, Zheng and Su, Chloe H. and Ye, Weirui and Du, Yilun},
  journal = {arXiv preprint arXiv:2606.13861},
  year    = {2026}
}