Catalog resources

The catalog is Murmur’s per-tenant configuration store. Every configurable entity — workspaces, environments, placements, secrets, agent personas, flights, and more — is a catalog resource.

Resource kinds

Each resource has a kind (its type), a name (unique within the kind and tenant), and kind-specific fields.

Infrastructure

Kind	Purpose
`workspace`	Groups repos, environment, placement, and agent defaults
`placement`	Where VMs run — cloud account, region, network
`environment`	VM compute shape — machine type, disk size
`pool-config`	Tenant-wide VM pool limits (singleton, always named `default`)
`machine-type`	Named VM sizes — vCPUs, memory, architecture
`disk-type`	Disk performance tiers
`image`	VM image records produced by the bake process
`recipe`	Image build definitions — base image, provisioning script
`repo-config`	Per-repository configuration overrides

Agents and identity

Kind	Purpose
`agent-persona`	Reusable persona definitions — prompt, model, tools
`agent`	Runtime record of a spawned agent (created automatically)
`tag`	Tenant-defined label (name + color) attached to agents for grouping and filtering
`share-link`	Read-only link to a single agent, openable without signing in
`flight`	Multi-agent orchestration documents with event triggers
`secret`	Tenant-wide secrets, encrypted at rest
`user-secret`	Per-developer secrets
`user`	Developer identity — name, email, SSH keys
`service-profile`	Service agent identity and credentials
`role`	Named permission sets
`group`	User groups for bulk role assignment
`tenant-binding`	Binds users or groups to roles
`alias`	URL aliases for agent port-proxy endpoints
`canned-response`	Reusable message-and-persona pair for agent follow-ups
`actor-allowlist`	Usernames permitted to steer agents via webhook events
`steering-policy`	Who may steer agents via externally-sourced events

Managing resources

Five CLI commands cover all catalog operations:

Command	Purpose
`murmur get`	Read a resource, or list all resources of a kind when name is omitted
`murmur set`	Create or full-replace a resource. Reads YAML from stdin or opens `$EDITOR`
`murmur patch`	Partial update — change specific fields with `--set field=value`
`murmur rm`	Delete a resource
`murmur describe`	Show the schema for a kind — fields, required values, input format

# List all workspaces
murmur get workspace

# Read a specific workspace
murmur get workspace backend

# Create or update a workspace from stdin
cat workspace.yaml | murmur set workspace backend

# Update one field
murmur patch workspace backend --set min_idle=3

# Delete a workspace
murmur rm workspace backend

# See what fields a kind expects
murmur describe workspace

Versioning

Every catalog edit creates a new generation. The catalog stores the full version history — who changed what, when — and supports reverting to any previous generation.

Referential integrity

Resources reference each other by name. A workspace references an environment, a placement, and secrets. An environment references a machine type. The catalog enforces these references — deleting a resource that another resource points to is blocked.

Platform builtins

Murmur provides built-in resources — default placements, machine types, and base images — that are available to every tenant. Builtins are immutable. You can create your own resources alongside them.

Type	Page
Reference	placement
Reference	`murmur get`
Reference	`murmur set`
Reference	`murmur patch`
Reference	`murmur rm`
Reference	`murmur describe`

​Resource kinds

​Infrastructure

​Agents and identity

​Managing resources

​Versioning

​Referential integrity

​Platform builtins