Skip to main content

​
Run and control a fleet

​
What this does

These commands show fleet activity and change lifecycle state. Every command uses the active workspace.

​
Before you begin

Install a fleet. Copy its identifier from agentsfleet list.

​
Steps

  1. List fleet identifiers.
  2. View recent activity. <FLEET_ID> comes from the list output.
  3. Send a manual message.
  4. Stop new work while keeping the fleet resumable.
  5. Resume the fleet.

​
Verify it works

​
Common problems

UZ-AGT-009 means the fleet does not exist in the active workspace. Check the workspace and fleet identifier. UZ-AGT-012 means the fleet cannot accept a message in its current state. Resolve the cause or resume a stopped fleet. A lifecycle command sends a write again only when the connection was refused, the name did not resolve, or the server declined it. A reset after sending or a timeout surfaces the error instead, because the server may have processed the write. Check agentsfleet doctor, then run the command again.

​
Remove or undo

Stopping is reversible with resume. Killing is permanent but keeps the fleet records until deletion. Deleting removes all fleet records and cannot be undone. The client has no dry-run option for either command.