This is an early release preview. You may encounter bugs.
OpenClaw logo
Unclaimed

Harness connectors

OpenClaw

Self-hosted single-operator assistant runtime that links models, tools, and messaging channels through one local Gateway

A 89/100 GitHub score ? This grade is derived from GitHub signals, not user votes. Open for the full breakdown.
100% recommend · 1 rater

01 / About

What OpenClaw is.

OpenClaw is an AI assistant runtime that runs on your own devices and reaches you through the messaging channels you already use. It connects models, tools, channels, and optional companion apps through a single Gateway, and the same gateway serves either one operator or a team whose members trust each other — configuration is the only difference between the two.

The Gateway is the local control plane for sessions, tools, events, and channel connections. A Control UI, a CLI, and a terminal UI all connect to it. Channels bring the assistant to WhatsApp, Telegram, Slack, Discord, Google Chat, Signal, iMessage, and other services, while companion apps and device nodes add voice, Canvas, camera, screen, and device-local actions on supported platforms. It works with hosted and local model providers, and tools, skills, and plugins extend what an assistant can do, with plugins built on a plugin SDK and shared through ClawHub.

Installation uses a script for macOS, Linux, and Windows that provisions a supported Node.js runtime, or the published npm package on Node 22.22.3+, 24.15+, or 25.9+; desktop apps are available for macOS, Windows, and Linux. Onboarding verifies model access, creates the workspace, and configures the Gateway, after which openclaw gateway status and openclaw dashboard confirm the assistant is running. Stable and dev release channels can be switched from the CLI.

The security model treats inbound messages as untrusted input. Channels that accept direct messages pair unknown senders by default, and a pairing request is approved from the CLI. Tools run on the host for the main session unless you configure sandboxing, and the documentation covers a security guide, an exposure runbook, and sandboxing before the Gateway is opened to other users or reached remotely.

Features

  • One Gateway: a local control plane for sessions, tools, events, and channel connections
  • Multiple front ends: Control UI, CLI, and terminal UI, plus desktop apps for macOS, Windows, and Linux
  • Messaging channels: WhatsApp, Telegram, Slack, Discord, Google Chat, Signal, iMessage, and more
  • Companion apps and nodes: voice, Canvas, camera, screen, and device-local actions on supported platforms
  • Model choice: hosted or local model providers, configured during onboarding
  • Extensions: tools, skills, and plugins built on a plugin SDK and distributed through ClawHub
  • Team mode: the same gateway runs as a personal assistant or a shared team deployment, by configuration
  • Pairing and sandboxing: unknown senders are paired by approval, and tool execution can be sandboxed away from the host

02 / Discussion CREDIBILITY-GATED

Discussion

Reading is open to everyone. Posting and voting need a verified identity or a GitHub grade of B or higher.

04 / Build

Build with OpenClaw.

Browse the catalogue for frameworks, tools, and harnesses, each scored on real GitHub credibility.

Get OpenClaw →

Browse the catalogue