Fleet Manager¶
Your agents, on a board, not behind a wall of text.
A desktop command room for a fleet of coding agents.
- Fly by hand. Answer, pause and review each agent from its card, with its live terminal and diff one click away.
- Autopilot. An orchestrator agrees the goal with you, breaks it down and runs specialists under a policy you set.
- Specialists. Narrow agents with one job each, whose limits Fleet Manager enforces, not only their prompt.
Today you fly by hand, and orchestrated tasks run with you approving each step. Autopilot and enforced limits are
next: see ROADMAP.md in the repository.
Getting started¶
- Install: download, run, update; where your data lives. Windows and Linux.
- First run: the setup wizard and tool check, your first product and your first task.
Guide¶
- The board: columns, why a card needs you, and what you can do from it.
- Products and releases: group tasks by product and track a release.
- Tasks and repos: worktrees, branches and merging.
- Orchestrated tasks: an orchestrator, its specialists and one pull request.
- Stop now, archive later: end an agent, clean up its disk later.
- Personas: one set of Claude and GitHub accounts per task.
- Management: products, personas, instructions, agent settings and definitions.
Reference¶
- Configuration: every key of
config.toml. - Architecture: the daemon, the app, the agents and the crates.
Contributing¶
- Development: setup, builds, tests, design notes and commits.
- UI internals: how the web UI and the desktop app are put together.
- Demo media: how the board image and animation are recorded.
- Release checklist: what to check on each system before tagging a release.
Background¶
- What fleet management means here: the v1 framing of the problem.