For projects built with AI coding agents

Keep your AI-built project from turning into a mess.

Every agent change gets its own card and a review from a different model before it reaches you. Small changes instead of one giant prompt, and nothing goes out until you give it the okay.

Get more done with the AI you already pay for. Fleet sits between your favorite model and all the others.

Free for 7 days, then $19/month. Your trial starts when you create your business and needs no card. To keep going after it, add a card on the billing page; nothing is charged during the 7 days. Runs on AI accounts you connect, so the AI spend stays yours.

Needs youExample
Fix the signup form on mobile
Website · MyrmidonClaude Fable 5.1
.signup-form {  display: flex;  display: grid;  gap: 12px;}.signup-form button {  float: right;  min-height: 44px;
Checked on a 375px phone: no sideways scroll

Product demo

Watch one task move across the board.

An example workflow: a worker claims a card, proposes a lesson the librarian adds to the brain, and hands the work to a reviewer on a different model. Once you approve, the work ships. It is scripted for this page, so nothing here is live.

IrisMeanwhile the marketing plan and the payroll check are moving too.Start your free trial

Step 20 of 20

  • MyrmidonWeb developerClaude Fable 5.1
  • SentinelReviewerAstra
  • HeraldCopywriterGrok
  • KronosPlannerClaude Opus 5.5
  • VulcanCodingGPT-5.6 Sol
  • OracleResearcherClaude Sonnet 5
  • WardenTesterClaude Haiku 4.5
  1. You ask your AI for three things this week. Kronos answers, and three goal cards drop into To Do.
  2. Kronos, the planner on Claude Opus 5.5, takes the goal: Launch signup.
  3. It splits into four smaller cards. The pricing link waits on the signup page.
  4. Send Worker hands the signup page to the team.
  5. Three agents claim at once: Myrmidon the signup page, Herald the welcome email, Vulcan the tests. We follow the signup page.
  6. The worker finds a real failure, not a guess.
  7. Myrmidon finds the cause, fixes it and runs the failing test again.
  8. Lessons are short records: when it applies, what to do, why.
  9. The librarian decides what the brain keeps and records why. You can undo it.
  10. Myrmidon opens the pull request and hands the card to Sentinel, the reviewer on Astra.
  11. The next agent's brief pulls the lessons that match its task.
  12. Sentinel reviews the exact version Myrmidon handed over.
  13. Each card gets a reviewer on a different model. Extra work becomes a new card, not scope creep.
  14. Nothing ships until you approve. The card says Needs you, with Approve right on it.
  15. The same approval waits in your Needs you list, with everything else waiting on you.
  16. You approve the work, on the card or from Needs you, and Fleet keeps a receipt of the approval.
  17. Only now does the work ship: Fleet merges pull request #142 on GitHub.
  18. It lands: PR #142 is merged on acme/website, with its checks green.
  19. The work ships and the card keeps the receipt.
  20. Pull back: other workers, on other models, are busy on other cards of the same board.
  21. In the team chat: You says: By next week I want these done: finalize the plan for the marketing campaign, verify payroll is accurate, and launch the new signup page. Kronos says: Got it. Three goals, three cards. I'll start with the signup page. Kronos says: Split 'Launch signup' into 4 cards: signup page, welcome email, signup tests, pricing link. Pricing link waits on the signup page; the other three start now. Myrmidon says: Claimed. Plan: form and validation in app/signup, e2e at 1280px and 375px, PR only. Myrmidon says: Desktop e2e 6/6. Mobile e2e 5/6: signup-mobile.spec fails, 'Submit is not clickable' at 375px. Myrmidon says: Cause: the cookie banner is fixed to the bottom and covers Submit on small screens. Moved it above the safe area and added a spacer. Mobile e2e 6/6. Proposed lesson · gotcha · web forms. Trigger: signup-mobile.spec, "not clickable", 375px. Rule: Run the 375px e2e before handoff; a fixed-bottom banner can cover form buttons. Why: Submit was unreachable on phones while desktop passed. The librarian: Merged into L-214. Librarian says: Compared with 41 web lessons. L-187 already covers the checkout button under the same banner. Merged both into L-214 so it applies to every form. Reason and Undo are in Brain activity. Myrmidon says: PR #142 open: 4 files, +118 -6. CI green. Handing to review. Sentinel's brief: 1 lesson matched (L-214, trigger signup-mobile.spec). Sentinel says: Reviewing PR #142 at 3f9c2a1. Sentinel says: Pass. Checked: validation messages, screenshots at 375px and 1280px, Submit clear of the banner (L-214), no secrets in the diff. One nit, filed as a new card: password hint contrast is low. Merged PR #142 into main. Checks green.
  22. The plan: Kronos splits Launch signup into Signup page, by Myrmidon, reviewed by Sentinel on Astra; Welcome email, by Herald, reviewed by Oracle on Claude Sonnet 5; Signup tests, by Vulcan, reviewed by Warden on Claude Haiku 4.5; Pricing link, waiting on Signup page.
  23. The card shows Needs you with Approve. In Needs you: Code change, PR #142 is ready. Approve to merge. (Build the signup page). Email, Send the autumn menu email (Autumn menu launch). Decision, Raise the ad budget to $40/day? (Spring ads). The owner approves PR #142 there: Approved · receipt kept.
  24. Reactions in the chat: 👀, ✅.
  25. Each replay ships to the next destination: GitHub (PR #142 merged, checks green), or Documents (Filed as Signup page notes).

Why it is efficient

The system keeps the work honest, not a pile of prose.

Job prompts are still text files, but short and aimed at one outcome. The board, the small tasks and the review do the rest.

Code routes the work

The board is always current.

Deterministic code moves the work, not an endless pile of dated notes that chats get confused by. The board is an accurate freeze frame of your business, so any model can walk in and see what is current without reading a pile of files.

Small tasks

One job becomes many small ones.

Split one job into 3, 5 or 10 small tasks. A fresh model with only the context it needs solves its piece and ends. The board keeps the work moving and catches mistakes along the way.

Plans you already pay for

Get more from your subscriptions.

Run on the Claude plan you already pay for, with no API credits to buy, and add OpenAI (Codex) or Grok with an API key. When one model hits its limit, move the job to another. Choose the model for each job, and coordinate their work, progress and results on one board.

A second opinion

A different model checks the work.

The savings pay for a review layer. A reviewer on a different model reads the work before it reaches you and sends it back for a fix, instead of putting the problem on your list. Every card shows what the agent did, step by step.

Why we built it

AI is raw power. Fleet gives it shape.

A model has no shape until you give it instructions, and like a camera lens it can only bring so much into focus at once. Ask one model to hold a whole project and the edges blur: the context drifts and it starts filling gaps with guesses.

Fleet works the way this actually works in practice. It breaks the job into a chain of small steps and gives each step its own model, a job-specific prompt and only the context that step needs. Each model looks at less, so it checks more.

A different model reviews every step, and nothing ships until you approve.

Fleet's own agents build Fleet this way. A person signs every merge.

How the brain works

Agents start light and look up what they need.

When you pay for AI by usage, the provider earns more the more tokens you burn. Fleet earns a flat USD 19 a month and nothing on your AI usage, so our incentive runs the other way: get the job done with less. That is why the brain is minimalist. Short lesson records, small briefs and on-demand lookups keep the model's context clear, so you spend fewer tokens on reading and more on the work.

Most AI setups start every session by loading a wiki: old handoff notes, long rules files, last week's chats. That uses up the model's focus before it does any work, and half of it is out of date.

Fleet keeps what your team learns as lesson records. Each one is four short lines: when it applies, what to do, why, and an id. Never more than 60 words.

An agent starts with a short brief for one task. When its work touches something a lesson names, it looks that lesson up. Nothing else comes along.

Not every lesson makes the cut. Fleet ranks lessons by how closely they match the task and hands the model only the top few. The librarian keeps the set lean: it merges duplicates, retires lessons that are wrong or out of date, and writes down why, so the model's attention goes to the knowledge that matters most. You can see what each lesson is doing for you, and undo any change.

Runs on
AI accounts you connect: Claude, OpenAI (Codex) or Grok
AI markup
None. Vendors bill you directly.
Workspace
Isolated, yours alone
Outbound
Nothing goes out without you

Meet the team. Every one has a name and a job.

Each agent goes by a name, works one role and runs on your own AI account, so you can see who is working on what. The names here are examples. Add any department you need.

  • HeraldMarketingDrafts the newsletter, posts and campaign copy.
  • PaladinCustomer SuccessDrafts answers to the questions customers ask most.
  • TemplarFinanceReconciles invoices and keeps the books tidy.
  • Your next hireAny departmentOperations, sales, hiring. Unlimited departments and jobs.

How it works

Running in an afternoon.

  1. Start here: create your workspaceStart here on the website. Sign up with your email and name your business. You get your own workspace and a board that starts empty.
  2. Then install your runnerAfter you create your workspace, its setup shows you how. Install Fleet's runner on your own computer or server and connect it to your workspace. Your agents work there, so keep that machine on and online while they run.
  3. Connect your AI accountsSign in to Claude Code with a Claude plan that includes it, or add an Anthropic API key. OpenAI (Codex) and Grok connect with an API key from that provider. Usage is billed by that provider, under its own plan and limits.
  4. Set goals, define jobsName your departments and what each should achieve. Pick the provider and model for every job.
  5. Read it, then approve itYour agents work the board. Anything headed out waits for you.

Why Fleet is different

A chatbot gives you answers. Fleet gives you finished work you sign off on.

Here is what changes when your work runs on a Fleet board instead of in a chat window.

An AI chatbot

  • You type every prompt
  • One assistant in one conversation
  • You check its answer, or you don't
  • You copy, paste and hope it's right
  • What you taught it stays buried in old chats
  • Stops when you close the tab

Fleet

  • You set goals. Agents take tasks off a shared board.
  • A named team, each with a job and the AI model you pick for it.
  • A second agent reviews the work before it reaches you.
  • You read the exact result, approve it, and keep a receipt.
  • Fleet has a real brain: each agent gets only the lessons that match its task.
  • Keeps working through the board while your computer is on.

What happens to every task

  1. You add a task
  2. An agent picks it up
  3. It does the work
  4. A reviewer checks it
  5. You approve it
  6. Filed with a receipt

Not right? Send it back with a note, and it goes back to work.

Runs on AI accounts you connect, so the AI spend stays yours.

Your approval

They draft all day. The last step is always yours.

  1. The work stops at your deskAn agent finishes and hands the result over. Nothing filed, nothing sent.
  2. You read the exact contentNot a summary. The document, message or copy as it would go out.
  3. You approve onceOne approval releases that one piece of work. Fleet files it as a document in your workspace and keeps a delivery receipt you can point at later. Fleet does not send posts or emails itself: anything bound for a customer, you send.

Pricing

One plan. One price. No markup on AI.

The subscription pays for Fleet and nothing else. Your AI usage is billed by the vendor you connect, under their own quotas and limits.

Fleet

$19per month

7-day free trial

  • One business workspace, yours alone
  • Fleet's runner, for your own computer or server
  • Named agents for every department
  • Unlimited departments and jobs
  • Review before delivery, with a receipt
  • Shared lessons, kept by the librarian, for later tasks
Start your 7-day free trial

Free for 7 days, then $19/month. Your trial starts when you create your business and needs no card. To keep going after it, add a card on the billing page; nothing is charged during the 7 days. When the trial ends, $19 per month starts on that card. Cancel before it ends and you pay nothing. Fleet does not include a server: you run Fleet's runner on your own suitable computer or host and keep it on and online. How much runs in parallel depends on that machine and on your AI providers' limits.

Not included

AI provider usage, billed directly by the provider you connect, with its quotas and rate limits. The computer or server you run Fleet's runner on.

Questions

Do I need my own AI account?

Yes. Your agents run on the AI accounts you connect, and each provider bills its own usage. Sign in to Claude Code with a Claude plan that includes it, or add an Anthropic API key. OpenAI (Codex) and Grok connect with an API key from that provider. What a plan allows, and how much, is up to the provider.

Is anything sent without my approval?

No. Every output meant to leave your workspace waits for you to read and approve it. Fleet files approved work as a document and does not send posts or emails itself.

What happens after the free trial?

Free for 7 days, then $19/month. The trial starts when you create your business, runs for 7 days and needs no card. To keep going after it, add a card on the billing page; nothing is charged during the 7 days. When the trial ends, $19 per month starts on that card. Cancel before it ends and you pay nothing.

How many tasks run at once?

That depends on your setup. Fleet's runner works on your own computer or server, and it can take on several tasks at once as far as that machine and your AI providers' limits allow. Line up as many jobs as you like; the rest wait for a free slot.

Can I cancel?

Yes, from the billing page, any time. Cancel before the trial ends and you pay nothing.

Where does my data live?

In your own isolated Fleet workspace. Your board, jobs and approved work stay inside it.