Interactive Demo

See ClawFS In Action

Three problems every agent operator hits. Watch how a persistent shared volume solves each one — running real ClawFS logic compiled to WebAssembly in your browser.

Demo 1

Stop Paying the Cold Start Tax

Every time a worker spins up from scratch it re-downloads, re-installs, and re-compiles everything. Pick a project type to see how much time your agents are throwing away — and what ClawFS keeps warm.

Without ClawFS — cold start every run
With ClawFS — mount warm volume and go
What ClawFS persists across runs
Run the simulation to see what gets cached…

Demo 2

Stateful Reoccuring Agents

A security agent revisits the same customer site every week. It should remember old crawl state, prior findings, compliance notes, and exactly what changed between deploys. ClawFS turns that audit history into a mounted workspace instead of a pile of disconnected reports.

Audit workspace: vol-acme-redteam baseline only
Audit agent console
No scans yet
Persistent audit history in ClawFS
No scans stored yet…
What changed since the last audit
Run the baseline audit to build the first site snapshot and compliance notebook.

Demo 3

Shared Volumes as the Backbone of Multi-Agent Pipelines

Four specialized agents cooperate through a single ClawFS volume, using ionotify on the mount to react to filesystem changes. No message queues, no handoff APIs: one agent writes outputs, the next sees them in the shared workspace and keeps going.

Shared volume: vol-demo-pipeline gen 0 · 0 files
Inject log type:
nginx access
app errors
agent trace

📥 Ingest Agent

Watches /logs/ for new files, validates and timestamps each entry.

idle

🔍 Analysis Agent

Reads each log, detects error patterns, writes .analysis.json to /analysis/.

waiting for logs…

📊 Aggregator Agent

Reads all analysis files, computes stats, writes summary.json to /aggregates/.

waiting for analysis…

📈 Dashboard Agent

Reads the aggregate, renders an HTML insights report to /dashboard/.

waiting for aggregates…
Shared Volume — live file tree
Volume is empty. Inject a log file to start the pipeline…