fleet config <get|set|list|validate|export|import|snapshot|snapshots|rollback|diff> [args]Reads and writes Fleet's runtime settings, stored in the SQLite settings table — not in .fleet/config.yaml. Use get/set/list for individual settings, validate to check a repo's .fleet/config.yaml, and export/import/snapshot/rollback/diff to manage config snapshots.
Unknown setting keys are rejected up front so a typo can't silently persist a dead row. All config output is JSON; there is no --json flag and no --org flag.
| get <key> | Look up a single setting by key (emitted as JSON; exits non-zero if absent or unknown) |
| set <key> <value> | Create or update a setting (validates the key first, emits the new pair as JSON) |
| validate | Validate the .fleet/config.yaml discovered from the current directory |
| import <file> | Import settings from a file (--strategy skip|overwrite) |
| rollback [--rev N] | Restore a previous config snapshot (defaults to the most recent) |
List all settings (JSON)
fleet config list
# [{"key":"brain.approval_required","value":"true"}, ...]Read a single setting
fleet config get brain.approval_required
# {"key":"brain.approval_required","value":"true"}Validate the repo's config file
fleet config validate
# config valid: /path/to/repo/.fleet/config.yamlNo. get and set operate on the SQLite settings table. Use `fleet config validate` to check your .fleet/config.yaml, and edit that file by hand to change agent definitions.
No. config output is always JSON, and there is no --org flag. Use export/import/snapshot to move config between machines.
One binary. Five minutes. See every agent, coordinate every handoff, and keep a full audit trail of what your fleet did.