Computers and environments

# Your project.   Ready for the fleet.

Prepare the code, tools and dependencies once. Give every agent a working place to start.

 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
On this page [Run the work ](#section-0) [Prepare once, use across the fleet ](#section-1) [CPU sized for the work ](#section-2) [Room for different workloads ](#section-3) [Read as Markdown ](/features/environments/index.md) 

## Run the work

Agents can build software, execute scripts, query data and run experiments. They inspect the output and decide what to try next.

## Prepare once, use across the fleet

Start from a prepared Linux image. Add your dependencies and tools, then reuse that environment across agents and future runs.

## CPU sized for the work

Each agent has its own computer. CPU capacity is shared, with allocations sized for the tools it needs. Tool execution alternates with model responses, so many tasks can use fractional CPU allocations. Larger builds and analyses can use larger environments.

## Room for different workloads

Combine smaller environments with larger machines for memory-intensive analysis or builds. The fleet can share work between them.

[How it works ](/how-it-works/) [Run your first fleet ](/first-fleet/) 

## Put a fleet on your project.

256 agents. Four hours. $1,000 for your first run, with model inference, computers and fleet operation included.

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