What the system is
The system accepts a capability request, resolves it through a provider, coordinates execution and caching, and returns something the target environment can consume. That result may be an artifact today and, in later provider classes, can also represent a runtime or remote service.
What counts as a capability
The model is intentionally broader than dependency installation.
- Packages: Cargo crates, JavaScript packages, Go modules, Python wheels.
- Tools: binaries such as protoc, ffmpeg, chromium, or language servers.
- Toolchains: compilers, runtimes, SDKs, and native libraries.
- Models and data: weights, tokenizers, indexes, and build assets.
- Services: MCP servers, APIs, databases, browser/GPU/remote execution.
Core model
The public model does not depend on GitHub Actions, Cloudflare KV, Cargo, or a particular sandbox implementation.
What is implemented today
Cargo is the first production provider. It turns a Rust manifest and optional lockfile into an offline-ready dependency artifact. The surrounding provider, job, cache, event, execution, and storage interfaces are generic.
Start with the stack you already use
- Cargo — available today.
- pnpm / npm — target product experience.
- Go — target product experience.
- Python / uv — target product experience.
After the stack-specific guide, use Capabilities to understand the wider product surface, Providers to understand extensibility, or Architecture for the control plane.
OpenAPI is available for direct programmatic integration.