fleet task <assign|list|get|update> [<agent> <task>] [flags]Dispatches work to agents and manages fabric tasks. fleet task assign <agent> <task> injects the task as FLEET_TASK_TITLE and starts the agent in tmux. Batch forms (--team, --department, --all) assign the same task to many agents. The list/get/update subcommands inspect and edit fabric tasks.
Assigning to a running agent stops and restarts it with the new task. Assignment starts an agent session, so it is license-gated. Agent names support fuzzy matching.
| --title <task> | Task text (alternative to the second positional; required for batch modes) |
| --project <repo> | Override the target repo for the assignment |
| --dry-run | Preview the assignment without launching the agent |
| --output <path|dir> | With --dry-run, write the preview to a file (solo) or directory (batch) |
| --team <name> / --department <name> / --all | Batch modes: assign the same task to all matching agents |
Assign a task to a specific agent
fleet task assign frontend-dev "Refactor the payment form to use the new design tokens"Dry-run a task assignment without launching
fleet task assign qa-lead --title "Run regression on checkout" --dry-runAssign a task to an entire team
fleet task assign --team dev-team --title "Update dependency pins"`fleet task assign` stops the existing session and restarts the agent with the new task. It does not refuse.
Yes. It starts an agent session, which is a license-gated operation. The list/get/update subcommands are not.
One binary. Five minutes. See every agent, coordinate every handoff, and keep a full audit trail of what your fleet did.