Skip to content
CapletsCaplets Docs

Caplets

Caplets is the capability layer for coding agents. Turn MCP servers, OpenAPI and Google Discovery APIs, GraphQL endpoints, simple HTTP actions, and curated CLI commands into reusable Caplets your agent can use across the work surrounding your code.

Your Whole Stack is the set of capabilities you intentionally expose through Caplets—not blanket access to every system or credential. Caplet definitions can be reused across Codex, Claude, OpenCode, Pi, and supported MCP clients while each host independently supplies and authorizes access.

Code Mode is the default surface: each configured backend becomes a typed caplets.<id> handle that an agent can inspect, search, call, filter, and summarize in one workflow. Direct and progressive exposure remain available for clients and tasks that need them.

Required upgrade migration: If this host ran caplets@0.25.x or earlier, do not start caplets@0.26.0 or later until you complete the one-time legacy-state migration. Caplets does not automatically migrate or fall back to the old auth, Vault, remote-security, setup, activity, and tracked-Caplet stores.

Quick Start

Section titled “Quick Start”

Install the CLI, then run a known-good no-auth setup first. OSV is public, so it is the fastest way to prove your agent can see and call a Caplet.

Terminal window
npm install -g caplets
caplets setup
caplets install spiritledsoftware/caplets osv
caplets doctor

Use npx caplets ... only for temporary foreground commands; daemon-backed agent setup expects a stable installed caplets binary on PATH.

caplets setup is daemon-first: it initializes Caplets config, starts or reuses the local Caplets daemon, and configures your agent as a thin caplets attach <local-daemon-url> or native client. The daemon owns backend execution and environment passthrough, so agent configs do not need secrets or provider-specific environment values.

doctor should identify the active Caplets config path and report the checks it can run for your configured integrations. Fix any failed check before testing through an agent.

Then ask your agent to use Caplets Code Mode to query OSV for npm package react@18.2.0, returning the package, version, vulnerability count, and advisory IDs as compact JSON.

A successful agent run should use the visible caplets__code_mode tool and inspect an OSV handle such as caplets.osv. If the agent cannot see that tool, go to Troubleshooting.

First success shape

Section titled “First success shape”

The exact OSV data can change over time, but the result should have this shape:

{
  "package": "react",
  "version": "18.2.0",
  "vulnerabilityCount": 0,
  "advisoryIds": []
}

If the package has advisories, vulnerabilityCount should increase and advisoryIds should contain the OSV identifiers the agent found.

Section titled “What to read next”