Connect the Android companion to your own OpenClaw Gateway, then use the existing Rokid connection and HUD. Complete the backend connection on the phone before troubleshooting the glasses.
Before you start
ClawLensXR uses an Android phone as the bridge to compatible Rokid display glasses. This is connection setup for an existing backend, not instructions to run an AI agent on the phone. Audio-only glasses and other brands are not confirmed by this guide.
Have a trusted private TLS Gateway endpoint and permission to approve this phone as a device. The phone must reach the Gateway over wss:// with a valid certificate. A private Tailscale route can provide reachability; public exposure or Funnel is not required.
Connect on the phone
-
Open the OpenClaw/Server settings on the phone. Obtain a fresh QR or setup code from a trusted Gateway-owned surface; use Scan QR or Paste setup code where available. Keep the code out of chat and screenshots.
-
Review the displayed endpoint, then pair. In the Gateway Devices interface, review and approve the ClawLensXR request. A website login is not Gateway approval, and a Hermes API token cannot substitute for OpenClaw credentials.
-
Wait for the phone to show the connected state after approval. Then select the OpenClaw agent, session and supported model. Confirm the intended conversation before sending a small intentional text.
-
Connect compatible Rokid glasses through the existing Hi Rokid or Direct route and install/update the matching bundled HUD using the full guide. The phone remains the bridge; a glasses connection alone does not establish Gateway connectivity.
Check the first exchange
Check that the phone receives the reply and that the same session appears on the HUD. In supported versions, intentionally selected photos and transcribed voice can be used with the chosen provider; verify the actual server/model response rather than assuming every model accepts images.
Troubleshooting without losing work
-
Cannot connect: check the phone’s private route, host, port, certificate and Gateway availability. Do not disable certificate checks or publish the Gateway just to bypass a reachability error.
-
Approval pending or code expired: inspect the trusted Gateway device request and obtain a new code if needed. Do not paste credentials into support messages.
-
No visible answer: inspect the original run/session and any pending or unknown-work notice before retrying. Repeated Send, switching providers or clearing recovery data can duplicate or lose work; use the app’s explicit recovery controls.
Installation and compatibility
Check the installed phone version and the HUD version shown on the glasses. Use the matching bundled HUD and the existing Updates workflow; keep both devices awake during transfer. A model name or an APK build number alone does not establish firmware compatibility.
The Google Play phone installation, website membership/download access and glasses HUD installation are separate steps. The store listing does not establish Hermes availability in your installed version. Use the release notes for your actual channel; do not downgrade or clear app data to solve a connection problem. AI/model and voice-provider charges are separate.
For support, share app/HUD versions, selected provider, connection route and a redacted error. Never share tokens, setup codes, private hostnames, photos or conversation transcripts publicly.
Does this run OpenClaw on the glasses?
No. The phone connects to your existing Gateway and bridges the compatible glasses HUD.
Is a Hermes HTTPS URL interchangeable with the Gateway?
No. OpenClaw uses its own TLS WebSocket endpoint and device-approval flow. Follow the separate Hermes Agent guide for its HTTPS API connection.