Hull Fleet
Run a team of coordinated agents that plan, build, review and land work in your repositories
Hull Fleet runs a team of agents on your repositories. You describe the work. Coding agents write it in parallel, a review agent checks it, and a coordinator keeps everything moving, while you decide what ships.
Open Hull Fleet from app.withhull.com. You can run it on your personal account or inside an organization.
Three kinds of agent
| Agent | Role | What it does |
|---|---|---|
| Polecats | Coding | Write code, run commands and tests, push branches. Several can work at once on different tasks. |
| Refinery | Review | Reviews polecat work, runs your quality gates, and merges or opens a pull request. |
| Mayor | Coordination | Your conversational interface. Plans work, reports status and investigates problems. |
These agents work inside a town: a persistent workspace connected to one or more repositories. The town keeps configuration, work history and agent state between sessions.
How it works
1. Create a town
Name the town, connect a GitHub or GitLab repository, and pick models. Hull Fleet provisions a container for the town's agents.
2. Sling work
Describe what needs doing: a bug, a feature, a refactor. Sling a single task, or a convoy: a set of tasks where some depend on others.
3. Agents pick it up
Hull Fleet assigns open work to available polecats. Each polecat works in its own Git worktree, makes changes, runs commands and pushes a branch.
4. Work gets reviewed
Finished work goes to the refinery. Depending on your merge strategy, it pushes directly to your default branch or opens a pull request for human review.
5. You stay in control
Watch progress on the town dashboard, chat with the Mayor, review pull requests and step in when agents need guidance. Branches, commits, review feedback and events are all visible.
Core concepts
| Concept | What it is |
|---|---|
| Town | A persistent workspace connecting repositories to a team of agents. |
| Rig | A repository connected to a town. A town can have several rigs. |
| Bead | A unit of work. Beads move through open, in progress, in review and closed (or failed). |
| Convoy | A group of related beads, with dependencies, that agents work through in order. |
| Mayor | The coordination agent you talk to. |
| Polecat | A coding agent. |
| Refinery | The review agent. |
For the details, see Concepts.
What you can use it for
- Features: describe a feature and get back a reviewed pull request
- Bug fixes: point agents at an issue to investigate and fix
- Refactors: break large changes into convoys that land step by step
- Maintenance: dependency updates, lint fixes, documentation
Get started
- Quick start: create your first town
- Concepts: towns, rigs, beads, convoys and agents
- The Mayor: working with the coordinator
- Sling work: tasks, convoys and staged plans
- Review and merge: how the refinery reviews and lands work
- Settings: models, Git authentication, merge strategy and more
- Troubleshooting: common problems and fixes
- Hull Commons: pick up shared tasks from a Hull Commons workspace