murmur watch CLI command

Streams events for an agent as they arrive. Each event prints on its own line with a timestamp. The stream stays open until you cancel it or the agent completes. On transient connection errors, murmur watch reconnects automatically and resumes from the last received event — no events are missed.

Synopsis

murmur watch [flags] [slug]

On a VM, the slug is optional — omitting it watches the current agent’s own events.

Arguments

Name	Type	Required	Description
`slug`	string	on laptop	The agent’s slug. Optional on VMs (defaults to self).
`--from`	string	no	Resume from 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 line prefixed with a timestamp:

[2026-05-14T18:30:12Z] PR comment from @alice (comment ID 12345):
Fix the nil check on line 42.

With --json, each event prints as a single JSON object per line — one field per event type. 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), check name, commit SHA, and failing jobs.
`file_changed`	List of conflicting files and conflict resolution instructions.
`notify`	The free-text message.
`child_lifecycle`	Child agent slug and new state (running, task-complete, failed, interrupted).
`pr_lifecycle`	PR action (opened, closed, merged, reopened) with title and URL.
`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.

Examples

Watch a running agent

murmur watch fix-auth

[2026-05-14T18:30:12Z] PR comment from @alice (comment ID 12345):
Fix the nil check on line 42.

Address this comment on main.go:42.
[2026-05-14T18:31:05Z] CI result: failure (test-suite) for agent fix-auth — PR: https://github.com/acme/backend/pull/42
Commit: a1b2c3d
Failed jobs: unit-tests
Run: https://github.com/acme/backend/actions/runs/123456

Events stream in real time. Press Ctrl-C to stop.

JSON output for scripting

murmur watch fix-auth --json

{"event":{"prComment":{"author":"alice","body":"Fix the nil check on line 42.","path":"main.go","line":42,"commentId":"12345"}}}

Each line is a standalone JSON object.

Resume from a specific point

murmur watch fix-auth --from 1715710212000-0

Starts streaming from the given entry ID. 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
`NOT_FOUND`	No agent with that slug exists.	Check the slug. Use `murmur ls` to list running agents.
`UNAUTHENTICATED`	Identity token is missing or expired.	Run `murmur auth` 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