// Browser build

PasClaw runs in a browser tab

The browser build packages PasClaw for WebAssembly so users can run the agent loop, tool calls, and memory from a static web deployment.

WebAssemblyNo installStatic hostingClient-side

Compile the native stack for the web

The container2wasm-based build carries the PasClaw runtime into a browser-compatible environment instead of rewriting the agent in JavaScript.

Host the browser build from a static site without maintaining a dedicated PasClaw application server for every user session.

Agent orchestration and local state stay in the browser environment; model requests only go to the providers the user configures.

A browser tab gives developers and users a low-friction way to try PasClaw before installing or integrating the native executable.

From the documentation

Implementation notes drawn from the PasClaw repository documentation.

Rather than porting PasClaw directly to wasm32, container2wasm runs the unmodified Linux binary in a WebAssembly-hosted Linux environment.

This preserves sockets, threads, subprocess behavior, and SQLite expectations.
c2w-net-proxy uses a gVisor network stack to bridge Indy HTTPS through the browser Fetch API.
PASCLAW_C2W enables the proxy-aware build path.

The browser artifact is built as a dedicated target and must be launched with browser networking enabled.

make C2W=1 browser
# launch the generated app with:
?net=browser

The browser image onboards and starts the agent in the tab; static assets can be hosted without a PasClaw application server.

Users provide the model-provider credentials used by their session.
Agent state and orchestration remain in the browser environment.
After upgrading an old build, clear the stale service worker and site data if cached assets continue loading.

Common questions

Keep exploring

See how the rest of PasClaw fits together.