OpenClaw Mobile and Remote Nodes Guide

A node extends a Gateway with capabilities on another device. Depending on the platform, that can include camera, location, media, voice, Canvas, browser access, or computer-use actions.

Prepare a secure route

The node must reach the correct Gateway over an approved local or private-network path. Remote mobile pairing should use wss://. Keep the Gateway authenticated and treat a setup QR or copied pairing code as a temporary secret.

Review current state on the Gateway:

openclaw nodes --help
openclaw devices list
openclaw status --all

Pair and approve deliberately

Create the pairing handoff from an administrator session, connect the intended device, and inspect the requested role and scopes before approval. A phone, browser profile, and node host can represent different device identities.

Grant operating-system permissions individually. Camera, microphone, screen recording, accessibility, and location are not harmless convenience toggles; leave every unused capability disabled.

Test one capability

Use a benign request such as a presence check or a test Canvas operation. Confirm which device handled it and where any captured media was stored or sent. Do not begin with camera, location, or computer control.

For remote browser routing, restrict the node browser proxy to only the profiles that the Gateway should target.

Expected result

• The intended node appears online once.
• Its role, scopes, and device name are clear.
• Only approved platform permissions are available.
• One harmless node command completes on the expected device.
• Revoking the device removes access.

Use Pairing failed if the request never appears or repeatedly changes identity.