How Capsules works for teams and agents.
This is the high-level product model: what a capsule is, how an AI agent uses one, where the limits are, and how credits map to active work. Internal control-plane and host details are intentionally left out.
What a capsule is
A capsule is a small Linux environment you create through an API, CLI, SDK, or console. It is useful when an AI agent needs somewhere safe to clone code, install dependencies, run tests, expose a preview URL, and keep working state between sessions.
First agent workflow
Create a restricted agent token, choose an approved size, start a capsule with a task name, run commands, inspect logs, and terminate the capsule when the work is merged or abandoned.
Restrictions
Capsules are meant for controlled development and automation tasks, not unrestricted public hosting. Beta defaults keep sizes, regions, public URLs, private-network access, and idle behavior intentionally bounded.
Credits and usage
Usage is shown as a ledger: active compute minutes, persistent storage, lifecycle events, and preview traffic. The initial onboarding flow starts with $5 of credits so a team can test real agent tasks without a sales call.
Quickstart shape
Exact command names may change before public release, but the end-user workflow should feel like this: create a restricted token, start a capsule, run the task, inspect the result, and terminate it.
Step 1
Create a token
Create a token
capsule tokens create --scope agent:write --prefix agent-Step 2
Start a workspace
Start a workspace
capsule create agent-pr-482 --size 2x2gb --credit-limit 2.00Step 3
Run the agent task
Run the agent task
capsule exec agent-pr-482 -- npm testStep 4
Terminate when done
Terminate when done
capsule terminate agent-pr-482Current beta framing
Capsules is aimed at controlled engineering and AI-agent automation. It is not positioned here as a general public cloud, global hosting platform, GPU environment, Windows environment, or unlimited free tier.