CLI reference

fleet corpus

Name: Fleet
Author: Fleet

fleet corpus resolve [--dir <path>] [--json]

Resolves the context corpus declared in your .fleet/config.yaml — a set of glob patterns over the markdown and context files in your repo that general-purpose agents read as input. fleet corpus resolve walks the project with git, matches every corpus pattern, and prints the exact file set an agent run would see, so you can confirm a corpus before pointing agents at it.

The corpus IS your git repo: resolution runs git ls-files, so it honors .gitignore automatically and includes both tracked and new-but-not-ignored files. Patterns are slash-separated globs relative to the repo root; ** matches across directory boundaries (for example, docs/**/*.md). Results are sorted and deduplicated. corpus is read-only and never modifies your files.

Flags

resolve	Resolve and list the corpus files for the project config in the current (or --dir) directory
--dir <path>	Project root to search from (defaults to the current working directory)
--json	Emit the resolved file set as a JSON array of repo-relative paths instead of one path per line

Examples

Declare a corpus in .fleet/config.yaml

corpus:
  - path: docs/**/*.md
  - path: "*.md"

List the resolved corpus file set (one path per line)

fleet corpus resolve
# README.md
# docs/guides/quickstart.md
# docs/intro.md

Emit the file set as JSON for a script or another tool

fleet corpus resolve --json
# ["README.md","docs/guides/quickstart.md","docs/intro.md"]

Resolve a corpus in another checkout

fleet corpus resolve --dir ~/code/handbook

Frequently asked questions

Where does fleet corpus read its patterns from?

From the corpus: list in the .fleet/config.yaml discovered at or above the current directory (or the path given with --dir). Each entry is a path: glob relative to the repo root. If no .fleet/config.yaml is found, the command exits with a clear error.

Does the corpus respect .gitignore?

Yes. Resolution runs `git ls-files --cached --others --exclude-standard`, so anything ignored by .gitignore is excluded automatically, and both tracked and untracked-but-not-ignored files are included. The project root must be a git repository.

What does ** match in a corpus pattern?

** matches any number of path segments, including zero — so docs/**/*.md matches docs/intro.md as well as docs/api/ref/endpoints.md. A single * matches within one path segment only. Matching is done on slash-separated, repo-relative paths.

Does fleet corpus change any files?

No. corpus resolve is read-only: it lists the files that match your corpus patterns and never reads, writes, or moves their contents.

Related commands

fleet config →fleet init →fleet agent →

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