CLI reference

fleet doctor

Name: Fleet
Author: Fleet

fleet doctor [--json]

Checks that every prerequisite Fleet depends on is present and functional: tmux, SQLite, the gh CLI, the fabric and brain sockets, the data directory, daemon freshness, configured providers, and reactive-chain wiring. Each check prints OK, INIT, WARN, or FAIL with a short explanation, then a bottom-line verdict.

Run fleet doctor when setting up Fleet on a new machine, after an upgrade, or whenever fleet status shows something unexpected. It only reads state, never modifies anything, and works without a license. Pass --json for structured output.

Flags

--json

Emit the full check list as a JSON array instead of the formatted report

Examples

Run all prerequisite checks

fleet doctor
# Fleet Doctor
# [OK]    tmux                      /opt/homebrew/bin/tmux
# [OK]    sqlite                    ~/.fleet/fleet.db (812 KB)
# [OK]    gh cli                    /opt/homebrew/bin/gh
# [OK]    fabric socket             not running (optional; direct-DB mode)

Emit JSON for a bootstrap script

fleet doctor --json

Frequently asked questions

Does fleet doctor require a license?

No. doctor is read-only and works without a license.

Is a missing fabric.sock a problem?

No. The fabric socket is optional — Fleet falls back to direct SQLite access when it is absent, so doctor reports the missing socket as OK in direct-DB mode.

Related commands

fleet status →fleet init →fleet watcher →

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