Motion projects
Declarative scene graphs — node types, templates, and safe authoring.
A motion project is a declarative scene: a tree of visual nodes whose properties are animated by timeline tracks. Projects render deterministically to PNG frames and MP4.
Node types
| Node | Typical use |
|---|---|
| Text | Titles, captions, animated labels |
| Rectangle | Panels, backgrounds, frames |
| Line | Rules, connectors, separators |
| Chart | Embed a live or snapshotted chart inside the scene |
| Counter | Animated numeric readouts |
| Callout | Highlighted annotations |
| 3D objects | Three-dimensional content via Three.js |
Start from templates
Templates give you a working scene with approved node types, default properties, and animatable fields. Editing a template is the recommended authoring path — especially for agents, which should discover the catalogue rather than invent structures.
No code in the scene
Motion scenes never evaluate JavaScript, expressions, or HTML. What you can express is exactly what the schema allows — which is what makes rendering deterministic and safe.
Revisions and rendering
Accepted edits become immutable revisions. Renders always reference an exact revision: render a single frame to PNG for a quick check, inspect the first, middle, and final frames for animations, and only then commit to a full MP4 render of that revision. See exports.
Programmatic authoring
The catalogue of approved component types and properties is published as a resource for MCP clients — see the MCP guide for the recommended agent workflow.