openclaw
Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞
OpenClaw: your assistant, wherever you already chat
OpenClaw is a personal AI assistant that runs on your own devices and shows up in the channels you already use, routing through a Gateway. The README covers install, setup, security, and development.
What it is
OpenClaw is a personal AI assistant built for a single operator. It runs on your devices and meets you in the messaging channels you already use. A Gateway ties together models, tools, messaging channels, and optional companion apps. The project came out of work on Molty, a space lobster assistant, by Peter Steinberger and the community, and it is developed by the OpenClaw Foundation, a non-profit.
Install and first run
The installer supports macOS, Linux, and Windows and provisions a supported Node.js runtime when needed. People who already manage Node can install the published package instead; the README lists version requirements. Onboarding verifies model access, creates the workspace, and configures the Gateway. The final command opens the Control UI, where sending a message confirms everything works.
Channels and companions
Channels bring the assistant to WhatsApp, Telegram, Slack, Discord, Google Chat, Signal, iMessage, and other messaging services. Companion apps and nodes add voice, Canvas, camera, screen, and device-local actions on supported platforms. The assistant works with hosted and local model providers, and tools, skills, and plugins extend what it can do. The Gateway is the local control plane for sessions, tools, events, and channel connections.
Security stance
The README treats inbound messages as untrusted input. DM-capable channels pair unknown senders by default, and an operator approves the pairing request. Tools run on the host for the main session unless sandboxing is configured. Before connecting other users or exposing the Gateway remotely, the README points to the security guide, exposure runbook, and sandboxing guide.
Development and community
The repository is a pnpm workspace, and a plain npm install at the root is not supported. New capabilities usually belong in plugins built on the plugin SDK and shared through ClawHub. Bugs and feature requests go through the issue chooser, setup questions land on Discord, and vulnerabilities are handled through SECURITY.md. AI-assisted pull requests are welcome.
Editorial conclusion
The README is careful about scope: one operator, your devices, your channels. It also tells you to treat inbound messages as untrusted input. That kind of caution is rare in assistant projects.
Community notes