murmur watch CLI command

Streams events for an agent as they arrive. Each event prints as its own message, prefixed with the event’s timestamp when it carries one. The stream stays open until you cancel it with Ctrl-C. On any stream error or disconnect, murmur watch reconnects automatically with backoff and resumes from the last received event. No events are missed.

Synopsis

murmur watch [flags] [slug]

On a VM, the slug is optional. If you omit it, the command watches the current agent’s own events.

Arguments

Name	Type	Required	Description
`slug`	string	on laptop	The agent’s slug. Accepts the same relative and absolute path forms as `murmur status`. Optional on VMs (defaults to self).
`--from`	string	no	Resume after a specific stream entry ID. Default: `"0"` (all events).
`--json`	bool	no	Output raw JSON, one event per line. Default: `false`.
`--workspace`	string	no	Workspace name. Overrides the value from `murmur.yaml`.

Output

By default, each event prints as a human-readable message prefixed with its UTC timestamp:

[2026-05-14T18:30:12Z] PR comment from @alice (acme/backend#42, comment ID 12345):
Fix the nil check.

PR comments, PR reviews, and merged-PR events end with an Instructions: block. For a PR comment, the block carries the exact command for replying or resolving. Progress messages carry no timestamp. With --json, each event prints as a single WatchEventsResponse JSON object per line: the stream entry id plus either event (with one field set for the event type) or progress. Useful for piping into jq or other tooling.

Event types

Type	What prints
`pr_comment`	PR comment body, author, file path and line (if inline), and resolution instructions.
`pr_review`	Review body, author, and state (approved, changes requested, commented).
`ci_result`	CI conclusion (success, failure, neutral, skipped, cancelled) or check state (queued, in progress), check name, repo and branch, commit SHA, and run URL.
`file_changed`	Repo, base-branch commit, conflict resolution advice, and the list of changed files.
`notify`	The free-text message.
`child_lifecycle`	Child agent slug and new state (running, task-complete, failed, pr-merged, pr-closed, destroyed, interrupted), with any error and the follow-ups that triggered it.
`pr_lifecycle`	PR action with title and URL, plus the merge commit for a merged PR.
`pr_labeled`	PR number, labels, title, and URL.
`issue_opened`	Issue number, repo, and body.
`issue_labeled`	Issue number, labels, title, and URL.
`pr_opened`	Branch, repo, and body.
`progress`	Agent progress text, as `[progress] <text>`.

Retry notices (usage limits, VM timeouts, preemptions) print their message and the retried input. An event type the CLI has no formatter for prints Unhandled event: <type>.

Examples

Watch a running agent

murmur watch fix-auth

[2026-05-14T18:30:12Z] PR inline comment from @alice on main.go:42 (acme/backend#42, comment ID 12345):
Fix the nil check.

Instructions:
Address this comment on main.go:42 individually — reply to the thread, or resolve it if addressed; do not leave an addressed thread open. ...
[2026-05-14T18:31:05Z] CI result: failure (test-suite) for agent fix-auth
Repo: acme/backend (branch murmur/fix-auth)
Commit: a1b2c3d
Run: https://github.com/acme/backend/actions/runs/123456

The ... stands for the reply and resolve commands, which are elided here. Events stream in real time. Press Ctrl-C to stop.

JSON output for scripting

murmur watch fix-auth --json

{"id":"1715710212000-0","event":{"eventTime":"2026-05-14T18:30:12Z","prComment":{"repo":"acme/backend","author":"alice","body":"Fix the nil check.","commentId":"12345","path":"main.go","line":42,"prNumber":42}}}

Each line is a standalone JSON object.

Resume from a specific point

murmur watch fix-auth --from 1715710212000-0

Starts streaming after the given entry ID (the id field of a --json line). Use this to resume a watch session without replaying earlier events.

Self-watch on a VM

When running on an agent VM, omit the slug to watch the current agent’s own events:

murmur watch

Errors

Code	Meaning	What to do
`watch events: ...`	The slug could not be resolved to an agent (for example `invalid target path "a//b"`). Stream errors after the watch starts are retried, not reported.	Check the slug. Use `murmur ls` to list running agents.
`UNAUTHENTICATED`	Identity token is missing or expired.	Run `murmur login` or check your `murmur.local.yaml` configuration.

Events: concept overview of event types and delivery
murmur status: check an agent’s phase and progress
murmur notify: publish a message to an agent
murmur ls: list running agents

Getting Started

Core Concepts

Guides

murmur watch CLI command

Synopsis

Arguments

Output

Event types

Examples

Watch a running agent

JSON output for scripting

Resume from a specific point

Self-watch on a VM

Errors

​Synopsis

​Arguments

​Output

​Event types

​Examples

​Watch a running agent

​JSON output for scripting

​Resume from a specific point

​Self-watch on a VM

​Errors

​Related

Synopsis

Arguments

Output

Event types

Examples

Watch a running agent

JSON output for scripting

Resume from a specific point

Self-watch on a VM

Errors

Related