Who it is forA researcher testing forward dynamics without pixel reconstruction.
The problemPixel reconstruction losses are expensive.
The outcomeA policy that also predicts the next latent state during training and rollout.
What you need first
- Python with PyTorch
Steps
- Install robo-ttt
- Set predict_next_latent = True and designate state_arg
- Tune next_latent_predictor_kwargs for loss weighting
- Request the predicted next latent during rollout sampling
Prompt for your agent
In robo_ttt, enable predict_next_latent with a state_arg, train for a few steps on dummy data, and report the dynamics loss. Confirm rollout returns the predicted next latent.
Caveat. This option follows Xu et al., 2026, which is separate from the RoboTTT paper.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for lucidrains/robo_ttt and "Supervise actions with next-latent prediction"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer