Installation

The tutorial commands below are validated in CI against the current product — see site/scripts/validate-tutorial.sh and the docs CI workflow. If a command here does not work, that is a product bug, not a typo.

Prerequisites

• Go 1.26+ to build the binary.
• Deno 2.9+ on PATH: the kernel packages and validates every AppRevision by running the application’s TypeScript through Deno (the kernel-owned mandatory CI gate).

No database server, no container runtime, and no Node.js are required.

Build and initialize

# Build the muoto binary from the repository root.
go build -o muoto ./cmd/muoto

# Initialize a fresh instance: creates the SQLite database and bootstraps the
# starter application revision in .muoto/.
./muoto init

init writes:

• .muoto/muoto.db — durable kernel state (work, revisions, leases, audit).
• .muoto/revisions/ — immutable AppRevision artifacts.
• .muoto/state/ — runtime state.

All paths are overridable with --db, --revision-root, and --state-dir, which is how the tutorial validation runs against a disposable instance.

Start the control plane

./muoto serve

The web control surface is now at http://127.0.0.1:6420. Verify it is healthy:

curl http://127.0.0.1:6420/api/health

The kernel runs a revision-specific Deno AppHost per active AppRevision; nothing about running Muoto requires the frontend to be rebuilt.

What you have now

• A bootstrapped starter application: a Todo board with a default workflow.
• The web control surface (board, runtime, repository, mold).
• The muoto mold / muoto unmold / muoto rescue command surface.

Continue with Your first mold.

Status marks

• The MCP adapter (muoto mcp) is experimental and not part of this tutorial.
• The Slack frontend, container, and SSH execution strategies exist as extensions but are not preconfigured by the starter application.