murmur ls lists the direct children of the current agent. It does not include the current agent itself or agents outside its subtree.
Account and workspace selectors only narrow results. Discovery requires agent.read from tenant, runtime, or workspace grants, plus applicable workspace access. Grants on individual agents authorize direct access but not discovery. An authorized listing with no matching entries succeeds with an empty result; see listing rules.
Synopsis
Arguments
Output
The default output is a tab-aligned table with six columns:
When no agents match, the command prints no table, writes a
no agents note to stderr (with a hint to use -a when it is not set), and exits successfully.
Quiet mode (-q)
Prints one slug per line with no header. Useful for scripting: pipe to xargs or loop over the result.
JSON mode (-json)
Prints a JSON array of objects. Each object has slug, phase, vm, progress, progress_at, and cost fields, plus dashboard_url and sleep_expired when set. phase is the kebab-case label shown in the table, without the (expired) marker. An empty result produces [], not null.
Examples
List active agents
Include completed agents
List all developers’ agents
SLUG column does not name the owning developer.
List a specific developer’s agents
Slugs only for scripting
JSON output
Child agents on a VM
When running on an agent VM,murmur ls lists child agents spawned by the current agent:
Errors
Related
- Agents: concept overview
murmur status: detailed status for a single agentmurmur kill: cancel an agentmurmur spawn: start an agent