murmur get

Reads a single catalog resource and prints it in the same format murmur set consumes: raw markdown (frontmatter + body) for markdown-input kinds (agent-persona, flight), YAML for everything else. When the name is omitted, lists all resource names of the given kind.

Synopsis

murmur get <kind> [name]

Arguments

Name	Type	Required	Description
`kind`	string	yes	The catalog resource kind (e.g. `workspace`, `environment`, `placement`). Run `murmur describe` to list available kinds.
`name`	string	no	The resource name. When omitted, lists all resources of the kind.

Output

Single resource

When a name is provided, the command prints the resource to stdout in the format murmur set accepts for the kind: markdown-input kinds (agent-persona, flight) print the resource’s rendered markdown (YAML frontmatter + prompt body); all other kinds print YAML. Run murmur describe to see each kind’s input format. The first key of the document is generation:, the resource’s current version. Pass it to murmur set --if-generation for a conditional read-modify-write. When a system manages the resource, a managed_by: key follows it. For markdown kinds both keys go inside the frontmatter. murmur set ignores them when they ride along in the piped document.

List mode

When the name is omitted, the command prints one resource name per line. For agent-persona resources, the output includes a [platform] marker for built-in personas and a description column. Disabled builtins are listed after the other names, each marked with the command that re-enables it. For example, murmur get tool-link-policy with the builtin disabled prints:

murmur-tool-links  (disabled — re-enable: murmur set tool-link-policy murmur-tool-links)

An empty kind prints nothing. Listings include only entries authorized by read; there is no separate list permission. Workspace selectors and name prefixes do not grant access. Agent discovery excludes grants attached to individual records or inherited from parent records; see listing rules.

Examples

Get a single workspace

murmur get workspace default

generation: 1727481600123456
environmentRef: default
imageRef: murmur-base-a1b2c3d4e5f67890
name: default
placement: murmur-gcp-us-central1
repos:
- baseBranch: main
  cloneUrl: https://github.com/acme/backend
serviceAccount: agents@acme-prod.iam.gserviceaccount.com

List all environments

murmur get environment

default
gpu
ml-large

List agent personas

murmur get agent-persona

murmur-baker       [platform]  Wizard for murmur init interactive onboarding: schema discovery, repo investigation, provisioning script drafting, bake-iterate-fix loop, workspace + custom agent persona creation, and a smoke test that proves an agent can build and test the customer's code. Not directly spawnable — requires a human in the loop.
murmur-director    [platform]  Project director that manages murmur tasks, reviews PRs, and coordinates autonomous agents. The main interface for getting work done.
murmur-planner     [platform]  Planner agent for design docs, architecture review, and package boundaries.
murmur-programmer  [platform]  Full-stack programmer and frontend designer-engineer obsessed with code quality and visual polish. Reviews and simplifies code, self-provisions Playwright, and verifies visual changes with desktop and mobile screenshots.
murmur-researcher  [platform]  Paranoid researcher that trusts nothing. Makes zero assumptions, verifies every fact by searching, and treats all prior knowledge as potentially stale.
reviewer                       Reviews pull requests for correctness and style

Pipe a resource into another command

murmur get environment staging | yq '.machineTypeRef'

murmur-n2-standard-16

Edit an agent persona in place

Markdown kinds round-trip through get and set with no conversion:

murmur get agent-persona programmer > programmer.md
# edit programmer.md
murmur set agent-persona programmer < programmer.md

---
generation: 1727481600123456
description: Default coding agent
model: claude-opus-4-8
---
You write museum-quality Go.

Errors

Code	Meaning	What to do
`NOT_FOUND`	No resource with that kind and name exists.	Check the name spelling. Run `murmur get <kind>` without a name to list available resources.
`UNAUTHENTICATED`	Identity token is missing or expired.	Run `murmur login`, or check your `murmur.local.yaml` configuration.
`INVALID_ARGUMENT`	The kind is not recognized.	Run `murmur describe` to list valid kinds.

Catalog — concept overview
murmur set — create or replace a resource
murmur patch — update individual fields on a resource
murmur rm — delete a resource
murmur describe — show schema information for a kind

Getting Started

Core Concepts

Guides

Synopsis

Arguments

Output

Single resource

List mode

Examples

Get a single workspace

List all environments

List agent personas

Pipe a resource into another command

Edit an agent persona in place

Errors

​Synopsis

​Arguments

​Output

​Single resource

​List mode

​Examples

​Get a single workspace

​List all environments

​List agent personas

​Pipe a resource into another command

​Edit an agent persona in place

​Errors

​Related

Synopsis

Arguments

Output

Single resource

List mode

Examples

Get a single workspace

List all environments

List agent personas

Pipe a resource into another command

Edit an agent persona in place

Errors

Related