Genie and Interactive Generated Environments › Genie and Interactive Generated Environments
World Models HandbookAll chapters Genie and Interactive Generated Environments › Genie and Interactive Generated EnvironmentsOne section · Sections in this chapter1 / 9 ↓
Reading tools Definitions & inline links
Choose your expertise level to adjust how many terms are explained. Beginners see more tooltips, experts see fewer to maintain reading flow. Hover over underlined terms for instant definitions.
Article links
Make inline references clickable
Picture a short video clip of a cartoon character standing on a grassy platform. The scene looks coherent: shadows line up, the sky matches the grass, and the character's idle animation loops naturally. Now imagine trying to play that clip. You press an arrow key, and the character turns. You press another, and it jumps. You press a third, and it stops against a rock that was already in the background. You walk to the left edge of the platform, turn around, and the same rock is still there, in the same place, with the same shadow. You have not watched a video. You have interacted with a small, generated world.
That experience, a machine-learned environment that accepts a stream of actions and produces a consistent stream of observations in response, is the target of this chapter. The original Genie model (Bruce et al., 2024) learned a discrete latent-action interface from video without recorded button presses. Genie 2 (2024) and Genie 3 (2025) are later Google DeepMind releases that report image-prompted 3D environments and text-prompted real-time interaction, respectively. Their control interfaces and training details should not be assumed to match the original architecture.
The key shift is not simply that these models generate video. The generated frames sit inside an interaction loop: an action changes what the model generates next. When a real environment and a fixed action sequence are available, a generated rollout can be compared with its reference trajectory, as we do in the toy experiment below. For open-ended generated worlds there may be no unique reference for every branch, so we must also test responsiveness, persistence, and control through interventions. That evaluation difference matters as much as the architecture.
The toy seeds its random generators and computes model-comparison diagnostics and figures from fitted outputs and simulator reference trajectories. The feedback-gain figure is a separate seeded scalar illustration. Its prose describes the seeded configuration shown here; after changing the grid, horizon, or codebook size, rerun the cells and revisit the prose as well. A Key Parameters summary at the end records the settings.
We have already met video generators as candidate world models in Video Generators as Candidate World Models. That chapter used an occluded moving object, timed actions, matched-initial-state branches, and horizon-resolved error to ask whether a generator responds to actions. Genie adds the missing-label problem: how can video without recorded controls supply an action interface? We will trace the original model's answer, then test in a small grid world where inferred codes, true actions, and reference trajectories can all be compared.
It helps to separate four things that are often blurred together when people talk about the quality of a learned world model. Predictive fidelity asks whether the next observation is close to the real next observation. Representation quality asks whether the internal codes or tokens preserve the structure that matters for control. Uncertainty quality asks whether the model knows when it is guessing. Decision usefulness asks whether a planner or policy can achieve goals by using the model. Genie-style systems touch all four, but they do not optimize all four in the same way. The inverse model is mainly about representation and action abstraction. The forward model is mainly about predictive fidelity. The interaction loop is where decision usefulness is tested, and it is also where uncertainty and consistency failures become most visible. Keeping these axes separate will make the rest of the chapter easier to read.