Destroys idle (warm) VMs in the pool. The pool workflow then replenishes with fresh VMs built from the current base image. Running agents are not affected — only warm VMs waiting for assignment are deleted. Use this after changing an environment configuration or baking a new image, so that newly spawned agents pick up the changes.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 |
|---|---|---|---|
--nuke | bool | no | Terminate all agent workflows and delete all VMs, not just warm ones. Default: false. |
--workspace | string | no | Workspace name. Overrides the value from murmur.yaml. |
Output
Without--nuke, prints the number of warm VMs flushed:
--nuke, prints the total number of workflows terminated and VMs deleted:
Examples
Flush warm VMs after a new image bake
Nuclear reset
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.delete 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 status— check the current pool statemurmur pool up— ensure the pool is running after a flushmurmur kill— cancel a single agent (use instead of--nukefor targeted cleanup)