ACT packages tools as WebAssembly components. One .wasm file runs on every OS and CPU, served over MCP, HTTP, CLI, or in the browser — inside an explicit capability sandbox. Built for agent tooling where distribution and isolation both matter.
Every useful developer tool today ships with a matrix — package manager, OS, CPU; hope the native bits line up; run with your full user permissions. For AI agents that breaks twice: you need the same tool as both MCP server and HTTP backend, and you'd rather not hand ambient filesystem access to code a stranger wrote.
ACT collapses both. Write a tool once, as a WebAssembly component. Ship it as one signed artifact in an OCI registry. Run it under wasmtime on any target, served over any transport, inside a declarative capability sandbox. Open protocol, small spec, SDK on a postcard.
Our stack
WebAssembly (WASI)
Rust
0 posts published
1 member
loading...
We're a place where coders share, stay up-to-date and grow their careers.