Skip to main content
Zap requires Node 24.x. Every command supports --json: humans get text, agents get JSON.
1

Check your setup

doctor reports Node version, payer mode (byok | managed | missing), sandbox availability, and template status.
2

Compose a runtime

compose resolves Runtime.md (or zap.config.ts) into a deterministic plugin tree without acquiring anything. Equivalent Runtime.md and zap.config.ts definitions produce identical trees and lock hashes. Drop --dry-run to boot the runtime on your sandbox.
3

Manage the runtime

zap runtime also supports logs, snapshot, fork, stop, resume, and desktop. zap fs <ls|read|write|rm> <runtime-id> <path> operates on the runtime’s filesystem.
4

Stay plan-only, or go live

Plan-only is the default everywhere. Side-effecting work emits tool.planned events with cost estimates. To spend for real:
No payer + --live fails closed with PAYER_MISSING — never a silent downgrade.

​
Install options

Or project-local: npm install --save-dev @wzrdtech/zap, then npm exec -- zap --version.

​
Next steps

Agents quickstart

Write, deploy, and talk to an agent as code.

Runtime profiles

Choose between zap-light, zap-med, and zap-heavy.

Use Zap from your agent

One command connects Claude Code, Cursor, Codex, Devin, and more over MCP.

Sandboxes

Box-first isolation with nine providers behind one contract.