Skip to content
WAMP

Platform documentation

Build AI applications on WAMP

A substrate of agents, tools, views, and storage. Coding is one application on it — yours is the next.

QuickstartWhat WAMP is
extension.json
{
  "name": "Reading List",
  "version": "1.0.0",
  "icon": "BookOpen",
  "compat": { "pluginApi": "^2.0.0" },
  "contributes": {
    "pages": [
      {
        "id": "reading-list",
        "title": "Reading List",
        "icon": "BookOpen",
        "context": "both"
      }
    ]
  }
}

An app is a manifest, a page, and a declaration of what it may touch. The host typechecks and builds it — there is no toolchain to install.

Start where you are

Section titled “Start where you are”

I want to build something

An app is an extension that owns its window. One manifest, one build, one lifecycle. Quickstart gets a running app in front of you, then Extensions and apps explains what you just made.

I want to ship it

Ship your own branded desktop binary, or put WAMP behind a product you already operate. Choosing a path is a one-page decision.

I want agents running in the cloud

Durable sessions in managed sandboxes, driven by HTTP from any backend. Use the HTTP integration contract in WAMP Cloud.

The shape of the platform

Section titled “The shape of the platform”

Everything you build is an extension: a manifest, some code, and a declaration of what it may touch. The file tree, preview, terminal, and chat dock are core, while extensions add workbench views and workflow skills. From there the platform is a set of surfaces your extension can contribute to, and a set of capabilities it can ask for.

Contribute a surfacePages, windows, dock tools, commands, status items — the parts of the shell your extension can occupy.
Give the agent new abilitiesA tool is a function the AI can call. Agents carry a tools allowlist; extension tools stay reachable.
Store structured dataTyped collections with queries and additive schema migration, held on the machine the app runs on.
Ask for a capabilityWhich permissions withhold an API, which declare intent, and how to handle missing capabilities.

Reading this with an agent

Section titled “Reading this with an agent”

Every page here is also served as markdown, and the whole site is served as one file. Point a coding agent at the text instead of having it scrape the rendered pages.

Read one page as markdownAdd .md to any page's path — /build/manifest.md. The Copy page button at the top of every page copies the same text.
The whole site, as one filellms.txt indexes every page with its summary; llms-full.txt is the entire corpus in one document.