Packages and SDKs

WAMP is assembled from a set of packages, some of which are meant to be consumed from outside the platform. This page says which is which, and is honest about the part that matters most today: none of them are published to the public npm registry. Every name below returns a 404 from npm view.

That is an operational gap, not a design one. Until it closes, the packages marked consumable below are usable from a source checkout, and the HTTP surfaces they wrap — the AI proxy, the accounts API, and the Cloud API — are reachable directly and are fully documented. Where a package only wraps a signing or verification step, that step is short enough to write yourself, and the pages that describe it show how.

Packages you would consume

Package	What it does	Availability
@wamp/extension-sdk	Author extensions: manifest types, build helpers, the wamp CLI. See The wamp CLI	Not on npm. From a checkout only
@wamp/app-sdk	Server-side app identity — generate a keypair, issue end-user tokens, mint installation tokens, verify webhooks, and a typed Cloud client	Not on npm
@wamp/sdk	Embed the WAMP engine in your own Node process on your own model keys	Not on npm, and marked private
wamp-engine	The standalone secured headless core: serve, call, local. This is what the desktop app spawns	Not on npm
@wamp/ui	The React primitives, design tokens, and Tailwind preset the host itself uses. See Interface kit	Not on npm, and marked private

Packages internal to the platform

These exist because the platform is split across processes and hosts. You do not consume them directly, but knowing they exist explains the shape of everything else.

Package	What it is
@wamp/engine	The host-agnostic AI runtime: agents, runs, tasks, the tool registry, MCP, compaction, plan mode
@wamp/shared	The cross-process contract surface — one typed IPC contract per domain, plus the extension manifest schema
@wamp/api-fetch	Auth-aware HTTP and WebSocket client: token storage, the refresh state machine, the AI proxy
@wamp/remote-engine-client	Client for an engine core running on another machine
@wamp/cli-harness	Shared primitives for extensions that wrap a CLI coding harness
@wamp/runner	The sandbox runner

packages/engine-node is worth one line of its own: despite living beside the others, it has no package.json and is not a package. It is the headless Node composition layer — plus the prompt, agent-definition, and skill assets the engine ships — compiled into whichever host consumes it.

What each one wraps

If you are deciding whether to wait for a package or write the request yourself:

• @wamp/app-sdk wraps three cryptographic contracts — signing an app assertion, signing an end-user token, and verifying a webhook signature — plus a typed client over the Cloud HTTP API. The signing steps are about ten lines of jose each; Apps and credentials shows them. The Cloud client is a convenience over documented HTTP.
• @wamp/extension-sdk wraps a scaffolder, a build helper, and the manifest types. An extension is a directory with a manifest and a bundle, so the SDK is a convenience rather than a requirement — but the manifest types are the clearest statement of what is valid, and the manifest reference is derived from the same schema.
• @wamp/sdk is the one with no substitute: embedding the engine means running the engine.

Versions

Nothing here follows semantic versioning against a published history yet, because there is no published history. @wamp/extension-sdk is at 1.0.0 and wamp-engine at 3.6.1; the rest sit at 0.1.0 or 0.0.0. Treat those numbers as internal until a package actually ships, and pin by commit if you are building against a checkout.