murmur queue add CLI command

Sends a follow-up message to a running agent’s queue. The agent picks up queued follow-ups between tasks. Use this to add work after the current task or to steer an idle or sleeping agent. A follow-up wakes a sleeping agent. With --deliver-in or --deliver-at, the message is deferred. It remains in the agent’s durable workflow, survives VM sleep, and is delivered as a normal follow-up at the deadline. This provides a reliable “resume me at T” operation without an in-session timer. The command prints the message’s follow-up ID; cancel an undelivered message with murmur queue remove. A pending deferred message also holds a terminate-on-idle service agent alive until it delivers. Agents started on an older version reject deferral (see Errors).

Synopsis

murmur queue add [flags] <slug> <description>

The description is everything after the slug. Multiple words are joined with spaces.

Arguments

Name	Type	Required	Description
`slug`	string	yes	The agent’s slug.
`description`	string	yes	The follow-up message. All remaining arguments after the slug are joined into the description.
`--agent`	string	no	Override the agent persona for this follow-up (a catalog persona name, e.g. `murmur-programmer`).
`--model`	string	no	Model override for this and subsequent turns (e.g. `claude-opus-4-8`). Sticky, like `--agent`: empty leaves the agent’s current model unchanged. An explicit model overrides the persona’s model, exactly as at `murmur spawn`. Must stay on the agent’s backend (claude vs codex); a cross-backend model is rejected.
`--reasoning-effort`	string	no	Reasoning-effort override for this and subsequent turns. Sticky, like `--model`: empty leaves the current effort unchanged. Claude: `low`, `medium`, `high`, `xhigh`, `max`. Codex: `none`, `low`, `medium`, `high`, `xhigh`.
`--service-tier`	string	no	Codex service-tier override for this and subsequent turns (`standard`, `fast`, `flex`). Sticky, like `--model`: empty leaves the current tier unchanged. Codex agents only.
`--preempt`	bool	no	Interrupt the agent’s in-flight turn and discard pending follow-ups so this one runs next. Mutually exclusive with `--front` and with deferral.
`--front`	bool	no	Deliver this follow-up before everything already queued. Discards nothing and interrupts no turn. Mutually exclusive with `--preempt`. Can be combined with deferral: the placement applies when the message delivers. Agents started on an older version reject it (see Errors).
`--deliver-in`	duration	no	Defer delivery this long from now (e.g. `40m`, `2h`; max 30 days). At most one of `--deliver-in` or `--deliver-at`.
`--deliver-at`	string	no	Defer delivery to this absolute RFC3339 time (max 30 days out). At most one of `--deliver-in` or `--deliver-at`.
`--task`	string	no	A checklist item to include. Repeatable: pass `--task` multiple times to build a checklist.
`--attach`	string	no	Local file to attach privately to the turn. Repeatable. Agents started on an older version reject it (see Errors).
`--json`	bool	no	Output the `QueueAddResponse` (the follow-up ID) as JSON.
`--workspace`	string	no	Workspace name. Overrides the value from `murmur.yaml`.

Examples

Send a follow-up message

murmur queue add fix-auth Now add integration tests for the JWT middleware

Follow-up 4f6c2a1e-8b1d-4c3a-9e2f-7a5b6c8d9e01 sent to fix-auth

The agent receives this message after completing its current task.

Defer a follow-up (“resume me at T”)

murmur queue add --deliver-in 40m fix-auth Deferred: check whether CI finished

Follow-up 4f6c2a1e-8b1d-4c3a-9e2f-7a5b6c8d9e01 deferred to 2026-07-22T18:30:00Z for fix-auth (cancel with 'murmur queue remove fix-auth 4f6c2a1e-8b1d-4c3a-9e2f-7a5b6c8d9e01')

Follow-up with a checklist

murmur queue add fix-auth Harden the auth layer --task "Add expiry validation tests" --task "Add malformed token tests" --task "Update the README"

Follow-up 4f6c2a1e-8b1d-4c3a-9e2f-7a5b6c8d9e01 sent to fix-auth

The agent receives the description along with a structured checklist of tasks.

Override the persona

murmur queue add fix-auth Review the PR for security issues --agent architect

Follow-up 4f6c2a1e-8b1d-4c3a-9e2f-7a5b6c8d9e01 sent to fix-auth

The agent processes the follow-up using the architect persona instead of its default.

Switch the model

murmur queue add fix-auth Take another pass at the flaky test --model claude-opus-4-8

Follow-up 4f6c2a1e-8b1d-4c3a-9e2f-7a5b6c8d9e01 sent to fix-auth

The agent runs this and all subsequent turns on claude-opus-4-8 until the model is changed again.

Errors

Error	Meaning	What to do
`NOT_FOUND`: `<slug> is not running — spawn it first with 'murmur spawn'`	No running agent with that slug exists.	Check the slug. Use `murmur ls` to list running agents.
`INVALID_ARGUMENT`: `deliver_at: ... is not in the future` or `... is more than 720h0m0s out`	The delivery time is in the past or more than 30 days out.	Pick a time within the next 30 days.
`INVALID_ARGUMENT`: `deliver_at and preempt are mutually exclusive`	`--preempt` was combined with `--deliver-in` or `--deliver-at`.	Drop one of them.
`--deliver-in and --deliver-at are mutually exclusive`	Both deferral flags were passed.	Pass only one.
`--front and --preempt are mutually exclusive`	Both placement flags were passed.	Pass only one.
`UNAUTHENTICATED`	Identity token is missing or expired.	Run `murmur login` or check your `murmur.local.yaml` configuration.

Agents: concept overview
Agent personas: persona configuration
murmur queue clear: discard all queued follow-ups
murmur queue strategy: set how follow-ups are drained
murmur queue conflict-resolution: set per-repo conflict handling
murmur notify: send a one-off message without queuing
murmur status: check an agent’s phase and queued follow-ups
murmur watch: stream events for an agent in real time

Getting Started

Core Concepts

Guides

murmur queue add CLI command

Synopsis

Arguments

Examples

Send a follow-up message

Defer a follow-up (“resume me at T”)

Follow-up with a checklist

Override the persona

Switch the model

Errors

​Synopsis

​Arguments

​Examples

​Send a follow-up message

​Defer a follow-up (“resume me at T”)

​Follow-up with a checklist

​Override the persona

​Switch the model

​Errors

​Related

Synopsis

Arguments

Examples

Send a follow-up message

Defer a follow-up (“resume me at T”)

Follow-up with a checklist

Override the persona

Switch the model

Errors

Related