Host and companion surfaces

OpenClaw Platforms

Choose where the Gateway runs, which companion app joins it, and which CoClaw setup path matches the operator environment.

CoClaw is community-run and independent from the official OpenClaw project. Use official OpenClaw docs for canonical command, schema, and release details.

Official docs All CoClaw hubs

Local workstation

macOS, Linux, and Windows are best when the operator wants direct control of files, credentials, and desktop automation.

Read next

Always-on server

VPS, cloud, and Raspberry Pi setups fit chat-first assistants that need to keep the Gateway reachable all day.

Read next

Companion apps

Mobile and desktop companion apps are node surfaces. Treat pairing, network discovery, and permissions as part of the platform choice.

Read next

CoClaw reading path

Community pages are intentionally narrower than upstream docs. Use them to choose a path, then return to official references for exact commands and schema fields.

Install paths

CoClaw entry point for macOS, Linux, Windows, Docker, VPS, and cloud installs.

Open

Deployment form factors

How local, LAN, remote, and hosted patterns differ operationally.

Open

Raspberry Pi guide

Community guidance for low-power always-on hosts.

Open

Other current OpenClaw surfaces

These CoClaw hubs are first-pass orientation pages, not exhaustive docs.

CoClaw treats OpenClaw v2026.6.1, published June 3, 2026, as the latest stable baseline for this first-pass map. Main branch and beta builds can move faster and should not be presented as stable.

Nodes Use this hub when a workflow depends on a paired device, node permissions, Canvas, media capture, or remote browser control. Tools Use this hub when OpenClaw can chat but cannot act, or when an operator is deciding which actions should be available. Plugins Use this hub when a capability lives outside the core Gateway or when an operator is evaluating ClawHub packages. Providers Use this hub when the hard problem is not the channel, but the model/provider path behind the agent. Automation Use this hub when OpenClaw is expected to initiate or continue work outside a single live chat reply.