Skip to main content

​
What it is

A fleet follows saved instructions to handle repeated work. Your account owns its workspaces, billing, and model settings. The API calls the account a tenant.

​
Why it exists

You set up repeated work once, then review results in the fleet’s conversation and activity stream. Workspace permissions control who can access the fleet.

​
How it behaves

Describe a task in a private setup chat. Review the proposed instructions, access, and budget, then save the fleet. A message or another declared trigger starts a run. The fleet uses its allowed tools and returns a result. Memory can keep useful information for later runs. Authorized workspace members can stop, resume, or kill a fleet. Deleting a killed fleet removes its records permanently.

​
Limits

A fleet receives only its declared tools and secrets. Network restrictions depend on the tool and runner settings. Budgets, account balance, and model limits can block new work.