- the agent enters the
--phasetarget (if one was given), - the agent enters a terminal phase (
PHASE_COMPLETED,PHASE_FAILED,PHASE_CANCELED), - the agent comes to rest in
PHASE_TASK_COMPLETE,PHASE_IDLE, orPHASE_SLEEPINGwith no queued follow-ups. A resting agent cannot move again without input. A sleeping agent never completes on its own, so waiting longer cannot satisfy the request. Check the printed phase: “at rest” means the agent is awaiting follow-ups, not finished.
Synopsis
Arguments
Valid phases
If the agent reaches a terminal phase, or comes to rest, before the target phase, the command returns immediately with the current status. A target-phase wait never blocks on an agent that cannot reach the target on its own.
Output
The command prints a one-line outcome (wait ended: …) followed by the same status output as murmur status: workflow ID, phase, VM assignment, progress, output, and cost. On timeout, it prints only the status, without the outcome line. With --json, it prints only the AgentStatus as JSON.
Examples
Wait for an agent to finish its work
Wait for an agent to start running
Wait in a script
Waiting on an agent that went to sleep
on_idle: sleep policy an agent parks its VM after the idle timeout and never reaches PHASE_COMPLETED by itself. The command returns the resting status instead of blocking forever, and exits non-zero because the target phase was not reached: send a follow-up with murmur queue add or kill the agent to drive it terminal.
Agent fails before reaching target phase
PHASE_FAILED is terminal. It does not block forever waiting for PHASE_IDLE.
Errors
Related
- Agents: concept overview
murmur status: check an agent’s current statusmurmur sleep: stop an agent’s VMmurmur wake: restart a sleeping agent’s VMmurmur spawn: start an agentmurmur ls: list running agents