Prints the current state of your tenant’s pool. Shows how many warm VMs are available and lists each one by name and task queue.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.
Synopsis
Pool commands run from your laptop only. They are not available on agent VMs.
Arguments
| Name | Type | Required | Description |
|---|---|---|---|
--workspace | string | no | Workspace name. Overrides the value from murmur.yaml. |
Output
The output starts with awarm: count line, followed by one indented line per warm VM.
| Field | Description |
|---|---|
warm | Total number of warm VMs in the pool. |
| Per-VM line | The VM’s instance name and task queue. |
Examples
Pool with warm VMs
murmur spawn claims one instantly.
Empty pool
murmur spawn triggers a cold boot, which takes longer. Use murmur pool up to ensure the pool is running and backfilling.
Errors
| Code | Meaning | What to do |
|---|---|---|
UNAUTHENTICATED | Identity token is missing or expired. | Run murmur auth or check your murmur.local.yaml configuration. |
PERMISSION_DENIED | Your role does not have pool-config.read permission. | Ask a tenant admin to grant you the required permission. |
| (exit error) | pool commands are not supported on VMs | Run this command from your laptop, not from an agent VM. |
Related
- Pools — concept overview
pool-config— catalog resource that controls pool capacity limitsmurmur pool up— ensure the pool is runningmurmur pool flush— destroy warm VMs so the pool replenishesmurmur spawn— start an agent (claims a warm VM from the pool)murmur ls— list running agents