murmur turns

Prints an agent’s turns: one block per task run, in run order. Each turn shows what triggered the run (your initial prompt, a follow-up, a PR comment, a PR review, a CI result), the agent’s written response, and an error if the run failed. Use it to read back what an agent did and why, without opening the dashboard. A turn is the unit the dashboard’s Turns view renders. murmur turns reads the same data from the command line.

Synopsis

murmur turns [flags] [slug]

On a VM, the slug is optional. If you omit it, the command reads the calling agent’s own turns.

Arguments

Name	Type	Required	Description
`slug`	string	on laptop	The agent to read. Accepts the same relative and absolute path forms as `murmur status`. Optional on VMs (defaults to self).
`--scope`	string	no	Which executions to include: `current` (the latest execution only) or `all` (every execution of the slug). Empty uses the server default for the slug: the current execution for a `--force-new` spawn, all executions otherwise.
`--json`	bool	no	Output the turns as a JSON array of Turn objects instead of formatted text. Default: `false`.
`--workspace`	string	no	Workspace name. Overrides the value in `murmur.yaml`.

Output

Each turn renders as a block: a header with the run number and its start and end times (UTC), the task description, each input with its kind and label, the agent’s response, and an error line if the run failed. An in-flight turn shows (in flight) for its end time, and a turn with no recorded start shows (unknown). A turn that started an execution (the initial spawn, a --force-new, or a --resurrect) carries a [start by <author>] marker in its header, or [start] when no author is recorded.

turn 1  2026-06-09 11:42:10 → 2026-06-09 11:58:04  [start by alice]
  description: Fix the flaky test in auth_test.go
  response:
    Root-caused the flake to a shared clock. Pinned it and pushed the fix.

turn 2  2026-06-09 12:01:05 → 2026-06-09 12:08:33
  input [pr-comment] PR comment from alice
    please also cover the refresh-token path
  response:
    Added a refresh-token case and re-ran the suite. All green.

With --json, the command prints a JSON array of Turn objects:

murmur turns --json fix-auth

[
  {
    "runId": 1,
    "description": "Fix the flaky test in auth_test.go",
    "response": "Root-caused the flake to a shared clock. Pinned it and pushed the fix.",
    "startedAt": "2026-06-09T11:42:10Z",
    "completedAt": "2026-06-09T11:58:04Z",
    "executionStart": true
  }
]

Examples

Read an agent’s turns

murmur turns fix-auth

Read every execution of a slug

murmur turns --scope all fix-auth

Includes turns from prior executions. This is useful after a --resurrect or --force-new spawn reused the slug.

Read the current agent’s turns on a VM

murmur turns

Errors

Code	Meaning	What to do
`unknown scope "<value>" (want "current" or "all")`	The `--scope` value is not `current` or `all`.	Pass `current`, `all`, or omit the flag.
`fetch turns: ...`	The request to the Murmur API failed (for example `NOT_FOUND` for an unknown slug).	Check the slug with `murmur ls` and the cause in the message.
`UNAUTHENTICATED`	Identity token is missing or expired.	Run `murmur login` or check your `murmur.local.yaml`.

murmur status: the agent’s current phase and summary
murmur watch: stream live agent state
murmur session watch: follow the raw session stream
Events: the triggers that start new turns
Dashboard: the Turns view this command mirrors

Getting Started

Core Concepts

Guides

Synopsis

Arguments

Output

Examples

Read an agent’s turns

Read every execution of a slug

Read the current agent’s turns on a VM

Errors

​Synopsis

​Arguments

​Output

​Examples

​Read an agent’s turns

​Read every execution of a slug

​Read the current agent’s turns on a VM

​Errors

​Related

Synopsis

Arguments

Output

Examples

Read an agent’s turns

Read every execution of a slug

Read the current agent’s turns on a VM

Errors

Related