CLI reference

fleet watcher

Name: Fleet
Author: Fleet

fleet watcher <start|stop|status> [--org [name]] [--supervised] [--no-brain] [--json]

Controls the watcher daemon, Fleet's autonomous engine. It runs three loops: a label watcher that polls GitHub for label changes (about every two minutes) and publishes fabric events, a subscription processor that matches new events to agent subscriptions (about every ten seconds) and starts agents, and an agent scheduler that fires cron-scheduled agents.

fleet watcher start launches the daemon for the current repo (license-gated). Pass --org <name> for an org-level watcher across all repos in that org. The watcher does not respawn crashed agents; work is re-dispatched via the reactive chain.

Flags

--org [name]	Operate on the managed org watcher (~/.fleet/orgs/<name>/org.yaml) instead of the repo watcher
--supervised	With start, run under a process supervisor without daemonizing
--foreground	With start, run in the foreground (used internally by the supervised/daemon fork)
--no-brain	With start, skip auto-starting the brain daemon and brain-monitor loop
--json	With status, emit watcher status as JSON

Examples

Start the repo-level watcher daemon

fleet watcher start

Start an org-level watcher

fleet watcher start --org feral-intelligence

Check watcher status as JSON

fleet watcher status --json

Frequently asked questions

Does fleet watcher require a license?

Yes. `fleet watcher start` is license-gated.

Does --supervised restart crashed agents?

No. --supervised keeps the watcher daemon itself running under a supervisor. The watcher does not monitor or respawn crashed agent sessions; work is re-dispatched through the reactive chain.

Related commands

fleet status →fleet fabric →fleet agent →

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.

See how it works Install Fleet