Is v0.1.0 production-ready?

The core, providers, agents, gateway, CLI, Node bindings, and Telegram adapter are stable. We're calling it 0.1.0 (not 1.0.0) because the channel adapter set is incomplete and the WASM plugin runtime hasn't shipped — both visible roadmap items, not stability concerns.

What changes between 0.1 and 1.0?

Channel adapters (Discord, Slack, Signal, Matrix, WhatsApp), WASM plugin runtime, additional providers (Google Gemini, Ollama), measured benchmark numbers.

Announcing openclaw-rs v0.1.0

After months of building, openclaw-rs v0.1.0 is public.

What’s in the box

Stable today:

openclaw-core — types, JSON5 config, sled event store, AES-256-GCM credential store, input validation, OAuth.
openclaw-ipc — nng transport + JSON-RPC message types for the TypeScript plugin bridge.
openclaw-providers — Anthropic + OpenAI with SSE streaming and tool use.
openclaw-agents — runtime, sandbox backends for Linux/macOS/Windows, tool registry, workflow engine.
openclaw-gateway — axum HTTP + WebSocket + JSON-RPC 2.0 + embedded Vue 3 dashboard.
openclaw-cli — onboard, gateway, doctor, status, config, sessions, channels, daemon.
openclaw-node — napi-rs bindings with pre-built binaries for Linux x64/arm64, macOS x64/arm64, Windows x64.
openclaw-ui — Vue 3 dashboard embedded in the gateway.

Partial:

openclaw-channels — Telegram complete (full Bot API, attachments, allowlisting). Discord/Slack/Signal/Matrix/WhatsApp are roadmap items.
openclaw-plugins — TypeScript IPC bridge complete with 8 lifecycle hooks. WASM runtime (wasmtime vs wasmer) under evaluation.

How to try it

cargo install openclaw-cli
openclaw onboard
openclaw gateway run

The dashboard is at http://localhost:18789.

Compatibility with TypeScript OpenClaw

Same config: ~/.openclaw/openclaw.json (JSON5) — drop-in.
Same skills: Markdown + YAML — drop-in.
Same plugin contract: existing TypeScript plugins run unchanged via the nng IPC bridge.
Same event format on disk.

The migration story is its own piece: migrating from TypeScript OpenClaw to Rust.

What’s next

In rough order:

Channel adapters — Discord, Slack, Signal, Matrix, WhatsApp.
WASM plugin runtime — once we pick a backend.
Additional providers — Google Gemini, Ollama.
Benchmark numbers — we want measured figures before making performance claims with concrete numbers.
OpenTelemetry exporters — tracing is already wired; OTel is a small step.

Where to file issues

Bugs: GitHub Issues.
Questions: GitHub Discussions.
Security: see docs/SECURITY.md for the responsible disclosure address.

Thank you

This wouldn’t exist without the original OpenClaw project. The architecture is theirs. The Rust implementation is ours. We’re grateful for the design, the docs, and the community that made it sensible to build on.

— The Neul Labs team