@agent-wasm/* is the published browser-native Node/agent package line. wasm-vm is this repository's RISC-V Linux machine. They can sit in one product, but they are different artifacts, targets, and release streams.
This is a registry snapshot queried on 2026-08-30. These packages are published from the separate BLamy/agent-wasm repository, not from this wasm-vm checkout.
@agent-wasm/coreNode.js in the browser: a virtual filesystem, runtime/sandbox workers, package manager, dev-server bridges, Electron shims, and container/network helpers.
npm install @agent-wasm/core@0.4.0/internal, /vite, and /next exports.@agent-wasm/sdkWorkspace and agent-lifecycle APIs over @agent-wasm/core: snapshots, agent sessions, adapters, workspace templates, and plugins.
/auth and /plugins exports.@agent-wasm/reactReact workbench, chat, and UI components for agent-wasm workspaces. It composes with the SDK and the framework-free chat domain package.
npm install @agent-wasm/react@0.1.0 with the SDK, chat-core, React, and React DOM for the full workbench./workbench, /chat, or /ui.The npm metadata identifies the listed agent packages as MIT-licensed, except @agent-wasm/tailscale-connect, which is BSD-3-Clause. Re-check the package metadata before redistributing a dependency bundle.
| Package | Version | What it contains |
|---|---|---|
@agent-wasm/chat-core | 0.1.0 | Framework-free chat domain types and session registry. |
@agent-wasm/code | 0.1.0 | Claude Code transcript parsing and browser IDE bridge helpers. |
@agent-wasm/vscode | 0.1.0 | VS Code-shaped shell and React integration APIs. |
@agent-wasm/keychain | 0.1.0 | Browser credential vault, OAuth orchestration, and session persistence. |
@agent-wasm/codex | 0.1.0 | Browser-hosted Codex sessions and WASM worker bridges. |
@agent-wasm/tailscale-connect | 1.39.98-t02582083d | Tailscale Connect browser SDK fork; npm metadata identifies it as BSD-3-Clause. |
Use a package manager and bundler for the published agent packages. Pin exact versions in the consuming lockfile; the package pages and repository links below are the provenance trail.
npm install @agent-wasm/core@0.4.0
import { createContainer } from "@agent-wasm/core";
const container = createContainer();
container.vfs.writeFileSync(
"/index.js",
"console.log('hello from the browser')",
);
await container.run("node index.js");npm install @agent-wasm/core@0.4.0 @agent-wasm/sdk@0.1.0
import { createWorkspace } from "@agent-wasm/sdk";
const workspace = createWorkspace();
workspace.vfs.writeFileSync("/index.html", "<h1>hi</h1>");
await workspace.snapshots.save();Release URL: the verified @agent-wasm/core@0.4.0 registry tarball is the package artifact. The registry metadata exposes bundler entry points and subpath exports; no direct browser CDN URL is claimed here, so do not turn a guessed CDN URL into a script tag.
The agent packages above run on the host side of a browser application. The file-transfer agent below runs inside the RISC-V Linux guest. The wasm-vm host module is a third artifact again.
wasm-vm-file-agentThe guest-side WVFT v1 service from crates/file-agent. Current Cargo metadata reports version 0.0.0; tools/build-file-agent.sh targets riscv64gc-unknown-linux-musl and the rootfs build installs it as /usr/libexec/wasm-vm/wvft-agent.
10.0.2.2:10021/var/lib/wasm-vm/transfer/inbox and outbox/usr/bin/vm-downloadThere is no published npm package for this guest binary. It is delivered in the guest rootfs, not imported by the host UI.
wasm-vm-wasmThe wasm-bindgen boundary from crates/wasm, version 0.0.1. The demo imports WasmMachine and WasmLinux from the locally built module; a registry lookup does not find an npm release.
import init, { WasmMachine } from "./pkg/wasm_vm_wasm.js";
await init();
const machine = new WasmMachine(64);
machine.loadElf(elfBytes);
const result = machine.run(100_000);This import assumes your site has vendored pkg/wasm_vm_wasm.js and its sibling wasm_vm_wasm_bg.wasm, as described in the current embedding guide.
@wasm-vm/sdk appears in the planned E6-T19 package and E6-T27 docs work, but no npm package or install URL exists today. Treat snippets that name it as a proposal, not as a current dependency.These cards embed the hosted Orly player, which uses the published @brett_lamy/viz-engine / Docstream stack. The fallback copy stays visible and links directly to the same explainer if an iframe, network, or player package is unavailable.
How wasm-vm streams a disk, joins a tailnet, and freezes a machine.
Accessible fallback: five chapters cover touched blocks, the browser node, freezing and restoring, replay as a stream, and a readable cluster. Open Linux in a Tab directly ↗
Why a worker's claim becomes trustworthy only after a critic can replay and attack the evidence.
Accessible fallback: five chapters follow the claim, recorded run, critic attack, refutation/rework loop, and why replayable evidence beats a review summary. Open The wasm-vm Proof Loop directly ↗
For a React docs surface, the portable GitBook-style embed remains the integration point:
npm install @brett_lamy/viz-engine@0.2.1 @brett_lamy/docstream@0.3.7
import { GitbookStreamdown } from "@brett_lamy/docstream";
const markdown = `{% embed url="https://orly.brett-lamy.workers.dev/?bundle=wasm-vm-loop" /%}`;
<GitbookStreamdown markdown={markdown} />Source and media note: the bundle names, titles, and hosted URLs come from BLamy/orly at commit 7a00a5d; the repository is MIT-licensed. Its README/manifests describe generated MP3 narration, but the inspected metadata does not declare a per-file audio license or attribution. This sidecar therefore copies no MP3 and adds no standalone audio element; any narration remains inside the hosted player and its own controls.