The scene editor is where 3D scenes get shaped — the outliner, the orbit
viewport, and the transform/material panels, all editing the same
scene.design.json state. It opens over a 3D project's preview and edits the
scene live.
The screen
Scene editor from a 3D project opens the editor: the outliner on the left lists the scene's parts, the viewport in the middle shows the object in orbit, and the panels on the right expose the selected part's transform, parameters and materials. The status bar tracks the revision and object count.
Working the scene
- Add primitives — box, sphere and the rest, from the toolbar
- Select a part — in the outliner or the viewport, and the right panels show its transform and parameters
- Transform — move, scale and rotate the part with the controls or the numeric fields
- Materials — the material slots the part uses, color and finish
- Parameters — the procedural fields the object exposes (height, radius, rings, hue, spin)
Edits preview live in the viewport; committing writes scene.design.json as
one undoable step — the scene's state is a document, not a stack of
operations.
Procedural and native
The authoring backend shows on the status bar:
- Procedural — always available; geometry from parameters in
scene.design.json - Native — Blender-backed recipes, when Blender is installed (see Blender)
Procedural edits are the fast path — the parameters are sliders, not vertices. Native adds the heavier recipes when a shape needs real modeling.
Steering a scene
The editor is one tool among the steering set:
- Editor edits — direct parameter, part and material work
- ⌥-click / follow-ups — ask the agent to reshape or relight
- Versions — keep one shape while exploring another
- Tweaks — the sliders the object exposes for fast parameter play
Tip: Edit the parameters before the primitives — "more rings, tighter spin" is a slider move in a procedural scene; hand-moving vertices is for when the shape outgrows its parameters, which is what Blender's for.