All pages
Lesson 3.5 · Organize your work · 14 min
Fleet
Let agents work the board on their own, within limits you set.
After this lesson you know what a fleet does, how to prepare a board for one, and how to run a small, safe first run that ends in pull requests you review.
Time: 14 minutes · Works on: macOS app.
What a fleet is
A fleet is a pool of agents that work a project's Tasks board on their own. You file the cards, choose how many workers run and how much they may spend, and press Start. Each worker:
- Claims a card that is ready to start.
- Works it in its own git worktree, on its own branch.
- Optionally has its branch checked by a reviewer agent.
- Lands the work under the policy you chose. By default that means opening a pull request for you to merge.
The board is the queue. There is no separate list of jobs. Anything that can write to the board can feed the fleet, including Claude Code over MCP. The work survives closing the window or relaunching the app.
Fleet is experimental. It runs several agents at once that approve their own edits, and it spends money for as long as it runs. Start with one worker, a small budget and the default Open a PR policy, and watch your first run.
Before this lesson, work through The Kanban board and Worktrees. The project must be a git repository.
Make cards ready
A worker only takes a card that is ready: not finished, not claimed by anyone, and with every card it depends on already done.
- Open the Tasks tab from More ▾.
- Add two small, well-described cards. Write each one so an agent with no other
context could do it. For example: "Add a
--versionflag to the CLI that prints the version from package.json." - If one card must wait for another, open it and add the other card under Blocked By. TRMNLY refuses a dependency loop and names the cards in it.
- Click the bolt button in the filter bar. The board now shows only cards that are ready to start. This is the same rule the fleet uses, so what you see is what a worker will take.
A card whose branch already has an open pull request is held back. It isn't offered again, and it doesn't unblock the cards that depend on it until the PR is merged.
Set up the run
The Fleet strip sits under the Tasks header. Click it to expand it.
Set the number of workers with the stepper. Use 1 for your first run. The most is 8, and each worker gets its own worktree.
Pick where the tokens come from:
- CLI harness (subscription) runs workers on an installed Claude Code, Codex or Gemini CLI, so a long run bills against your subscription. This is the default. Approvals, the audit log and the agent lock still apply.
- Project default uses the project's model and API key.
If no CLI harness is installed, workers fall back to the project's model.
Enter a Budget in US dollars. When the run reaches it, workers stop taking cards and the ones in progress finish.
Leave When done on Open a PR (default).
Turn on Review first to have a reviewer agent check each branch before it lands.
When done: the land policy
| Policy | When a card is finished |
|---|---|
| Open a PR (default) | The branch is pushed and a PR opened. The card waits. You merge. |
| Merge when green | The branch merges once its checks pass. |
| Merge immediately | The branch merges at once. Breakage becomes a repair card. |
The last two let an agent change your base branch with nobody in the loop. They are off unless you choose them, per project, in this strip. The agent can't change this setting over MCP.
What the reviewer does
The reviewer reads the branch's diff against its base and can read surrounding files. It can't edit anything. It fails closed: if its output can't be read, has no verdict or gives no reason, the branch is rejected. A rejected card goes back on the board with the findings added, so the next attempt starts from them.
Run it
- Click Start. The board the Tasks tab is showing is the one the run works. Switching boards later doesn't move a running fleet.
- Watch the strip. It shows how many workers are busy, how many cards are done and what the run has spent.
- Watch the board. The claimed card shows which worker holds it.
- When the worker finishes, find the pull request it opened. Read it the way you'd read anyone's.
- Click Stop at any time. Stopping hands every unfinished card back and cancels any review or merge in progress. Nothing merges after you stop.
A card that fails three times in one run is left alone for the rest of the run, with a note on the card saying so.
If a worker crashes or TRMNLY quits, the claim's lease runs out and the card returns to the board by itself.
Repair cards
While a fleet runs, a build or test failure it detects becomes an urgent card with no dependencies, so the next free worker takes it. Repair is on by default. Attempts are limited. After the limit, the fleet files one card for you and stops retrying that failure.
Standing rules for every agent
When several agents work one project, they need rules that don't live in any one
conversation. Put them in your repository, in docs/doctrine/*.md. TRMNLY adds
those files to the context of every agent working the project. Create the folder
yourself; TRMNLY won't write into your repository unasked. Write each rule as a
decision with its reason, and keep the file short.
Check yourself
- The bolt filter shows exactly the cards you expect to be ready.
- A one-worker run with a small budget claimed a card and opened a pull request.
- Stop returned an in-progress card to the board.
- You can say which land policy is on for this project and why.
Go further
- Fleet — races, wishes, repair limits and the
fleet_*tools - Kanban — claims and dependencies in detail
- Agent lock — what still guards your Mac while workers run