You write the ticket.
Your agents ship it.
Fleet is a single Go binary that executes the saved workflows you design — so a code step opens a PR, a review step checks it, and a governed merge step ships it without hidden handoffs.
Configure the worker locally, build the workflow visually
YAML declares repositories, agents, and types. The dashboard declares steps, dependencies, retries, and approval gates.
# .fleet/config.yaml
types:
- name: developer
model: claude-sonnet
- name: reviewer
model: claude-opus # judgment-heavy → stronger model
- name: release-manager
model: claude-sonnet
agents:
- name: backend-dev
role: developer
- name: code-reviewer
role: reviewer
- name: release-manager
role: release-managerUse efficient models for routine types and a stronger model where judgment matters. Then bind those types to steps in a saved workflow. See the full walkthrough in the step-by-step guide.
What you'd build by hand vs. what Fleet handles
You can wire this together yourself with tmux and worktrees. Here's what you'd be signing up to maintain.
The DIY approach
- Open a terminal per agent and a worktree per branch
- Notice when one agent finishes and manually tell the next to start
- Relay context between agents by reading output and re-prompting
- Cap how long each agent runs by babysitting sessions yourself
- Hope nobody's agent deletes tests to make them pass
- Reconstruct what happened from git history when something breaks
With Fleet
- Each agent gets its own tmux session and worktree automatically
- A code step opens a PR; the next review step receives the real diff
- Context moves across explicit dependency edges and persisted run state
- Per-agent run-time budgets with hard ceilings
- A separate risk model auto-quarantines a drifting agent before it ships
- Every decision written to an audit trail you can query with fleet log
Dig deeper
Guides, comparisons, and reference for running an agent fleet.
Guides →
Step-by-step: parallel agents, PR review, cost control.
Comparisons →
Fleet vs. Devin, OpenHands, Cursor, Claude Squad, and more.
Glossary →
Plain-language definitions for the AI agent fleet era.
Agent templates →
Role-tuned starting points for every agent in your fleet.
Integrations →
Claude Code, GitHub, MCP, tmux, and the rest of your stack.
Docs →
Install, configure, and run Fleet end to end.
Need to convince your lead?
The business case — cost, governance, and audit trails — laid out for engineering leaders.
The case for FleetA note on access
The binary is free to install and inspect; starting agents requires a license. Sign up free and you'll get a registration code for your dashboard.
Start free