@wzrdtech/zap@5.0.1) turns Zap from one-click generative media recipes into a composable CPU agent runtime: an npm package, a CLI, an MCP server, and a skill set that let an agent or a human compose a runtime from plugins, boot it on an isolated VM, and run agents written as code — plan-only by default, with explicit metered live spend.
Why CPU
Agents mostly do; they do not mostly think. Running code, clicking, reading files, calling APIs, and writing outputs are CPU workloads. Zap v5 is the runtime for that work — GPUs and LLMs are plugins it calls, not the substrate it runs on.How it works
- Agents compose runtime plugins. A runtime is a plugin graph declared in
Runtime.md;zap composeresolves the graph and boots it on a sandbox. - CPU work runs in tenant sandboxes. Every command goes through
sandbox.execon an isolated Box VM (noEnv: true); Namespace, self-host, microsandbox, E2B, Daytona, Cloudflare, Modal (GPU lane), and Docker adapters share one contract. - Plan-only is the default. Side-effecting tools emit
tool.plannedwith price estimates; nothing spends without--liveand a payer. A missing payer fails closed withPAYER_MISSING. - The gateway owns provider keys. LLM and media provider keys stay server-side; they are never copied into managed VMs, bundles, logs, or
--jsonoutput. - Agents as code.
agents/<id>/agent.tsrenders the next step’s instructions; hooks attach a model, tools, MCP servers, and subagents. Deployments are immutable and sha-addressed; sessions are durable.
What changed from 0.3.1
The 0.3.1 recipe framework is preserved in v5 — recipes still validate and run, and
defineRecipeTool wraps a recipe as an agent tool. Legacy recipe docs live under Legacy.
Quickstart
Compose your first runtime with
npx @wzrdtech/zap@5.0.1.Agents quickstart
Build, render, deploy, and talk to your first agent in five minutes.
Core concepts
Kernel, plugins, profiles, sandboxes, plan/live, sessions.
CLI reference
Every command with flags, exit codes, and
--json shapes.Use Zap from your agent
One command connects Claude Code, Cursor, Codex, Devin, and more over MCP.
MCP
Stdio and Streamable HTTP transports with ten tool domains.
