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.

Murmur delivers GitHub events to running agents via a Pub/Sub pipeline. When someone comments on a PR, approves a review, or CI fails, the relevant agent receives the event and can react autonomously.

​
Event pipeline

GitHub event (PR comment, review, CI result)
  → GitHub Actions workflow (murmur-events.yaml)
  → Authenticates to GCP via Workload Identity Federation
  → Publishes to Pub/Sub topic
  → Subscriber routes by branch/slug
  → Event delivered to the agent
  → Agent receives event via MCP channel notification
Alternatively, for orgs using the GitHub App webhook path: 
GitHub event → GitHub App webhook (HMAC-signed) → murmur-webhook → Pub/Sub → agent

​
Event types

EventDescriptionWhen agents react
pr_commentSomeone commented on the agent’s PRAddress the feedback
pr_reviewPR review submitted (approved/changes-requested)Fix requested changes
ci_resultCI check completed (pass/fail)Investigate failures
file_changedFiles modified on base branch conflict with agent’s changesRebase or merge
child_lifecycleChild agent state changed (running/complete/failed)Process child results
notifyFree-text message from a human or directorFollow instructions
pr_openedNew PR opened in a subscribed repoUsed by flight triggers
issue_openedNew issue opened in a subscribed repoUsed by flight triggers
pr_labeledLabel added to a PRUsed by flight triggers
pr_lifecyclePR state changed (merged/closed/reopened)Track PR status

​
Setting up event delivery

For orgs using GitHub Actions event delivery, install the workflow: 
murmur install-repo --webhook-url https://webhook.murmur.dev
This creates .github/workflows/murmur-events.yaml in your repo. The workflow:
  • Fires on PR comments, reviews, and CI completions
  • Extracts the agent slug from the branch name (murmur/<developer>/<slug>)
  • Authenticates to GCP via Workload Identity Federation (no stored secrets)
  • Publishes the event to Pub/Sub
Commit and push the workflow file: 
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 — no workflow installation needed.

​
Branch-based routing

Events are routed to agents by branch name. Murmur agents work on branches matching the pattern murmur/<developer>/<slug>. When a PR comment arrives on a branch with this pattern, the subscriber routes it to the correct agent.

​
Subscriptions

Agents can subscribe to additional event sources beyond their own branch: 
# Subscribe to file changes
murmur subscriptions add my-agent --file src/auth.go --file src/session.go

# Subscribe to a branch
murmur subscriptions add my-agent --branch main

# List subscriptions
murmur subscriptions ls my-agent

​
How agents receive events

Events arrive as MCP channel notifications — real-time push messages that Claude Code processes between tool calls. Each notification includes:
  • Event type (e.g., pr_comment, ci_result)
  • Timestamp — RFC3339 time of the underlying event
  • Content — human-readable formatted message
Agents react based on the event type:
  • PR comment/review: Read the feedback, make changes, resolve review threads
  • CI failure: Investigate failing jobs, fix the code, push
  • File changed: Rebase or merge the base branch
  • Child lifecycle: Check child output, proceed with the plan