Skip to main content
Sends a follow-up message to a running agent (empty slug = yourself). The message is queued and delivered when the agent is ready to process it — or, with delay_seconds/deliver_at, deferred: it parks in the agent’s durable workflow (surviving VM sleep, unlike an in-session timer) and delivers as a normal follow-up at the deadline, waking a sleeping VM. This is the reliable “resume me at T” primitive for autonomous agents; cancel an undelivered message with clear_queue using the returned follow-up ID. Returns an error if the agent is not running. Equivalent to murmur queue add in the CLI. Follow-ups are delivered according to the agent’s dequeue strategyall (drain everything), one (one per turn), or five (up to five per turn).

Parameters

Response

Returns a confirmation string carrying the message’s effective follow-up ID (client-supplied or server-minted): follow-up <id> sent to <slug>, or for a deferral follow-up <id> deferred to <time> for <slug> (cancel with clear_queue + this ID).

Examples

Schedule your own resumption (from an agent VM)

The message parks in your workflow — your VM can sleep in the meantime — and delivers as a normal follow-up in 40 minutes, waking the VM. A pending deferred message also holds a terminate-on-idle service agent alive until it delivers.

Send a follow-up message

Response:

Send a follow-up with new tasks

Interrupt then redirect

Use interrupt to stop the current turn, then send new instructions:

Errors

  • murmur queue add — equivalent CLI command
  • interrupt — stop the current turn before sending a follow-up
  • clear_queue — discard queued and deferred follow-ups (all, or one by follow-up ID)
  • status — check agent state
  • spawn — create an agent