Skip to main content
murmur init is an interactive wizard that turns one or more local repos into a fully provisioned Workspace, including the underlying Recipe, Image bake, and a smoke test.
Run murmur setup first. murmur init reads your tenant config from .murmur/murmur.yaml, which setup creates.

​
Run murmur init

From inside one of the repos your Workspace will span: 
murmur init
The wizard inspects your repo(s), generates a Recipe, bakes the Image, runs a smoke test, and creates or updates the Workspace. The full flow takes 10 to 20 minutes, most of it the unattended bake. You only need to be at the keyboard for the first few minutes. You only need to run init once per Workspace. The wizard will ask you which repos to include, so list every repo your agents need to clone onto the same VM.

Heads up: --dangerously-load-development-channels

Under the hood, murmur init launches Claude Code with --dangerously-load-development-channels server:murmur. The flag opts the session into Claude Code’s channel transport, which Murmur uses to stream real-time events (bake progress, smoke-test status, child lifecycle) into the wizard’s conversation as <channel> tags. Without it the wizard can’t observe the bake-iterate-fix loop and falls back to blind polling.The dangerously- prefix is Claude Code’s wording for an opt-in developer feature, not a security warning specific to Murmur. The same flag is also used by murmur director and by every interactive agent VM that Murmur spawns.When Claude Code prompts you to confirm channels, say yes and opt in. The wizard can’t observe the bake without it.

​
What gets customized

The custom part lives in your Recipe, the shell script the wizard generates and bakes into a VM Image. Typical things to install:
  • Language toolchains beyond Node.js (Go, Python, Ruby, Java)
  • Build tools (Docker, Bazel, make)
  • Private CLIs or SDKs
  • System packages your repos need (libpq-dev, ImageMagick, ffmpeg)
  • Environment variables and dotfiles
See Bake a custom agent Image for the full anatomy of a Recipe.

​
Next steps

Spawn your first agent

Launch an agent into the Workspace you just customized.

Bake a custom agent Image

Edit your Recipe to add tools, libraries, or private dependencies.