> ## Documentation Index
> Fetch the complete documentation index at: https://getskydive.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Sizes

> How much machine an agent gets, and how it asks for more

Every agent's computer has a size: how much CPU and memory it gets. Most agents never need to think about it. Some jobs do.

## The ladder

Sizes run from smallest to largest:

```
xsmall  <  small  <  medium  <  large  <  xlarge  <  xxlarge  <  xxxlarge
```

An agent can see its own size and which sizes it could move up to. It cannot resize itself.

## Asking for more

When a job is genuinely compute-bound, the agent requests a bigger machine and explains why. A test suite that runs out of memory, heavy parallel work, or a large data pass are the usual reasons.

<Steps>
  <Step title="The agent asks">
    It requests a specific size with a reason, and an Approve or Deny card appears in the conversation.
  </Step>

  <Step title="Someone decides">
    A person who can edit that agent approves or denies it. Cost is a human's call, which is why the agent cannot do this on its own.
  </Step>

  <Step title="It restarts at the new size">
    On approval the size is raised and the sandbox restarts, so in-flight work is checkpointed first. The agent resumes once it is back.
  </Step>
</Steps>

An agent can only request a size above its current one, and only one request can be open at a time.

<Note>
  A resize request needs a live conversation, because it needs someone to approve it. A [routine](/docs/agents/routines) firing with nobody watching cannot request one.
</Note>

## When a bigger machine is not the answer

Reach for a resize when the work does not fit in memory or takes far too long on the current size. Do not reach for it when the real problem is scope: an agent doing five unrelated jobs is better split into several agents, or given [subagents](/docs/capabilities/subagents) to spread the work.

<Card title="Track what it costs" icon="chart-line" href="/docs/account/usage">
  Compute draws on your credit balance alongside model usage.
</Card>