WorldStream Builds an Endless 3D World and Remembers Every Player Edit
Researchers have introduced WorldStream, an open 3D-world model. It extends playable terrain beyond any predefined map, executes free-form text commands, and returns visited places together with the player's edits. At its core is a hierarchical planner. Macro defines settlements, ecology, transport, and hydrology for a group of tiles, while Micro refines the semantics of each individual tile. Deterministic code assembles the terrain, roads, and objects, and a single world record stores the plans, object identities, and state. • Plans are built ahead along a predicted movement corridor • Geometry behind the player is freed • NPCs update their state as they act
AI-processed from Hugging Face Daily Papers; edited by Hamidun News
The authors of WorldStream have built a 3D-world model that handles three tasks usually solved separately. It extends playable territory beyond the borders of any predefined map, executes free-form language commands in a world that is already running, and returns visited places with all the edits made to them. Planning runs on two levels, Macro and Micro, and the geometry itself is built not by a neural network but by deterministic code. The work appeared in Hugging Face Daily Papers.
Two planners and a compiler instead of head-on generation
WorldStream does not draw the world in pixels and does not output a finished mesh. The model produces a structured decision according to a typed schema, and everything else is assembled from that decision. This shapes the architecture.
Macro works at the level of a group of tiles and fixes the big things: where settlements stand, what the region's ecology is, how transport runs, and how the hydrology is laid out. This is where the system decides that a river will not break off at the seam between two pieces of the map, and that a road will lead somewhere. Micro takes this contract and specializes it down to the semantics of an individual tile. It takes into account the measured terrain and the commitments that neighboring tiles have already made.
Then local deterministic code takes over. It compiles the accepted plans into terrain, roads, settlements, vegetation, and entities. This setup makes results reproducible: with the same plans and seed, you get the same output.
Streaming with different horizons
The main engineering idea is that different stages have different ranges. Plans run far ahead along the predicted corridor of the player's movement. Compilation starts only where movement will soon require geometry. Everything left behind the user is freed from memory.
As a result, the world grows within limited budgets. The cheap level (the plan) looks far ahead, while the expensive one (geometry) stays close to the player. For an open world this is ordinary streaming logic, just applied to a generative model.
One world record instead of hidden memory
The most practical part of the work is the single world record. It holds plans, seeds, object identities and their mutable state, boundary commitments between tiles, and edits tracked by attribute. The record updates as the player moves forward and changes things. When the player returns, tiles are recompiled from the record rather than reconstructed from the model's vague "memory."
In other words, the system stores the recipe of the world and the deltas on top of it, not the finished geometry. That is where the persistence comes from: a felled tree or a built road will not vanish when the player comes back.
The same record serves as the basis for interaction. The model can act on existing entities, including NPCs whose state updates as they act. It can edit the current region or bind an intent to regions that have not been planned yet.
System components
• Planner: two levels, Macro (group of tiles) and Micro (individual tile), built on a typed decision model • Macro fixes: settlements, ecology, transport, hydrology • Micro accounts for: measured terrain and accepted commitments from neighbors • Assembly: deterministic local code (terrain, roads, settlements, vegetation, entities) • Streaming: plans ahead along the corridor, compilation on demand, geometry behind the player is freed • State: a single record with plans, seeds, object identities, and attribute-level edits
Where it could be useful and what to check
The first candidates for adoption are game studios and prototyping tools. A world that extends itself around the player, understands text commands, and keeps edits fits sandboxes, procedural RPGs, and level editors. The second scenario is simulation environments for training agents: a structured world record is easier to replay and debug than the hidden state of a video model.
Three things deserve attention in evaluation. The first is consistency at the borders of independently planned tiles over long sessions. The second is how the world record grows if the player changes the environment heavily. The third is how the planner behaves on unusual commands, when the intent is bound to a region that has not been planned yet. That is where it will become clear whether the hierarchy keeps its promise to "expand under a limited budget" without losing coherence.
- Oct 27, 2026S3AC brings the critic back to RL for LLMs: gains from 1.5B to 397B parameters
- Oct 27, 2026Skill∞: an agent improves its own skills and its own meta-skill, 60.7% on SkillsBench
- Oct 27, 2026A 12-Author Review Charts How to Trust AI That Improves Itself
- Oct 27, 2026Work Agents: 16 Researchers Build a Unified Coordinate System for AI Agents
Key Questions Answered
What are the key details on Two planners and a compiler instead of head-on generation?
WorldStream does not draw the world in pixels and does not output a finished mesh. The model produces a structured decision according to a typed schema, and everything else is assembled from that decision. This shapes the architecture. Macro works at the level of a group of tiles and fixes the big things: where settlements stand, what the region's ecology is, how transport runs, and how the hydrology is laid out. This is where the system decides that a river will not break off at the seam between two pieces of the map, and that a road will lead somewhere. Micro takes this c
What are the key details on Streaming with different horizons?
The main engineering idea is that different stages have different ranges. Plans run far ahead along the predicted corridor of the player's movement. Compilation starts only where movement will soon require geometry. Everything left behind the user is freed from memory. As a result, the world grows within limited budgets. The cheap level (the plan) looks far ahead, while the expensive one (geometry) stays close to the player. For an open world this is ordinary streaming logic, just applied to a generative model.
What are the key details on One world record instead of hidden memory?
The most practical part of the work is the single world record. It holds plans, seeds, object identities and their mutable state, boundary commitments between tiles, and edits tracked by attribute. The record updates as the player moves forward and changes things. When the player returns, tiles are recompiled from the record rather than reconstructed from the model's vague "memory." In other words, the system stores the recipe of the world and the deltas on top of it, not the finished geometry. That is where the persistence comes from: a felled tree or a built road will not
Build & Ship Production AI Agents Without Boilerplate Code
Start your free 72-hour trial at Hamidun Academy (academy.hamidun.com) — interactive lessons on Claude Code & Cursor, live Tech Radar, and production agent templates.
The AI world, distilled — once a week
Seven stories that actually mattered, hand-picked. No noise, no reposts, no press releases.
Done! Check your inbox for a confirmation.