Fleet 1.13:Teams are now shipping 5x more PRs with autonomous pipelines.See what's new →
FleetFleet
CLI reference

fleet log

fleet log [--agent <name>] [--type <type>] [--ticket owner/repo#N] [--since <dur>] [--limit N] [--project <slug>] [--all-projects] [--follow] [--json]

Shows the unified decision and conversation history: a chronological timeline merging fabric events with agent activity entries. Use it to audit what agents did and in what order across the reactive chain. By default it spans all projects over the last 24 hours.

Filter by agent, type, ticket, or time window; stream live with --follow (aliases --tail, -f); or emit JSON. log is read-only and works without a license.

Flags

--agent <name>Filter to events from a specific agent
--type <type>Filter by event type (e.g. start, decision, handoff); typos are rejected loud
--ticket owner/repo#NPer-ticket timeline, payload and trace_id threaded
--since <duration>Lookback window: 1h, 24h, 7d (default 24h)
--follow, --tail, -fStream new events as they land (not compatible with --json)

Examples

Show the last hour of fleet activity

fleet log --since 1h

Filter to one agent over the last day

fleet log --agent tech-lead --since 24h

Stream a ticket's chain live

fleet log --ticket Feral-Intelligence/forge#42 --follow

Frequently asked questions

Does fleet log require a license?

No. log is read-only and works without an active license.

What is the difference between fleet log and fleet event list?

fleet log is a unified view merging fabric events with agent activity records. fleet event list shows only raw activity events.

Run your first agent fleet

One binary. Five minutes. See every agent, coordinate every handoff, and keep a full audit trail of what your fleet did.