Pods

A pod is the compute environment where an agent runs. It pairs two things:

• A server: a persistent process that holds state and stays reachable between tasks.
• A sandbox: an isolated environment where code actually runs, with its own filesystem, CPU, and network boundary.

The pod fuses both into one managed unit, so the agent has a place to be (the server) and a place to do (the sandbox) without you wiring them together.

Isolation

A pod is an isolation boundary. Each pod has its own compute, its own attached vaults, and its own member list. Agents in different pods can’t see each other’s files, processes, or secrets.

Pods and projects

A pod runs one or more projects, and every project belongs to exactly one pod. Projects on the same pod share its server, sandbox, and network, so they coordinate cheaply while staying logically distinct.

Most projects are lightweight and don’t need a dedicated pod. Give a heavy workload its own pod when you want to isolate it from everything else.

Default pods

• Every user gets a private pod automatically: yours alone, no setup required.
• Every organization gets a pod named general. Teammates you add get access to its projects and agents with no extra configuration. It comes with a default project and a default vault already attached.

You can create more pods whenever you need a new isolation boundary.

Membership

Pods are shared through two roles:

• Owner: can manage the pod’s configuration, members, and attached resources.
• Member: can use the pod’s compute and access its projects, but can’t change the pod itself.

This is deliberately coarse. A pod is an infrastructure boundary; fine-grained access control over agents and data is handled at the project level.

Vaults

Vaults attach to a pod with a priority. When the same credential exists in more than one attached vault, the higher-priority vault wins, so a team vault can override org-level defaults for specific keys without replacing the org vault. Every pod gets a default vault at creation, so agents always have somewhere to store and retrieve secrets. See Vault.

Where to go next

• Projects: how agents, skills, and stores are grouped inside a pod.
• Environments: networking and package configuration for a pod’s sandbox.
• Agents: what actually runs inside a pod.