Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.murmur.dev/llms.txt

Use this file to discover all available pages before exploring further.

The murmur CLI is the primary interface for developers and platform engineers. It manages the full agent lifecycle, infrastructure provisioning, catalog resources, and developer setup.

​
Installation

​
Homebrew

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

​
Verify installation

murmur version

​
Command groups at a glance

GroupKey commandsDescription
Agent lifecyclespawn, kill, sleep, wake, status, ls, waitCreate, monitor, and manage agents
Session interactionsession watch, session send, queue addInteract with running agent sessions
Pool managementpool status, pool up, pool flushMonitor and control the warm VM pool
Catalog operationsget, set, patch, rm, describeCRUD for all 19 catalog resource kinds
Connectivityssh, port-forward, urlSSH into VMs, tunnel ports, get URLs
Secretssecret set, secret ls, secret rmManage KMS-encrypted secrets
Taskstask create, task update, task lsManage agent task checklists
Setupsetup, install, auth, connectDeveloper onboarding and authentication
FanouteachSpawn one agent per line from stdin
Flightsspawn --flight, bake, bakes lsExecute and manage flight documents

​
Configuration resolution

The CLI locates configuration through walk-up directory discovery. Starting from the current working directory, it walks up the filesystem tree looking for a .murmur/ directory containing murmur.yaml. 
/home/alice/projects/api/src/auth/   <-- you are here
/home/alice/projects/api/src/
/home/alice/projects/api/             <-- .murmur/murmur.yaml found here

​
Config files

FilePurposeVCS
.murmur/murmur.yamlShared team configuration (workspace, tenant, defaults)Committed
.murmur/murmur.local.yamlDeveloper-specific encrypted profile (credentials)Gitignored
.murmur/murmur.{context}.yamlNamed context shared configCommitted
.murmur/murmur.{context}.local.yamlNamed context local configGitignored

​
Named contexts

Switch between configurations using the MURMUR_CONTEXT environment variable: 
MURMUR_CONTEXT=staging murmur spawn deploy-fix "Fix the deploy script"
This resolves murmur.staging.yaml (shared) + murmur.staging.local.yaml (local overlay).

​
Environment variable overrides

Any configuration field can be overridden with a MURMUR_* environment variable. The variable name is the uppercase, underscore-delimited path to the field:
VariableOverrides
MURMUR_WORKSPACEworkspace
MURMUR_API_ADDRESSapi.address
MURMUR_MODELmodel
MURMUR_WORKSPACE=backend-team murmur ls

​
Authentication

The CLI authenticates to the Murmur API using identity tokens derived from your GitHub identity.

​
OAuth flow

Run murmur auth to initiate the OAuth flow. The CLI opens a browser for GitHub OAuth authorization, receives a token, and prints export lines: 
murmur auth
# Opens browser for GitHub OAuth
# Outputs:
# export MURMUR_TOKEN="eyJ..."

​
How it works

  1. murmur setup captures your GitHub token via gh auth token
  2. The CLI exchanges the GitHub token for a Murmur identity token
  3. The identity token is stored in your encrypted local config
  4. All subsequent CLI calls include the identity token in the Authorization header

​
Service authentication

For CI/CD and automation, set the token directly: 
export MURMUR_TOKEN="eyJ..."
murmur ls

​
Global flags

These flags are available on every command:
FlagShortDescription
--workspace-wOverride the workspace name from config
--configPath to a specific config file (skips walk-up discovery)
--contextNamed context (equivalent to MURMUR_CONTEXT)
--verbose-vEnable verbose output for debugging
# Override workspace for a single command
murmur ls --workspace backend-team

# Use a specific config file
murmur status my-agent --config /path/to/murmur.yaml

​
Output formats

Most listing commands support machine-readable output: 
murmur ls --json           # JSON array of agents
murmur ls -q               # Slugs only, one per line (for scripting)
murmur status my-agent     # Human-readable table

murmur spawn

The most important command — create agents.

Agent Management

Monitor, control, and interact with running agents.

Setup & Auth

First-time developer onboarding.

Catalog Operations

CRUD for all platform resources.