flt CLI reference

Build and distribute immutable Fleet content, manage client contexts, and call supported Registry workflows.

On this page

All command families

Command	Purpose
`flt version`	Show the client version and protocol compatibility.
`flt compile`	Compile authoring YAML into a self-contained OCI layout.
`flt compile-verifier`	Compile one authoring Verifier YAML document into canonical JSON and blobs.
`flt lock`	Resolve authoring image references into a deterministic fleet.lock.
`flt auth`	Log in to, inspect, and remove Registry credentials.
`flt context`	Manage isolated Store, settings, credential, and state contexts.
`flt config`	Read or change non-secret client settings.
`flt system`	Maintain the local Fleet Store, including safe pruning.
`flt status`	Show the effective context, Store, selected Registry, and its authentication state.
`flt env`	Pull and push standalone Environment roots.
`flt artifact`	Pull and push existing canonical Artifact roots.
`flt pull`	Import supported sources or pull TaskSet, Environment, and Artifact roots into the local Store.
`flt push`	Publish a complete local TaskSet closure to a Registry.
`flt tag`	Create or move a local Tag.
`flt label`	Manage Registry discovery labels on repositories, resource versions, and immutable subjects.
`flt credentials`	Manage credentials stored in a Registry project.
`flt experiments`	Submit and inspect hosted Experiments through the Registry API.
`flt rm`	Remove local Tags without deleting immutable content.
`flt cp`	Copy one Task into a new immutable TaskSet.
`flt merge`	Merge complete local Tasksets into one immutable TaskSet.
`flt export`	Write editable authoring material from a supported Fleet source.
`flt list`	List local roots or Tasks in one local TaskSet.
`flt inspect`	Inspect one local Fleet object or Task.

Authoring and compilation

Terminal

flt lock --input taskset.yaml --output fleet.lock --format json
flt compile --input taskset.yaml --source-root . --output ./layout --format json
flt compile-verifier --input verifier.yaml --source-root . --output ./verifier-layout --format json
flt export SOURCE DIR

The compiler commands require explicit JSON output because they are integration surfaces. export writes supported editable authoring material; it does not reconstruct arbitrary canonical content.

Distribution and local content

Terminal

flt pull SOURCE [ALIAS] [--eager]
flt push LOCAL DESTINATION [--dry-run] [--no-latest-retag]
flt env pull SOURCE [ALIAS] [--eager]
flt env push LOCAL DESTINATION [--dry-run] [--no-latest-retag]
flt artifact pull SOURCE [ALIAS] [--eager]
flt artifact push LOCAL DESTINATION [--dry-run] [--no-latest-retag]
flt inspect LOCAL[/TASK] [--format text|json|digest]
flt system prune [--confirm-rootless-user-store]

Registry workflows still owned by flt

flt label, flt credentials, and flt experiments remain supported Registry workflows. Access grants are the separate fleet access surface, and execution remains fleet-runtime.

Contexts, precedence, and global options

Configuration resolves from command flags, environment variables, the selected context, then built-in defaults. A named context switches Store, settings, credentials, and state together.

Terminal

flt context list|show|current|create|use|remove
flt config list|get|set|unset
flt [--context NAME] [--registry HOST] [--store PATH]
flt [--credentials PATH] [--settings PATH] [--state PATH]
flt [--timeout DURATION] [--max-import-bytes N] [--max-tasks N]
flt [--json | --quiet] [--no-input]

Shell completion is available through flt completion SHELL.