Paired device capabilities

OpenClaw Nodes

Orient around paired iOS, Android, browser, and desktop nodes that expose camera, canvas, voice, screen, and device actions to the Gateway.

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

Pairing first

A node should not be treated as trusted just because it can reach the Gateway. Approve pairing and scopes deliberately.

Read next

Media and context

Camera, image, audio, and screen surfaces can expand context quickly. Validate provider support and cost before enabling broad use.

Read next

Remote browser node

Browser control is a node-like operational surface with its own host, timeout, and network failure modes.

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.

Mobile access landscape

Community map of phone-first OpenClaw access patterns.

Open

Mobile release analysis

What the mobile release changes for operators.

Open

Browser automation timeouts

Failure isolation for browser-control workflows.

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.

Platforms Start here when the question is macOS app, Windows, Linux, VPS, Raspberry Pi, iOS, Android, or cloud hosting. 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.