Management¶
Management is where the fleet is configured, one tab per area:
- Overview: every product at a glance, and where you pick the active product. See Overview.
- Products: name, repos, each repo's specialist roster, and the product's overrides. See Products and releases and Overrides.
- Personas: create, re-login, rename, delete. See Personas.
- Instructions: one Markdown file given to every agent as its
CLAUDE.md, the replacement for a global one. - Agent settings: permission allow/deny rules and env merged into every agent's Claude settings.
- Orchestrators, Specialists and Skills: built-in and user definitions, edited as Markdown. See Orchestrated tasks.
- Workflow: what a repo's
.fleet/workflow.ymlis. See Workflow.
The app keeps the last tab you opened while it runs.
Overview¶
Overview is read-only: it shows each product as one row, so you can see the whole fleet without switching the active product.
Each row has:
- The product's name. Click it to make that product the active product, the same as picking it in the drawer's product switcher. The active product's row says active.
- Its tasks counted by where they stand: Working, Needs you and Review count tasks whose agent is in that board column; Merged counts tasks that are merged or marked done by hand. A task whose agent is in none of those columns, such as a stopped one that was never merged, is not counted.
- Each release not yet released, with its version and the same two bars as the Releases view: tasks merged, and days used or overdue. See Releases.
The Product filter above the rows shows one product or All products (the default).
Overrides¶
A product can set a few settings for itself. Everything it does not set follows the global value. The Overrides section on the Products tab lists the product's overrides, one row each: section, key, value.
| Section | Key | Value |
|---|---|---|
models |
An orchestrator or specialist name | A model: a name such as sonnet or opus, or a full model ID such as claude-sonnet-5-5 |
limits |
max_breakdown_versions, max_steps or max_parallel_specialists |
A whole number above zero |
Pick the section and the key from the dropdowns and type the value. The key list for models is the orchestrators
and specialists that load. Beside each row the app shows the value the override replaces and where that value comes
from: product, global, definition or default.
Save overrides sends the whole list and the daemon replaces what it stores. The daemon checks every row. If it refuses one, the app shows its message and keeps your rows, so you can fix them and save again. A stored row that no longer applies, because its definition was deleted, is shown with the reason. Remove it and save.
New agents use a changed override. Agents already running keep the model they started with.
Internal resources¶
A product's detail page in Products has a read-only Internal resources section: the product's private notes
repo, where orchestrated tasks keep their designs and plans. Pick a branch (main holds what past pull requests
merged; each task has a task/<task-name> branch), then a file to see its text and its last commit. Refresh,
or closing and reopening the section, fetches it again and keeps the branch and file you had if they still exist.
See Internal resources.
Models¶
An orchestrator or specialist definition can name a model in its front matter:
model: sonnet
An agent runs on the first of these that is set:
- The product's
modelsoverride for its definition. - The definition's own
model:. - The persona's default, which is Claude's own choice.
The side panel of a fleet agent shows the result as Model: sonnet, or Model: persona default when nothing sets one. A solo agent has no model line.
The built-in definitions carry a model:. A user file with a built-in's name replaces the built-in as a whole, so a
copy you made earlier does not get a model: the built-in has since gained. Add the line to your copy, or use
Reset to built-in to drop it. See Orchestrated tasks.
Workflow¶
Workflow explains the .fleet/workflow.yml file each repo keeps on its base branch, with a two-step example. The
tab does not edit the file: add it to the repo and push it. What the file holds and when it is read is in
The workflow file.
Where it is stored¶
The agent instructions and settings edited in Management live in the config folder
(~/.config/fleet-manager on Linux, %USERPROFILE%\AppData\Roaming\fleet-manager on Windows; see
Where your data lives): agent/ holds instructions.md
and settings.json, and fleet/ the orchestrator, specialist and skill definitions. The active product picked on
Overview is saved as active_product in gui.toml, in the same folder.