Skip to main content
Your admin must finish Admin Quickstart before developers can use Murmur.
Murmur setup happens in two stages. Your admin configures the team Workspace once, then each developer sets up Murmur locally. This page covers the developer side.

​
CLI setup

CLI setup requires a GitHub account, the gh CLI (authenticated via gh auth login), and a Claude API key or Anthropic subscription.

​
Step 1: Install the CLI

brew tap prassoai/tap
brew install prassoai/tap/murmur

​
Step 2: Navigate to your repository

cd into the repository where you want your Murmur agents to work.

​
Step 3: Set up

murmur setup
The wizard:
  • Gathers your credentials (GitHub, Claude, optionally OpenAI)
  • Generates an SSH signing key, and optionally uploads the public key to GitHub for verified commits
  • Reads the shared .murmur/murmur.yaml your admin committed and bookmarks the same tenant and Workspace
  • Writes your encrypted personal profile to .murmur/murmur.local.yaml (gitignored)
  • Registers the Murmur MCP with your coding agent (e.g. Claude Code)
When prompted to add the Murmur MCP, say Yes.

​
Next steps

Spawn your first agent

Launch an agent from the dashboard, CLI, or your coding agent.

Core concepts

Agents, Workspaces, Pools, Flights, Events, and the rest of the model.

Flights

Orchestrate multiple agents with declarative Markdown DAGs.

CLI reference

All flags and options for murmur spawn.