# Puni documentation

> Puni is a 3D motion editor for people and their agents: objects, scenes and motion you make by hand, by describing, or through an agent that works in the same studio.

These guides cover the studio on the web, the share and creator pages, the command line, and the tools an agent gets over MCP.

- [Complete documentation corpus](https://puni.design/docs/llms-full.txt): Every public guide in one text response.
- [Documentation home](https://puni.design/docs): Start from the six areas.

## Home

Your first scene start to finish, then the things every scene is made of: objects, motion, materials and light, and the link you share.

- [Puni 101](https://puni.design/docs/home/puni-101.md): Your first scene, start to finish: describe it, shape one object, give it motion, save, and share a link.
- [Scenes and the library](https://puni.design/docs/home/scenes.md): Where your scenes live, what a tile shows, how versions and checkpoints are kept, and how to find, archive and search scenes.
- [Objects and modules](https://puni.design/docs/home/objects.md): An object is an instance of a module: a shape, an outline, a curve, an imported file, text, a mark, a cloner, a shader, an interface, a fitting or a group.
- [Motion](https://puni.design/docs/home/motion.md): The timeline, actions, tracks and clips; behaviors that give an object life; responses to a tap; cameras, shots and audio.
- [Materials and light](https://puni.design/docs/home/materials-and-light.md): The skin of an object and the stage it stands on: materials, colour, finish, lighting presets, exposure, background and shadows.
- [Sharing](https://puni.design/docs/home/sharing.md): A link opens the exact version you shared. What a viewer can do, what remixing allows, the scene menu, the embed, and your creator page.

## Make

The deeper workflows: bringing files in, rendering stills and films, versions and checkpoints, and the pictures a scene carries.

- [Import](https://puni.design/docs/make/import.md): Bring a GLB, an SVG, a picture, a LEGO model, a Paper layout or a portable Puni file into a scene, and what each one becomes.
- [Rendering](https://puni.design/docs/make/rendering.md): Three ways to draw a scene: the studio's own renderer in your browser, its path tracer for a finer still, and Blender Cycles on your Mac.
- [Films](https://puni.design/docs/make/films.md): Turn a scene's motion into an MP4: Puni's film service where it is offered, the local renderer for films with sound, and the limits of each.
- [Versions and checkpoints](https://puni.design/docs/make/versions.md): How saving works: revisions, the checkpoints that are kept, restoring, and what happens when two places edit one scene.
- [Covers and pictures](https://puni.design/docs/make/covers-and-pictures.md): What a scene's cover is, when the studio takes it, and the picture, GIF, video and scene package a share page can hand out.

## Agents

Connect Claude, Codex, Cursor or ChatGPT to your library, and understand what an agent can and cannot see.

- [Connected runners](https://puni.design/docs/agents/ask-puni.md) [preview]: Deliver scene turns to an agent running on your own machine.
- [Connect Puni](https://puni.design/docs/agents/connect.md) [preview]: Connect ChatGPT, Claude, Cursor, Grok or Grok Bot to Puni, choose access, and make your first saved scene and picture.
- [Scopes and tokens](https://puni.design/docs/agents/scopes-and-tokens.md): What a device token is, the access choices, how long a token lives, and how to keep and revoke one.
- [Prompts](https://puni.design/docs/agents/prompts.md): Requests that work well with connected runners and with an MCP agent, and the working loop that keeps an agent honest.
- [How agents see](https://puni.design/docs/agents/how-agents-see.md): Agents inspect structure and numbers; only a render shows the picture. What that means for ChatGPT's browser, blind builds, and covers.
- [Plugins and skills](https://puni.design/docs/agents/plugins-and-skills.md) [preview]: What exists today for teaching a coding client about Puni, and how a skill differs from a connected tool.

## Surfaces

Where Puni shows up: the studio, the share page, your creator page, an iframe in someone else's product, and the command line.

- [The studio](https://puni.design/docs/surfaces/studio.md): A tour of the editor: the bar, the objects rail, the stage, the inspector, the timeline, and the palette that reaches everything.
- [The share page](https://puni.design/docs/surfaces/share-page.md): What a link opens: the player and its controls, the scene menu, downloads, remixing, and the small differences on a phone.
- [Creator pages](https://puni.design/docs/surfaces/creator-page.md): Your live links under one handle at puni.design/u/handle: turning the page on, choosing a handle, and choosing which links show.
- [Embedding](https://puni.design/docs/surfaces/embed.md): Put the player inside another page with the copied iframe, size it, hide the header, and know what the host page can and cannot do.
- [The command line](https://puni.design/docs/surfaces/command-line.md) [preview]: The same engine as the studio in a terminal: make and edit scenes as files, render, and work with your library and agents.

## Developers

The command line, the MCP tools, the scene document and its commands, the HTTP API, and the embed protocol, from the quickstart to the reference.

- [Quickstart](https://puni.design/docs/developers/quickstart.md) [preview]: Build the command line, make a scene from a study, change it with one command file, evaluate it, render a PNG, and push it to your library.
- [Setup](https://puni.design/docs/developers/setup.md) [preview]: What the command line needs: Node, Chrome for renders, the local renderer for films and Cycles, where credentials live, and what each exit code means.
- [The scene document](https://puni.design/docs/developers/scene-document.md): The shape of a saved scene: frame, modules, instances, actions, tracks, clips, cameras, shots and audio, and how the pieces refer to each other.
- [Commands](https://puni.design/docs/developers/commands.md): Every edit is a command on the document: the thirty-four kinds, atomic batches, command files, and one cloner for many copies.
- [Evaluate and simulate](https://puni.design/docs/developers/evaluate-and-simulate.md): Sample a scene at a time for the values of everything in it, and record physics into motion the document keeps.
- [Portable projects](https://puni.design/docs/developers/portable-projects.md): The .puni.json file: what it contains, how export and import validate it, and how pull and push move a scene between a file and the library.
- [MCP tools reference](https://puni.design/docs/developers/mcp-tools.md): Every tool Puni's MCP server mounts, with its arguments from the source schema, what it returns, and a call and response for each.
- [API](https://puni.design/docs/developers/api.md): The HTTP routes behind the studio and the command line: projects, transfers, assets, links, devices, agent turns, search and films.
- [The embed protocol](https://puni.design/docs/developers/embed-protocol.md): The message API a host page can opt into: connect to the player, inspect controls, set a parameter, seek, play, pause, trigger and reset.
- [WebMCP](https://puni.design/docs/developers/webmcp.md) [preview]: The tools Puni's pages register in a browser that supports WebMCP, the loop they follow, and the one thing the browser must have.
- [Command line](https://puni.design/docs/developers/cli.md) [preview]: Every command group in puni, the flags they share, how remote commands name their origin, and where the exit codes are.
- [Auth commands](https://puni.design/docs/developers/cli-auth.md) [preview]: Sign a machine in to your library and keep its token.
- [Scene commands](https://puni.design/docs/developers/cli-scene.md) [preview]: Make, inspect, edit, evaluate and validate a scene as a file.
- [Project commands](https://puni.design/docs/developers/cli-project.md) [preview]: Your library: list, pull, push, rename, archive, checkpoints, covers and links.
- [Render commands](https://puni.design/docs/developers/cli-render.md) [preview]: Draw a scene file with the studio's own renderer: a PNG, a GLB, a USDZ, or a film.
- [Renderer commands](https://puni.design/docs/developers/cli-renderer.md) [preview]: Talk to the local renderer: Cycles stills from a GLB, and film jobs.
- [Search commands](https://puni.design/docs/developers/cli-search.md) [preview]: Find scenes by name and description, and manage what semantic search knows.
- [Checkpoint commands](https://puni.design/docs/developers/cli-checkpoint.md) [preview]: Keep and restore a scene file with its assets and checksums.
- [Agent commands](https://puni.design/docs/developers/cli-agent.md) [preview]: Deliver a turn to a connected runner, host its turns on your own machine, and read what each turn saved.
- [Interface commands](https://puni.design/docs/developers/cli-interface.md) [preview]: Turn a Paper layout into an interface object.
- [Studies commands](https://puni.design/docs/developers/cli-studies.md) [preview]: The starting scenes `scene create` can begin from.
- [Runtime commands](https://puni.design/docs/developers/cli-runtime.md) [preview]: Check that this build of the command line matches the studio.
- [Contract commands](https://puni.design/docs/developers/cli-contract.md) [preview]: Print the command and type contract a scene is made of.
- [Sculpt commands](https://puni.design/docs/developers/cli-sculpt.md) [preview]: Sculpt from consistent reference views, retain the provider master, and derive a scene-ready mesh.
- [Mono commands](https://puni.design/docs/developers/cli-mono.md) [preview]: Puni's own agent runtime, embedded in the command line: a session that can look at a scene before it answers.

## Account

Security and privacy, keyboard shortcuts, fixes for common problems, the meaning of every product noun, and what changed.

- [Security and privacy](https://puni.design/docs/account/security.md): Where your scenes and assets live, who can read a link, what a device or an agent can do, and how to cut one off.
- [Keyboard shortcuts](https://puni.design/docs/account/shortcuts.md): The keys Puni answers to: library, scene, stage and time. The same list lives in Settings → Shortcuts.
- [Troubleshooting](https://puni.design/docs/account/troubleshooting.md): The common failures, surface by surface, and what to do about each.
- [FAQ and glossary](https://puni.design/docs/account/faq-and-glossary.md): The questions people ask first, then every product noun with its meaning.
- [Release notes](https://puni.design/docs/account/release-notes.md): What changed in Puni, newest first.
- [Provider keys](https://puni.design/docs/account/providers.md): Choose your own OpenAI and fal keys, verify or remove them, and recover when a provider cannot run.
- [Credits](https://puni.design/docs/account/credits.md): What Puni-paid generation costs, how welcome credits work, and where to see purchases, refunds and activity.
- [Profile and sign-in](https://puni.design/docs/account/profile.md): Update your name and picture, verify an email address, and manage the connected accounts offered in Settings.
- [Devices](https://puni.design/docs/account/devices.md): Sign a terminal into your library, check its access and expiry, and disconnect or reconnect a machine.