Synopsis
Arguments
| Name | Type | Required | Description |
|---|---|---|---|
slug | string | yes | The agent’s slug. |
strategy | string | yes | One of auto, all, one, or five. See Strategies below. |
--workspace | string | no | Workspace name. Overrides the value from murmur.yaml. |
Strategies
| Value | Behavior |
|---|---|
auto | Drain up to five follow-ups of one kind per turn; manual follow-ups and auto-generated events (PR comments, CI results, conflict resolutions) never share a turn. Default. |
all | Drain all queued follow-ups into one batch. |
one | Drain one follow-up per turn. |
five | Drain up to five follow-ups per turn. |
Examples
Drain one follow-up per turn
Restore the default behavior
Errors
| Code | Meaning | What to do |
|---|---|---|
NOT_FOUND | No agent with that slug exists. | Check the slug. Use murmur ls to list running agents. |
UNAUTHENTICATED | Identity token is missing or expired. | Run murmur auth or check your murmur.local.yaml configuration. |
invalid strategy | The strategy value is not auto, all, one, or five. | Pass one of the supported strategies listed above. |
Related
- Agents — concept overview
murmur queue add— send a follow-up to an agentmurmur queue clear— discard all queued follow-upsmurmur queue conflict-resolution— set per-repo conflict handlingmurmur status— check an agent’s phase and queue