CLI reference

fleet init

Name: Fleet
Author: Fleet

fleet init [--template <name>] [--list-templates] [--force] [--no-backup]
       fleet init --org <name> [--force]

Scaffolds a Fleet project in the current directory: creates .fleet/config.yaml and .fleet/prompts/ with a starter agent set, picked either from repo signals (interactively or auto in non-TTY shells) or from a named template. With --org <name> it scaffolds ~/.fleet/orgs//org.yaml instead, pre-wired with a label_watches block.

If a config already exists, init refuses unless you pass --force (which snapshots the old config to .fleet/.backup/ first, unless --no-backup). It does not write .mcp.json and does not run skills install.

Flags

--template <name>	Scaffold from a named project template (see --list-templates)
--list-templates	Print every available template and exit
--org <name>	Scaffold ~/.fleet/orgs/<name>/org.yaml instead of a repo config (name value required)
--force	Overwrite an existing .fleet/config.yaml or org.yaml
--no-backup	Skip the .fleet/.backup/ snapshot that --force otherwise creates

Examples

Initialize Fleet in the current repo

fleet init

Scaffold from a named template

fleet init --template go-service

Scaffold an org config

fleet init --org feral-intelligence

Frequently asked questions

What happens if .fleet/config.yaml already exists?

init refuses and tells you to pass --force. There is no partial-merge — --force overwrites the config (after a .fleet/.backup/ snapshot unless --no-backup is set).

Does fleet init set up .mcp.json or install skills?

No. init only scaffolds .fleet/config.yaml and .fleet/prompts/ (or the org.yaml). Run `fleet skills install` separately, and wire .mcp.json yourself.

Related commands

fleet config →fleet skills →fleet mcp →

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