Docs

Build, send, watch, fix.

Guides for the Unity package, the Launcher, Studio and the command line, and the reference behind them.

Start here

~10 min

Record your first playtest

Add the package, mark two moments, record yourself, open it in Studio.
~15 min

Send a build to testers

Push to a branch, make a campaign, mint codes, and send testers the Launcher.
~8 min

Review a session

The timeline, notes and drawings, and links for your tracker.

Guides

Getting startedWhat works today, then the shortest path
SamplesA Unity script, prompts for Claude, a CI job
Push a buildUnity, mulno build push, branches
The Launcher and the web zipHow a tester gets a build
Your own bucket and the lent keyR2 with the lock rule, and what we may read
Review in the browserThe web app, sign-in, who can read what
Moment links and trackersCopy for Jira, Trello, Markdown
Apply notes with an agentA note becomes a commit, and a status
Plans and quotasWhat each plan includes, and the limits
Privacy for studios and testersWho is the controller, and what to do first

AI AND MCP

Give Claude your sessions.

14 tools: nine read, five write notes. Read-only unless you turn writes on.

Connect Claude over MCP
# Studio installed? The plugin finds mulno.exe itself.
claude --plugin-dir .\plugin
# then ask:
> find moments where players got stuck in the latest session

Reference

mulno CLIbuild push, index, search, mcp, transcribe
MCP toolslist_sessions … get_moment, set_note_status
C# APISoonPlaytest.Mark, Span, BeginSpan, Track
PlaytestConfigSoonQuality presets, hotkeys, consent, overlays
Session format v1SoonThe folder every session is: manifest, segments, events
Build format v1SoonChunks, the signed release, changes.json

Stuck? Write to developer@mulno.com with your session ID. Security issues go to security@mulno.com.