An agent slot runs one task at a time. Slots are how you buy throughput.
For what a slot does and does not do, read Capacity and agent slots first — in particular, that slots do not make an individual task faster.
Buying slots
Manage capacity under Settings → Billing → Capacity & credits.
Professional includes one standard slot, with more available per slot per month. Enterprise runs on contracted capacity with a minimum commitment and priority processing.
Slots are a standing monthly commitment rather than metered usage. An idle slot costs the same as a busy one — which is what makes the bill predictable, and what makes over-provisioning genuinely wasteful.
Sizing capacity
Use your queue, not your intuition.
Run for a week and watch how long tasks sit in PENDING. If they start promptly,
you have enough. If they consistently wait while you want results, add a slot.
Things that look like a capacity problem but are not:
- Individual tasks feel slow. That is scope and test-suite duration. More slots will not help.
- A plan runs one phase at a time. Its phases depend on each other; they would serialise with a hundred slots.
- Everything is marked
P0. Priority orders the queue, it does not add capacity.
Priority
Tasks carry P0 (highest) to P3. When more work is queued than there are
slots, priority decides order.
On the free plan the single slot is low priority, which means evaluation work does not compete with paying workloads.
Scaling down
Reduce slots when your queue is consistently empty. Removing a slot does not interrupt work already running — it takes effect once the current task finishes.
Changing capacity mid-month
Adding a slot takes effect immediately so it can start absorbing the queue. Billing is prorated.