murmur turns reads the same data from the command line.
Synopsis
slug is optional — omit it to read the turns of the agent resolved from your current context (on a VM, the agent itself).
Arguments
| Name | Type | Required | Description |
|---|---|---|---|
slug | string | no | The agent to read. Accepts the same relative and absolute slug forms as murmur status. Omit to use the current context’s agent. |
--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.
--json, the command prints a JSON array of Turn objects:
Examples
Read an agent’s turns
Read every execution of a slug
--resurrect or --force-new spawn reused the slug.
Read the current agent’s turns on a VM
Errors
| Code | Meaning | What to do |
|---|---|---|
invalid scope | The --scope value is not current or all. | Pass current, all, or omit the flag. |
UNAUTHENTICATED | Identity token is missing or expired. | Run murmur auth or check your murmur.local.yaml. |
Related
murmur status— the agent’s current phase and summarymurmur watch— stream live agent statemurmur session watch— follow the raw session stream- Events — the triggers that start new turns
- Dashboard — the Turns view this command mirrors