Zeroclaw Plugins

ZeroClaw Plugin Registry

The official catalog of [ZeroClaw](https://github.com/zeroclaw-labs/zeroclaw) WASM plugins — **self-contained WIT components** the agent can fetch and install on demand. This is what `zeroclaw plugin search` and `zeroclaw plugin install ` read by default.

zeroclaw plugin search redact
zeroclaw plugin install redact-text
zeroclaw plugin install redact-text@0.1.0    # pin a version

What's in this repo

plugins//        # published plugins — one wit-bindgen component per directory
  Cargo.toml           # cdylib + rlib, wit-bindgen, standalone [workspace]
  src/lib.rs           # thin #[cfg(target_family = "wasm")] component shim
  src/.rs        # pure logic, no wasm deps — host-testable
  tests/               # host-run tests over the pure core (`cargo test`)
  manifest.toml        # name, version, wasm_path, capabilities, permissions
  README.md
wit/v0/                # vendored ZeroClaw plugin WIT contract (the ABI plugins build against)
registry.json          # GENERATED index — published by CI, do not hand-edit
tools/build-registry.py
.github/workflows/publish.yml

Plugins are **WebAssembly components** built for `wasm32-wasip2` against the WIT world `tool-plugin` (`wit/v0/`). They run sandboxed and deny-by-default: the host grants only the capabilities a plugin's `manifest.toml` declares.

`wit/v0/` is vendored **unmodified** from [zeroclaw `wit/v0`](https://github.com/zeroclaw-labs/zeroclaw/tree/master/wit/v0) — it is the contract the host actually implements. Plugins requiring host capabilities beyond it (e.g. HTTP egress) are blocked on the upstream host capability interface ([zeroclaw#8135](https://github.com/zeroclaw-labs/zeroclaw/issues/8135)).

How install works

• `registry.json` is a single index, fetched from https://raw.githubusercontent.com/zeroclaw-labs/zeroclaw-plugins/main/registry.json.
• Each entry's url points to a zipped plugin directory publishe