Configuration¶
config.toml in the config folder (~/.config/fleet-manager on Linux, %USERPROFILE%\AppData\Roaming\fleet-manager
on Windows; see Where your data lives), read by both the
daemon and the app. The setup wizard writes tasks_root and personas_dir; every key is optional. See
packaging/config.example.toml in the repo. A leading ~ means your home folder on both systems.
| Key | Default | |
|---|---|---|
listen |
127.0.0.1:7878 |
Loopback only |
tasks_root |
~/fleet-tasks |
One folder per task |
state_dir |
the data folder | Database, daemon.log, clones of URL repos, each product's internal/ notes repo |
branch_prefix |
fleet |
Agent branches are <prefix>/<task> |
claude_command |
["claude"] |
How agents are started |
personas_dir |
personas in the data folder |
One folder per persona: its claude and gh logins (mode 700 on Linux) |
gh_command |
gh |
The GitHub CLI |
test_timeout_secs |
1800 |
How long the checks open_pr runs may take, all steps together |
max_breakdown_versions |
8 |
Most breakdown versions one task may accumulate. Applies after the daemon restarts |
max_steps |
20 |
Most steps one breakdown may declare. Applies after the daemon restarts |
max_parallel_specialists |
3 |
Most specialists one orchestrator may run at once. Applies after the daemon restarts |
The data folder is ~/.local/share/fleet-manager on Linux and %USERPROFILE%\AppData\Local\fleet-manager on
Windows. Changes to the file apply when the daemon restarts; folders changed in the setup wizard offer
Restart now.
claude, gh and git are looked up on the PATH the daemon builds when it checks your tools: its own, plus the
system PATH (the registry on Windows, a login shell on Linux), so a tool installed after the app started is found
by Check again without a restart.
Next to config.toml in the config folder: gui.toml (the app's own settings, such as the active product and the
close choice), agent/ (instructions.md, settings.json, edited in Management) and fleet/ (orchestrator,
specialist and skill definitions).