A recipe defines how to build a custom VM image for your agents. It pairs a base image with a provisioning script that installs your toolchain — languages, package managers, SDKs, and build tools. When you trigger a bake withDocumentation Index
Fetch the complete documentation index at: https://docs.murmur.dev/llms.txt
Use this file to discover all available pages before exploring further.
murmur bake, the platform creates a scratch VM from the base image, runs your provisioning script, and snapshots the result as a new image. Agents boot from this image, so everything your script installs is available immediately — no install step at spawn time.
Base images
Every recipe starts from a platform base image that includes Debian 12, Git, Node.js, Claude Code, Codex CLI, and thegh CLI. Your provisioning script adds everything else.
Provisioning script
The provisioning script is a shell script that runs as root on the scratch VM during the bake. It installs your toolchain and exits. Anything it installs ends up in the final image. See the custom images guide for examples and best practices.Secret allowlist
If your provisioning script needs credentials — for example, to install packages from a private registry — list the secret names insecret_allowlist. Only listed secrets are available during the bake.
Baking
Trigger a bake withmurmur bake, passing the recipe name, environment, and placement. The resulting image is bound to the placement — a GCE image lives in the placement’s GCP project, an AMI lives in the placement’s AWS account.
See the custom images guide for a full walkthrough.
| Type | Page |
|---|---|
| Reference | recipe |
| Reference | murmur bake |
| Guide | Custom images |
| Concept | Images |
| Concept | Placements |