Q: Can my TypeScript plugins keep working?

Yes. openclaw-plugins runs each TypeScript plugin in its own process and communicates over nng (an embedded message-passing transport) using JSON-RPC. Eight lifecycle hooks are exposed: BeforeMessage, AfterMessage, BeforeToolCall, AfterToolCall, SessionStart, SessionEnd, AgentResponse, and Error.

Q: Is it production-ready?

The core, providers, agents, gateway, CLI, Node bindings, and Telegram adapter are stable today (v0.1.0). openclaw-channels is at ~50% (Discord, Slack, Signal, Matrix, WhatsApp are roadmap items). openclaw-plugins ships the TS bridge today; the WASM runtime is under evaluation.

Q: Is there a paid version?

No. openclaw-rs is MIT-licensed and free. Neul Labs offers separate commercial support and integration services on top of it, but the framework itself is fully open source.

Q: What platforms does it run on?

Linux, macOS, and Windows. Pre-built binaries are published on crates.io (Rust CLI) and npm (Node bindings) for Linux x64/arm64, macOS x64/arm64, and Windows x64. Rust 1.85+ (2024 edition) is required to build from source.

Q: How does the sandbox actually work?

openclaw-agents picks a backend per OS: bubblewrap on Linux (with namespace isolation for net + pid + mount), sandbox-exec on macOS (with a declarative Seatbelt profile), and Windows Job Objects (with CPU + memory + UI-access limits). The same SandboxConfig — None, Relaxed, or Strict — selects the policy regardless of OS.

Q: Which LLM providers are supported today?

Anthropic Claude (3.5 Sonnet, Haiku, Opus) and OpenAI GPT (4o, 4, 3.5) ship today with SSE streaming, tool use, and custom base URLs. Google Gemini and Ollama are on the roadmap and will reuse the same Provider trait.

Q: Are Telegram-only channels the plan?

No — Telegram is just first. The Channel / ChannelInbound / ChannelOutbound traits, allowlist, and routing layer are in place. Discord, Slack, Signal, Matrix, and WhatsApp adapters are tracked in docs/ROADMAP.md and follow the same pattern: PRs welcome.

Q: How is the Vue 3 dashboard deployed?

It isn't deployed separately. openclaw-ui builds with Vite into a static bundle that openclaw-gateway embeds and serves at /. You run one binary, you get a dashboard.

Question 1

What is openclaw-rs?

Accepted Answer

openclaw-rs is a Rust implementation of OpenClaw, an open-source AI agent framework. It is event-sourced, sandboxed, and single-binary. The same workspace ships a JSON-RPC 2.0 gateway (axum, HTTP + WebSocket), an agent runtime with platform-specific sandboxes, Anthropic + OpenAI provider clients, a Telegram channel adapter, an AES-256-GCM credential store, a Vue 3 dashboard, and napi-rs bindings for Node.js.

Question 2

How is this different from TypeScript OpenClaw?

Accepted Answer

Same configuration format, same skill format, same plugin contract — but the runtime is a Rust binary instead of a Node.js process. You get memory safety, sub-millisecond message routing, a < 15 MB single-binary target, and no Node runtime to ship. Existing TypeScript plugins keep working via an nng IPC bridge.

Question 3

Can my TypeScript plugins keep working?

Accepted Answer

Yes. openclaw-plugins runs each TypeScript plugin in its own process and communicates over nng (an embedded message-passing transport) using JSON-RPC. Eight lifecycle hooks are exposed: BeforeMessage, AfterMessage, BeforeToolCall, AfterToolCall, SessionStart, SessionEnd, AgentResponse, and Error.

Question 4

Is it production-ready?

Accepted Answer

The core, providers, agents, gateway, CLI, Node bindings, and Telegram adapter are stable today (v0.1.0). openclaw-channels is at ~50% (Discord, Slack, Signal, Matrix, WhatsApp are roadmap items). openclaw-plugins ships the TS bridge today; the WASM runtime is under evaluation.

Question 5

Is there a paid version?

Accepted Answer

No. openclaw-rs is MIT-licensed and free. Neul Labs offers separate commercial support and integration services on top of it, but the framework itself is fully open source.

Question 6

What platforms does it run on?

Accepted Answer

Linux, macOS, and Windows. Pre-built binaries are published on crates.io (Rust CLI) and npm (Node bindings) for Linux x64/arm64, macOS x64/arm64, and Windows x64. Rust 1.85+ (2024 edition) is required to build from source.

Question 7

How does the sandbox actually work?

Accepted Answer

openclaw-agents picks a backend per OS: bubblewrap on Linux (with namespace isolation for net + pid + mount), sandbox-exec on macOS (with a declarative Seatbelt profile), and Windows Job Objects (with CPU + memory + UI-access limits). The same SandboxConfig — None, Relaxed, or Strict — selects the policy regardless of OS.

Question 8

Which LLM providers are supported today?

Accepted Answer

Anthropic Claude (3.5 Sonnet, Haiku, Opus) and OpenAI GPT (4o, 4, 3.5) ship today with SSE streaming, tool use, and custom base URLs. Google Gemini and Ollama are on the roadmap and will reuse the same Provider trait.

Question 9

Are Telegram-only channels the plan?

Accepted Answer

No — Telegram is just first. The Channel / ChannelInbound / ChannelOutbound traits, allowlist, and routing layer are in place. Discord, Slack, Signal, Matrix, and WhatsApp adapters are tracked in docs/ROADMAP.md and follow the same pattern: PRs welcome.

Question 10

How is the Vue 3 dashboard deployed?

Accepted Answer

It isn't deployed separately. openclaw-ui builds with Vite into a static bundle that openclaw-gateway embeds and serves at /. You run one binary, you get a dashboard.

Question 11

When does the WASM plugin runtime ship?

Accepted Answer

TBD — see docs/ROADMAP.md. The TypeScript IPC bridge is production-ready today, so most plugin work doesn't need to wait. The open question is wasmtime vs wasmer for the WASM backend; the API will be stable once that choice lands.

Question 12

Is there OpenTelemetry / observability support?

Accepted Answer

openclaw-rs uses tracing with structured fields throughout, so any tracing-compatible subscriber (including OpenTelemetry exporters) works today. First-class OTel exporters and a dashboards bundle are on the roadmap.

Frequently asked.

Open an issue or a discussion.