Skip to content
PuniDocs
Open Puni

Surfaces

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

One scene reached from the studio, a share page, a creator page, an embed, the command line and agentsStudioedit, at /p/<scene>Share pageone saved versionCreator pageyour listed linksEmbedthe player in a host pageCommand linethe same engineAgentsMCP, with a token01One scenerevision 8, savedeach surface keeps its own controls; the document is the sameOne scene reached from the studio, a share page, a creator page, an embed, the command line and agentsStudioedit, at /p/<scene>Share pageone saved versionCreator pageyour listed linksEmbedthe player in a host pageCommand linethe same engineAgentsMCP, with a token01One scenerevision 8, savedeach surface keeps its owncontrols
One scene; six places to meet it. Each keeps its own controls.

Guides

The studioA tour of the editor: the bar, the objects rail, the stage, the inspector, the timeline, and the palette that reaches everything.The share pageWhat a link opens: the player and its controls, the scene menu, downloads, remixing, and the small differences on a phone.Creator pagesYour live links under one handle at puni.design/u/handle: turning the page on, choosing a handle, and choosing which links show.EmbeddingPut 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 linePreviewThe same engine as the studio in a terminal: make and edit scenes as files, render, and work with your library and agents.

One scene, several places to meet it. Each surface keeps its own controls and says what it can do.

#For making

The studio is the editor on the web. The command line is the same engine in a terminal.

#For showing

The share page is what a link opens. Creator pages collect your live links under one handle. Embedding puts the player inside another page.

Start with The studio for a tour of the editor.