An agent slot processes one Task at a time. Slots are what you use to purchase throughput.
To learn what a slot does and does not do, read Capacity and agent slots first — in particular, that slots do not make an individual Task run faster.
Purchasing slots
Manage capacity via Settings → Billing → Capacity & credits.
The Professional plan includes one standard slot, with more slots available each month.
Enterprise operates on a contracted capacity with a minimum commitment and Priority processing, and is currently in private preview — see Plans and pricing.
Slots represent a recurring monthly commitment rather than metered usage. An idle slot costs the same as an active one — which keeps the bill predictable and makes over-provisioning truly wasteful.
Sizing capacity
Use your queue, not your intuition.
Run for a week and observe how long Tasks remain in PENDING. If they start promptly,
you have sufficient capacity. If they consistently wait while you need results, add a slot.
Issues that appear to be capacity-related but are not:
- Individual Tasks feel slow. That relates to scope and test-suite duration. More slots will not help.
- A plan processes one phase at a time. Its phases depend on each other; they would serialise even with a hundred slots.
- Everything is marked
P0. Priority arranges the queue; it does not add capacity.
Priority
Tasks carry P0 (highest) to P3. When more work is queued than there are
slots, priority determines the order.
On the free plan, the single slot has low priority, meaning evaluation work does not compete with paid workloads.
Scaling down
Reduce slots when your queue is consistently empty. Removing a slot does not interrupt work already in progress — it takes effect once the current Task finishes.
Changing capacity mid-month
Adding a slot takes effect immediately so it can start handling the queue. Billing is prorated.