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.

Getting your team on Murmur takes minutes. An org admin installs the GitHub App, and each developer runs a single setup command.

​
For the org admin

​
1. Install the Macroscope GitHub App

Install the Macroscope GitHub App on your GitHub organization. This creates your tenant and enables webhook-based event delivery. The GitHub App requests these permissions:
  • Repository contents (read/write) — clone repos, push branches, create commits
  • Pull requests (read/write) — open PRs, comment, review
  • Issues (read) — read issue context for flight triggers
  • Checks (read) — monitor CI status

​
2. Create a workspace

After installation, create a workspace that references your repos: 
cat <<EOF | murmur set workspace my-team
name: my-team
image_ref: default
environment_ref: default
placement: us-central1
repos:
  - clone_url: https://github.com/my-org/my-repo
    base_branch: main
EOF

​
3. Set up event delivery (optional)

For real-time delivery of PR comments, reviews, and CI results to agents: 
murmur install-repo --webhook-url https://webhook.murmur.dev
git add .github/workflows/murmur-events.yaml
git commit -m "Add murmur event pipeline"
git push
If your org uses the GitHub App webhook path, event delivery is automatic — skip this step.

​
For each developer

​
1. Install the CLI

brew install prassoai/tap/murmur

​
2. Authenticate with GitHub

gh auth login

​
3. Run murmur setup

murmur setup
This discovers your GitHub identity, prompts for Claude credentials, generates SSH signing keys, and encrypts everything into .murmur/murmur.local.yaml. That’s it. The developer can now spawn agents: 
murmur spawn test "Create a hello world file" --out pr

​
4. Access the dashboard

Sign in at your organization’s Murmur dashboard URL with GitHub OAuth. No additional setup needed.

​
Revoking access

When a developer leaves the team, remove them from the GitHub org. They immediately lose access to the tenant — the platform checks org membership on every request.

​
Multiple repos

Each repo can have its own .murmur/murmur.yaml pointing to the same tenant but potentially different workspaces. Developers run murmur setup once per repo (or share the same .murmur/murmur.local.yaml across repos).