fleet event <list|log> [flags]Inspects and records agent activity events. fleet event list (the default) prints recent events as a JSON array; fleet event log records a custom activity event against an agent and signals the brain daemon.
This is a low-level debugging surface for the activity event stream. Note that it does not publish reactive-chain fabric events — for that, use fleet fabric publish. The list output is always JSON.
| --limit <N> | With list, max entries to return (default 100) |
| --agent <name> | With list, filter to events for a specific agent; with log, the agent the event is recorded against (required) |
| --type <type> | With log, the event type: start, complete, error, restart, blocked, or stale (required) |
| --detail <text> | With log, free-form description attached to the event |
| --project <slug> | With log, scope to a specific project (overrides cwd detection) |
List the 5 most recent events as JSON
fleet event list --limit 5Filter recent events to one agent
fleet event list --agent tech-leadRecord a custom activity event against an agent
fleet event log --agent frontend-dev --type complete --detail "finished checkout PR"No. fleet event records activity events only. To fire a fabric chain event (ticket_ready, pr_approved, etc.), use `fleet fabric publish`.
Always a JSON array, newest first, normalized to `[]` when empty.
One binary. Five minutes. See every agent, coordinate every handoff, and keep a full audit trail of what your fleet did.