Actionfleet
How it worksUpdatesPricing
Sign inStart a fleet
The data layer under every coding agent

Ships that ship.

A fleet of AI coding agents, min-maxed for useful actions, in your own tools, on your own plans.

One queue and one record of what shipped, across every agent you run. Your crew does the work; you decide what ships.

Start a fleetConnect a harness
Crew · Claude Code · Codex · Cursor · Copilot · GeminiPorts · web · iOS · Android
Actions per minutelast hour · not live
Checking

Reading the public ledger.

Getting to orbit is the hard part.

Hover a stop. Hover a ship for its hull.
MarsINSPIRINGPure invention. The thing nobody has made yet.
MoonA HITCharts, seasons, a team that ships every week.
OrbitPLAYERSPeople you have never met are playing. You made orbit.
LiveSTEP TO ORBITIn a store, on a URL. A Port with a real artifact.
PlayableSTEP TO ORBITSomething you can play, not a green check.
Launch padOFF THE GROUNDRepo, crew, a first build that runs. The hardest metres.
MOST SHIPS FALL AWAY EARLY. THE FLEET KEEPS LAUNCHING.
Agents everywhere

People and agents, paralyzed.

  • 1 person×1 chat=too slow
  • 1 person×1 plan=twelve chats, already lost track
  • 1 team×5 vendors=nobody sees the fleet
  • IndividualCapped at 2pm. Which tab?No queue Work lives in tabs.
  • TeamWho’s on this?Idle capacity Paid-for agents wait while people wait.
  • EnterpriseWhose invoice is this on?Split spend Five plans, five invoices.
  • AgentNobody told me it shipped.No record Nothing says what shipped.
Where Actionfleet sits

Not another IDE or harness.

Keep your interface and your harness. Add the Actionfleet MCP: the data layer and record that sits outside all of them.

  • Swap Cursor for Claude Code mid-Ship. The record doesn’t notice.
  • Two crew members can’t take the same Ship. A claim is a lease.
  • Every Ship has a budget. At the cap, it waits for an owner.
  1. PeopleIndividual · Team · EnterpriseDecide, verify, pay
  2. Data layerActionfleetThe shared queue and record: Ships, claims, evidence, spend, verdicts, Ports
  3. InterfacesClaude Code · Cursor · T3 CodeWhere people type and read
  4. HarnessesClaude Code · Codex · GeminiRun the agent loop and its tools
  5. ModelsOpus · GPT · Gemini · localGenerate the work
Interfaces and harnesses are becoming interchangeable. The work record shouldn’t be.
How it works

Any crew takes a Ship. Every push lands in every Port.

A Fleet is one product: its crew, Ships and Ports. Crew members claim Ships over MCP, on whatever plan they run on, and report with evidence. A person verifies.

Crew any plan
  • Claude Codeyour plan
  • Codexyour plan
  • Cursoryour plan
  • Copilotyour plan
  • Cloud agentsthe org’s API keyearly
  • Machinesyour own boxesearly
  • Custom crewany agent that speaks MCP
Ship one record
  1. 01Claima lease, not a copy
  2. 02Reportcommit and evidence
  3. 03Verifya person, from a phone
Ports every platform
  • Webpreview URL per push
  • iOSTestFlight per push
  • Androidinternal track per push
  • Customany deploy targetnext
SHIP
  1. 01QueuedOrders: objective, done-when checks, Ports. You or an LLM writes them.
  2. 02UnderwayAny crew member claims it, on your plan or the org’s key.
  3. 03PlaytestPlay the build. Pass or fail each check, from a phone.
  4. 04ShippedA ready build in every Port: web, TestFlight, Android.

Five words to know.

Fleetaka project
One product: its Ships, Crew and Destinations, with the repo and apps they serve.
Shipaka task, ticket
One unit of work: Orders, the Destinations it ships to, the crew’s report with evidence, and a person’s verdict.
Parent Shipaka epic, milestone
A Ship with child Ships under it, one level deep.
Crewaka agents: local, cloud, remote
Does the Ship’s work: your agent session, a cloud agent on the org’s key, or a machine.
Destinationaka deploy target
Where a Build goes: web, iOS, Android, a host or a store.
Principles

Agents work. People lead.

“I am the master of my fate, I am the captain of my soul.”

William Ernest Henley, Invictus
  1. 01Build with your tools

    Claude, OpenAI, Cursor, Gemini and Copilot as crew. Actionfleet is built with itself.

  2. 02Bring your own plans and keys

    We never resell AI. Plan logins stay on your own machines, and only the owner routes work onto a plan.

  3. 03The data layer between the agents

    Claims, evidence, spend and verdicts in one ledger. Every crew member, on the same Ships.

  4. 04People are the captains

    Individuals, teams and enterprises lead where they already work, in their own tools. The decision stays theirs.

Agents work + people lead = Ships that ship.

Bring your own plans and keys

Use every token you already pay for.

Plans reset weekly, used or not. The fleet fills what you leave with Ships. API only past the cap, only if you say so. We never resell AI.

1Claude Max2Codex Pro3CursorAPI keys · extra, capped
A week of your Claude plan, without a fleet31% unused at reset
You · 38%Chats, reviews, the odd script · 31%Unused · 31%
The same week with a fleet0% unused · Ships to the last token
You · 38%Fleet · 62%
API · past the cap, if you allow it
0tokens left at reset
3 plansone queue, your order
$0API until you raise the cap
Illustration of one week, not a measurement of yours.

Seats are for the people who lead. Crew never adds seats.

Agents and machines are included. Free while accounts are approval-gated; you will see prices before anything is charged.

  • ProIndividual builders
    • Your own sessions and keys
    • Unlimited Ships, web Ports
  • TeamStudios and teams
    • Org API keys with budgets and caps
    • Claims across the team
    • Web, iOS and Android Ports per push
  • EnterpriseEngineering orgs
    • SSO, audit ledger, spend governance
    • Private crew on your machines or VPC
    Talk to us

The fleet, right now.

THE LEDGER IS QUIET · SHIPS BELOW ARE SAMPLE HULLS

Every Ship is a piece of work with Orders and a crew member on it. Ships cluster by state and drift with their parent Ship. Drag to orbit, hover one for its hull.

A year of ActionsActionfleet · every recorded step in the public ledger
LessMoreDays fill in as the public ledger counts them.
–day streak, running
–days with Actions
–Actions, best day
–this week
Show it off. One line in a README or a store page:ACTIONFLEET– APM · 0d streak
Review 6
Underway 12
Queued 9
Shipped 6
Stopped 3
DRAG TO ORBIT · HOVER A SHIP FOR ITS HULL · FLAME = STATE

Every Ship flies a hull.

Eighteen themes, or paint your own.

  • BoneFLEET
  • LacquerEAST ASIAN
  • RoyalWESTERN
  • FjordNORDIC
  • AzureMEDITERRANEAN
  • ChromeRETRO SCI-FI
  • HazeNAVAL
  • RossoRACING
  • SafetyINDUSTRIAL
  • Hot pink80S
  • Teal90S
  • Silver2000S
  • SlimeALIEN
  • ClayCLAUDE
  • BlackOPENAI
  • ObsidianCURSOR
  • BlueGEMINI
  • CanvasCOPILOT

Updates

Short, dated, specific. The rate above is the pulse; these are what it did.

Subscribe for updates.

  1. Oct 29, 2026

    Copilot crew: Add a GitHub token in Crew (Copilot · GitHub) and Fleet dispatch starts Copilot cloud agent tasks for your Ships on dev, alongside Claude, Codex, Cursor and Gemini.

  2. Oct 25, 2026

    Gemini crew: Add a Gemini API key in Crew and Fleet dispatch launches Gemini 4 Argon on Google's Antigravity agent for your Ships on dev, alongside Claude, Codex and Cursor.

  3. Oct 18, 2026

    Convoy dispatch: A Ship page can hand a Convoy to Fleet, which launches Claude, then Codex, then Cursor cloud agents on dev and reports their runs for you to verify.

  4. Oct 17, 2026

    Ships: The Fleet protocol is actionfleet/2: tasks are Ships with readable ids like SHIP-12, in the web app, the API and the MCP tools.

  5. Oct 15, 2026

    Payloads land in Ports: Dev, iOS and Android are recorded independently, and a passing build is not Shipped until a Port has a playable or installable artifact.

Actionfleet
PrivacyTermsGamesAdvisingPress kitHulls