---
title: "The fleet board · intentic"
description: "Run ten coding agents at once and see which needs you: attention lanes, per-agent cost and diffs, one git worktree each, woken by schedule or event."
url: "https://intentic.dev/product/fleet/"
---

Fleet board

# A board for the whole fleet, sorted by what needs you.

One agent is a chat window. Ten need a control surface: who is running, who is blocked, what each has changed and spent.

[Get started free](https://app.intentic.dev) [Open the live workspace](https://intentic.dev/demo/)

acme-shop · /agents

![The intentic fleet board: an Attention lane with an agent asking a question and one blocked on a land conflict, an Active lane with three agents running, and a Finished lane where a completed agent offers Land now. Every card shows model, branch, tokens, cost and diff stats.](https://intentic.dev/_astro/fleet-board.CUFvo7ci_Z17wPTK.webp)

- 3 lanes

 Attention, Active, Finished. The board sorts itself
- 1 branch each

 every agent works on its own git worktree
- 5 harnesses

 Claude Code, Codex, Grok, Kimi, Gemini

## Attention is a lane, not a notification

An agent that needs a decision stops and says so, with the reason on its card. A fleet of ten reads as a short list of things only you can do.

- Question for you · Approval needed · Land conflict, each with the one action that clears it
- Everything else keeps running while you answer

## Every card carries the receipts

Model, branch, turns, tokens in and out, dollars spent, and the diff so far. No opening a transcript to find out where your money went.

![The same fleet board on a phone: agent cards stacked in one column with model, branch, cost and diff stats.](https://intentic.dev/_astro/mobile-fleet.Bzad5Wk6_Z11h8Ov.webp)

## Isolated by construction

Each agent gets its own git worktree off your base commit. They never write over each other, and nothing reaches your tree until you land it.

One base commit, one branch each

agent/checkout-stripe

its own worktree, its own checkout

agent/soft-deletes

its own worktree, its own checkout

agent/latency-p99

its own worktree, its own checkout

land, one at a time, after you have read the diff

Your working tree

untouched until you land, and still yours to amend or revert afterwards

## Woken by events, not only by you

An automation starts an agent on a schedule or an event, as a fresh session with its own transcript. The nightly dependency audit arrived that way.

Push

GitHub · GitLab

Alert

Sentry

Payment

Stripe

Email

IMAP

Message

Discord

Schedule

cron

guard, then run

A fresh agent session

Its own transcript, its own worktree, the same review before anything lands.

[Next Chat & plan mode → It proposes, you approve, then it works](https://intentic.dev/product/chat/)

[Get started free](https://app.intentic.dev) [Read the quickstart](https://intentic.dev/docs/quickstart/)