wado / wado-run-webgpu
AGENTS.md120 starsChanged 14 days agoMITView on GitHub
The wado run-webgpu subcommand: it compiles a Wado program with wado and runs the component on a wasmtime host that serves wasi:webgpu. - This crate is a workspace of its own and is excluded from the repository's, so that nothing at the repository root builds wgpu. Nothing here is built by cargo build at the repository root, mise run test, or the repository's clippy and fmt jobs. The test-webgpu CI job is what builds, lints and tests it, on every…
In this repository37 other files it gives its agents.
- AGENTS.mdAGENTS.md
- benchmark/AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- package-gale/AGENTS.mdAGENTS.md
- package-grog/AGENTS.mdAGENTS.md
- package-jade/AGENTS.mdAGENTS.md
- package-loam/AGENTS.mdAGENTS.md
- package-re/AGENTS.mdAGENTS.md
- package-wadopoet/AGENTS.mdAGENTS.md
- wado-cli/AGENTS.mdAGENTS.md
- wado-compiler/AGENTS.mdAGENTS.md
- wado-from-idl/AGENTS.mdAGENTS.md
- wado-host/AGENTS.mdAGENTS.md
- wado-lsp/AGENTS.mdAGENTS.md
- wado-manifest/AGENTS.mdAGENTS.md
- wado-run-pjrt/AGENTS.mdAGENTS.md
- wado-vscode/AGENTS.mdAGENTS.md
- benchmarkSkill
- ci-timingSkill
- code-review-responseSkill
- coverage-investigationSkill
- crSkill
- debuggerSkill
- distillSkill
- git-upstream-syncSkill
- jcoSkill
- markdownSkill
- on-task-doneSkill
- optimizer-debugSkill
- profiling-wado-compilerSkill
- pull-requestSkill
- rust-renameSkill
- rustSkill
- vendor-submodulesSkill
- wado-cliSkill
- wado-performanceSkill
- wasm-optSkill
The file
Files
wado-run-webgpu
The wado run-webgpu subcommand: it compiles a Wado program with wado and
runs the component on a wasmtime host that serves wasi:webgpu.
Rules
- This crate is a workspace of its own and is excluded from the repository's,
so that nothing at the repository root builds wgpu. Nothing here is built by
cargo buildat the repository root,mise run test, or the repository's clippy and fmt jobs. Thetest-webgpuCI job is what builds, lints and tests it, on every change that is not documentation. wasi-webgpu-wasmtimemust build on the wasmtime the repository pins, since this crate shareswado-host'srunner.- A program behaves the same here as under
wado run, which is the only reason to have both.wado_host::runner,guestandoptionshold what makes that so, and a divergence is a defect, not a variant. - The tests set
WADOaswadodoes (External Subcommands), so the tests and a real invocation reach the compiler through one path. - Running needs a GPU adapter. wgpu finds none without a driver, and the host
says so and exits rather than letting the guest see
request-adapteranswernone. On Linuxmesa-vulkan-driverssupplies the lavapipe software adapter, which is what CI installs; macOS answers with Metal and Windows with D3D12. - Dependencies live in this crate's own
Cargo.toml, there being no workspace above it to hold them. The other Rust rules apply as written.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

