Capsules
Capsules are portable bundles of Nova context that expose selected tools and resources through one scoped key.
A Capsule is a portable bundle of Nova context that another agent can connect to over MCP, REST, or the nova CLI. A capsule can include tools and content: integrations, documents, skills, artifacts, agents, and flows. The consuming agent uses a single key from /settings/api-keys that carries one capsule:<id> grant.
What a capsule exposes
Attach integration tools through allowedTools. For example, a capsule can expose linear_create_issue and linear_get_issue without exposing every Linear action.
Attach content through resources[]. Resource grants are id-scoped: a capsule with one skill exposes only that skill, not blanket access to all skills.
Auth and approvals
Auth stays server-side. The consuming agent never receives the integration's OAuth token, API key, or other credentials; it only holds the capsule key.
Human-in-the-loop approval also stays server-side. Side-effecting writes still pass through Nova's approval gate before they run.
CLI keys
Use the capsule's own key from capsule connect or a capsule key rotation. Do not use a personal device token for capsule consumers.
Sandboxes
Sandboxes are isolated execution environments where agents can browse, run shell commands, or drive a virtual desktop without risking the host.
Skills
Skills are reusable prompt fragments that any agent can invoke with /skill-name. They keep agent definitions short and shared knowledge centralized.