CLI reference

fleet template

Name: Fleet
Author: Fleet

fleet template <list|create|delete|spawn> [flags]

Browses Fleet's built-in agent catalog (over 120 role-specific prompt templates compiled into the binary) and manages user-authored custom templates stored in the control plane. You can list templates, create or delete custom ones, and spawn a new agent from a custom template.

By default list shows the embedded catalog. To seed an agent's prompt from the catalog, use fleet agent create --name <n> --vendor claude-code --template <catalog-name> rather than the template command.

Flags

--custom	With list, show control-plane custom templates instead of the embedded catalog
--search <q>	With list, filter catalog rows whose name or description matches the query
--json	With list, emit the templates as JSON
--name <n>	Name for create or spawn (required)
--vendor <v>	Vendor for spawn (required, e.g. claude-code)

Examples

List the embedded catalog

fleet template list
# Fleet agent catalog (121 templates)
#   frontend-developer       Frontend Developer
#   tech-lead                Tech Lead
#   release-manager          Release Manager

Search the catalog and emit JSON

fleet template list --search backend --json

Spawn an agent from a custom template

fleet template spawn 4 --name my-dev --vendor claude-code

Frequently asked questions

Where do the catalog templates come from?

They are compiled into the Fleet binary from internal/catalog/agents/ via go:embed. They are not fetched from the network.

Why does template list show the catalog but spawn needs a custom template?

`spawn` creates an agent from a user-authored custom template (control plane). To start from the embedded catalog instead, use `fleet agent create --template <catalog-name>`.

Related commands

fleet agent →fleet init →fleet config →

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