Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.murmur.dev/llms.txt

Use this file to discover all available pages before exploring further.

A pool config is a catalog resource that sets tenant-level limits on agent VMs. It is a singleton — every tenant has exactly one pool config, always named default. Changes to pool config take effect immediately. When you update max_vms, the pool recalculates capacity on the next cycle.

​
Fields

NameTypeRequiredDescription
max_vmsint32yesMaximum total VMs (warm + running) across all environments. Must be greater than 0.
descriptionstringnoHuman-readable description shown in the dashboard. Maximum 1024 bytes.
reap_stranded_workflowsstringnoControls automatic cleanup of agent workflows that are stuck on a retired build. Values: dry_run, enabled, disabled. Default when absent: dry_run.

​
reap_stranded_workflows values

ValueBehavior
dry_runDetects stranded workflows and logs them. Does not terminate. This is the default.
enabledDetects and terminates stranded workflows after they have been stranded for 48 hours.
disabledSkips stranded workflow detection entirely.
Unrecognized values are treated as disabled.

​
Examples

​
Setting the pool config

echo 'max_vms: 50' | murmur set pool-config default

​
Updating a single field

murmur patch pool-config default --set max_vms=100

​
Reading the pool config

murmur get pool-config default

max_vms: 50
description: "Production pool limits"
reap_stranded_workflows: dry_run

​
Full resource with all fields

max_vms: 25
description: "Staging tenant pool"
reap_stranded_workflows: enabled

cat <<'EOF' | murmur set pool-config default
max_vms: 25
description: "Staging tenant pool"
reap_stranded_workflows: enabled
EOF

​
Errors

CodeMeaningWhat to do
INVALID_ARGUMENTmax_vms must be positiveSet max_vms to a value greater than 0.
INVALID_ARGUMENTdescription exceeds 1024 byte limit (<n> bytes)Shorten the description field to 1024 bytes or fewer.