Skip to main content
Sends a follow-up message to a running agent. The message is queued and delivered when the agent is ready to process it. 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 strategy — all (drain everything), one (one per turn), or five (up to five per turn).

​
Parameters

NameTypeRequiredDescription
slugstringyesAgent task slug. Use an absolute path like /w/workspace/u/account/slug to target an agent outside your own path.
descriptionstringyesFollow-up message to send to the running agent.
tasksstring[]noChecklist items to add to the agent’s task list.
agentstringnoAgent persona override (e.g. programmer, architect).
workspacestringnoWorkspace name. Overrides the session default.

​
Response

Returns a confirmation string: follow-up sent to <slug>.

​
Examples

​
Send a follow-up message

{
  "slug": "fix-auth",
  "description": "Also fix the session expiry logic while you're in that file."
}
Response: 
follow-up sent to fix-auth

​
Send a follow-up with new tasks

{
  "slug": "fix-auth",
  "description": "Here are additional items to handle.",
  "tasks": ["Add rate limiting to the login endpoint", "Update the API docs"]
}

​
Interrupt then redirect

Use interrupt to stop the current turn, then send new instructions: 
{
  "slug": "fix-auth",
  "description": "Stop what you're doing. Focus on the login handler instead."
}

​
Errors

CodeMeaningWhat to do
NOT_FOUNDNo agent with that slug exists.Check the slug. Use ls to see running agents.
FAILED_PRECONDITIONAgent is not running.Use spawn with resurrect: true to resume a dead agent.
UNAUTHENTICATEDIdentity token is missing or expired.Check credentials.