← Back to all projects

openclaw

A single-operator assistant that runs as a local Gateway and reaches you in the chat apps you use.

OfficialMIT
Stars
393k
Forks
82.7k
Open issues
7.9k
Last commit
30 Oct 2026

What is openclaw?

OpenClaw installs a Gateway on your own machine and makes it the local control plane for sessions, tools, events and channel connections, so the Control UI, CLI, TUI and every connected messaging channel drive the same assistant. Models can be hosted or local, and the project expects new capabilities to arrive as plugins built on the plugin SDK rather than as changes to the core. The constraints are stated plainly in the README: it is designed for a single operator, tools run on the host for the main session unless you configure sandboxing, and DM-capable channels leave the assistant reachable by unknown senders until you approve a pairing with `openclaw pairing approve <channel> <code>`. The README tells you to read the security, exposure and sandboxing guides before connecting other users or exposing the Gateway remotely, which is a fair signal that shared or multi-user deployment is not the case it was built for.

What can you do with openclaw?

  • Talk to it from the chat apps you already use — Channels connect WhatsApp, Telegram, Slack, Discord, Google Chat, Signal and iMessage to the same Gateway. Inbound messages are treated as untrusted input, and unknown senders on DM-capable channels stay unpaired until you run openclaw pairing approve <channel> <code>.
  • Go from install to a working assistant in three commands — curl -fsSL https://openclaw.ai/install.sh | bash (or iwr -useb https://openclaw.ai/install.ps1 | iex on Windows PowerShell) provisions a Node runtime when needed; then openclaw onboard --install-daemon verifies model access and creates the workspace, and openclaw dashboard opens the Control UI. Installing via npm install -g openclaw@latest instead requires Node 22.22.3+, 24.15+ or 25.9+.
  • Drive the same session from terminal or browser — The Control UI, CLI and TUI are all clients of the Gateway, and openclaw gateway status reports whether the local Gateway is running.
  • Extend it without forking the core — Tools, skills and plugins are the extension points; the README states that new capabilities usually belong in plugins built on the plugin SDK and shared through ClawHub rather than merged into the main repository.
  • Attach device hardware through companion apps and nodes — Companion apps and device nodes connect to the Gateway to add voice, Canvas, camera, screen and device-local actions, but only on supported platforms — the per-platform setup is documented separately under docs.openclaw.ai/platforms and docs.openclaw.ai/nodes, not in the core install flow.

Before you choose openclaw

  • Incoming messages are guarded carefully, outgoing ones less so. Text the assistant produces while working, such as error handling and notes on what it is doing, has been reported arriving in Slack as visible messages.Reported in#25592

Star history

16 Aug to 30 Oct · +7k

386k393k

Frequently asked questions

Is openclaw free for commercial use?

openclaw is released under the MIT licence — OSI-approved open source, which permits commercial use.

How can openclaw be deployed?

openclaw is available as Self-hosted / Runs locally.