Dedicated AI agent fleets

# Your problem. A thousand agents. 

Hours or days on your problem.  Inference, computers and coordination.
[Get started](/pricing/) 

Stop background motion

Already using Claude Code or Codex?

## Plan a fleet for your project.

Paste the link into the conversation where you’re already working. Ask what to put the fleet on.

Copy link + question[See how it works ](/evaluate/) 

A fleet for your project

## Give your coding agent  256 more.

You have a codebase, a difficult problem and ideas you haven’t had time to try. Give them a fleet. Each agent has a computer to write code, run experiments and share discoveries.

Multiplet runs the models, environments and fleet. Your agent brings the work back into your project.
[Meet the fleet ](/features/) 

 agent-042 / workspace Linux 

project /src / tests / bench / results / 
A working environment 
Read the code.  Try a change.  Run the checks.

$ ./run-tests  Checking the implementation… 
Code · dependencies · tools · files

## More work on your project.  In the session you already use.

Self-service access  Coming soon 

01 / Your project 

### The conversation  you already have.

Your agent knows the code, the constraints and what you’ve tried.

Claude Code / Codex Let’s put a fleet on this.
02 / A fleet run 

### More approaches.  Working in parallel.

Agents write code, run experiments and share useful discoveries.

03 / Back to your project 

### Pick up  the useful work.

Your original agent retrieves the files and helps you test and use them.

Proposed changes Experiments & tests Findings & activity [How a run works ](/how-it-works/) 

From a fleet run / Java migration

## A migration  that builds again.

After OpenRewrite updated Restlight, its Java 17 build still needed repairs. The fleet returned a four-file patch. A separate replay completed the build with all 729 original tests passing.
[Follow the repair ](/examples/java-migration/) 

Restlight / Java 17 Replayed result 
Prepared migration Build blocked
Build tools and source still needed changes.

Returned patch · 4 files Build passing ✓
729 original tests passed.  219 test files unchanged.

Put it to work

## The work you’ve been  meaning to get to.

[01 

### Find the failure before the release.

Investigate behavior across inputs, platforms and configurations.
](/use-cases/software-correctness/) [02 

### Get the migration building again.

Work through dependency, compiler and integration failures.
](/use-cases/code-migration/) [03 

### Try a faster implementation.

Explore changes and measure them against the code you use today.
](/use-cases/performance-optimization/) 

## Give your project a fleet.

Start with the work already open in Claude Code or Codex.

[Explore your first fleet ](/first-fleet/) [Ask your agent what to run ](/evaluate/)