docs: correct WASM extension wording (WOR-145)#71
Merged
rickcrawford merged 2 commits intomainfrom May 6, 2026
Merged
Conversation
CLAUDE.md described the WASM surface as "WASM stub" but the production crate ships a real wasmtime + WASI preview-1 runtime: 568 lines in crates/sbproxy-extension/src/wasm/mod.rs with sandboxed memory caps, epoch-interrupt CPU timeouts, stderr capture, no FS, no network. End- to-end coverage exists in e2e/tests/wasm.rs and examples/wasm/. Drop "stub" from CLAUDE.md and tighten the language to match reality. llms.txt claimed "WASI networking with host allowlist" but the code parses allowed_hosts as a forward-compat reservation only; sockets are not exposed today (mod.rs:23, mod.rs:113-114). Rewrite the bullet to describe the actual stdin/stdout body-transform surface. Closes WOR-145. https://claude.ai/code/session_019zc6oCY6Kx2ssiuZEQdznk
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes WOR-145. The audit ticket asked whether the WASM surface is the "stub" described in CLAUDE.md or the production-ready engine described in marketing docs. After auditing the code, the engine is real and CLAUDE.md /
llms.txtare wrong.What's actually in
crates/sbproxy-extension/src/wasm/mod.rs(568 lines):wasmtime+wasi-commonwith WASI preview-1 ABImax_memory_pages(default 256 = 16 MiB), CPU cap via epoch-interruption (default 1000 ms), stderr capture with 1 MiB per-call cap routed totracing::debug!WasmRuntime::new/is_available/execute,WasmConfig,build_request_input_with_agent_class,build_enginee2e/tests/wasm.rsround-trips body through the echo moduleexamples/wasm/echo-rust/,examples/wasm/uppercase-tinygo/,examples/38-wasm-transform/docs/wasm-development.mdanddocs/scripting.md(already accurate, no changes needed)Corrections in this PR:
CLAUDE.mdline 58 — drop "WASM stub" wording, name the actual stack (wasmtime + WASI preview-1).llms.txtline 214 — replace the misleading "WASI networking with host allowlist" claim.allowed_hostsis parsed as a forward-compat reservation but sockets are not exposed (mod.rs:23, mod.rs:113-114). The bullet now describes the real stdin/stdout body-transform surface.Test plan
e2e/tests/wasm.rsalready exercises the production WASM path end-to-end (echo module viastaticorigin +wasmtransform).Out of scope (follow-ups, not filed yet)
allowed_hostsenforcement: if/when networking lands,llms.txtshould be updated again. Theallowed_hostsfield already parses to keep the config schema stable.docs/scripting.mdis already explicit about this scope.https://claude.ai/code/session_019zc6oCY6Kx2ssiuZEQdznk
Generated by Claude Code