The peer-to-peer agentic OS.

Agentic frameworks give you a platform for running agents. Wetware gives your agents an operating system. It provides primitives (processes, networking, storage, identity) and gets out of the way. Processes are network-addressable, capability-secured, and peer-to-peer by default.

Where agentic frameworks rely on ambient authority — any code can call any API, read any secret, spend any resource — Wetware replaces this with capabilities. A process can only do what it's been handed a capability to do.

rustup target add wasm32-wasip2   # one-time setup
make                              # build host + kernel + shell
cargo run -- run crates/kernel    # drops into a Glia shell

/ ❯ (host id)
"12D3KooWAbcDef..."

/ ❯ (host peers)
[{:peer-id "..." :addrs [...]} ...]

/ ❯ (ipfs cat "/ipfs/QmFoo...")
"hello world"

/ ❯ (routing find "my-service")
[{:peer-id "..." :addrs [...]} ...]

/ ❯ (exit)

ww run boots an agent:

1. Starts a libp2p swarm on the configured port
2. Loads bin/main.wasm from the merged image
3. Spawns the agent with a Membrane — the capability hub that grants access to host, network, IPFS, and identity services via Cap'n Proto RPC

Agents call membrane.graft() to receive epoch-scoped capabilities. When the on-chain epoch advances (new code deployed, configuration changed), all capabilities are revoked and the agent must re-graft, picking up the new state automatically.

Glia is a Clojure-inspired language where capabilities are first-class values. The design blends three traditions:

• E-lang: capabilities as values you can pass, compose, and attenuate
• Clojure: s-expression syntax, immutable data, functional composition
• Unix: processes, PATH lookup, stdin/stdout, init.d scripts

make                           # build everything (host + std + examples)
make host                      # host binary only
make kernel                    # kernel agent only
cargo test                     # run tests

Requires Rust with wasm32-wasip2 target. Optional: Kubo for IPFS resolution.

make container-build                          # build with podman (default)
CONTAINER_ENGINE=docker make container-build  # or with docker
podman run --rm wetware:latest                # boots kernel + shell
podman run --rm wetware:latest --help         # CLI help

The image ships kernel and shell WASM blobs, so podman run wetware:latest works out of the box. Pass additional layers as arguments to stack on top of the default kernel.

Read PROMPT.md and give me a guided tour of Wetware.

Or without cloning:

Read https://raw.githubusercontent.com/wetware/ww/master/PROMPT.md and give me a guided tour of Wetware.

Claude Code · Cursor · Windsurf · PROMPT.md

• Architecture — design principles and capability flow
• Capabilities — the capability model and Cap'n Proto schemas
• Image layout — FHS convention, mounts, and on-chain coordination
• CLI reference — full command-line usage
• Shell — Glia shell details
• Platform vision — roadmap and design