> ## 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.

# Events

> Real-time GitHub events delivered to running agents — PR comments, code reviews, CI results, branch updates, and file changes they can react to.

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

## Event types

| Event             | Description                                                      | Typical agent response                       |
| ----------------- | ---------------------------------------------------------------- | -------------------------------------------- |
| `pr_comment`      | Someone commented on the agent's PR                              | Address the feedback                         |
| `pr_review`       | PR review submitted (approved/changes-requested)                 | Fix requested changes                        |
| `ci_result`       | CI check completed (pass/fail)                                   | Investigate failures                         |
| `file_changed`    | Files modified on base branch conflict with agent's changes      | Rebase or merge                              |
| `child_lifecycle` | Child agent state changed (running/complete/failed)              | Process child results                        |
| `notify`          | Free-text message from a human or [director](/concepts/director) | Follow instructions                          |
| `pr_opened`       | New PR opened in a subscribed repo                               | Used by [flight](/concepts/flights) triggers |
| `issue_opened`    | New issue opened in a subscribed repo                            | Used by [flight](/concepts/flights) triggers |
| `pr_labeled`      | Label added to a PR                                              | Used by [flight](/concepts/flights) triggers |
| `pr_lifecycle`    | PR state changed (merged/closed/reopened)                        | Track PR status                              |

## Setting up event delivery

<Note>
  If your org has installed the Macroscope GitHub App, event delivery is automatic — no workflow installation needed.
</Note>

For personal tenants or repos not covered by the App, run [`murmur install-repo`](/cli/install-repo) to create the GitHub Actions workflow that delivers events.

## How agents receive events

Events arrive in the agent's session automatically via the MCP server's channel capability. They appear as `<channel>` tags in the agent's context — no polling required. The agent reads the event and decides how to respond.

## How your local Claude receives events

When you run Claude Code on your laptop with the Murmur MCP server configured, events for your [agents](/concepts/agents) are delivered to your mailbox. Stream them with [`murmur watch`](/cli/watch), or check the dashboard.

## Subscriptions

[Agents](/concepts/agents) subscribe to events automatically — when an agent pushes to a branch, it subscribes to events on that branch. You can also manage subscriptions manually with [`murmur subscriptions add`](/cli/subscriptions-add) and [`murmur subscriptions ls`](/cli/subscriptions-ls).

***

| Type      | Page                                                 |
| --------- | ---------------------------------------------------- |
| Reference | [`murmur watch`](/cli/watch)                         |
| Reference | [`murmur notify`](/cli/notify)                       |
| Reference | [`murmur install-repo`](/cli/install-repo)           |
| Reference | [`murmur subscriptions add`](/cli/subscriptions-add) |
| Concept   | [Flights](/concepts/flights)                         |
| Concept   | [Agents](/concepts/agents)                           |