Choose the Hermes provider on a version of ClawLensXR that includes Hermes settings. Connect to the supported HTTPS API supplied by your server administrator; dashboard access alone is not an API connection.
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.
Obtain the exact HTTPS API URL, including any profile path, and the matching Hermes API token. Do not infer an API port or path from a dashboard address. Features depend on the installed app, stock server API and model; this page does not certify a release/model matrix.
Connect on the phone
-
On the phone, open AI providers → Hermes. Enter a recognizable local connection name, the exact private HTTPS/profile URL and its Hermes API token. Do not use a wss:// Gateway address, OpenClaw token or Gateway QR pairing.
-
Choose Save connection, then Use connection, then Refresh status. Saving only records the configuration; selecting it and obtaining current status are separate actions. Resolve the displayed authentication or availability error before sending.
-
If you use a dashboard, sign in there separately to read its profiles. Explicitly link only the API connection you configured. Dashboard sign-in or a profile listing does not verify the serving API or grant Send access.
-
Select the intended profile/session on the phone and refresh available choices when required. Create new sessions on the phone in the documented workflow; the HUD browses existing sessions. Do not assume every deployment offers every model or control.
Check the first exchange
Start with an intentional short text and check the actual reply in the same session. Compatible app/server versions support text, selected photos and voice transcripts; Hermes remote audio is not supported. An earlier demo or development APK does not certify those features on your installation.
Troubleshooting without losing work
-
Authentication fails: verify the exact API/profile URL and its matching token with your administrator. A dashboard password, OpenClaw credential or another profile’s token is not interchangeable.
-
Catalog/profile unavailable: refresh status and the available choices in the phone UI. Do not invent a URL suffix, switch models/providers silently, or treat a saved connection as verified readiness.
-
Pending or unknown original work: inspect the original activity and recovery controls before retrying. Do not repeatedly Send or clear local data to remove a warning; lack of a visible reply is not proof the server did nothing.
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.
Can Hermes use photos?
The documented compatible versions support selected photos and transcripts, not remote audio. Actual success depends on your app/server/model; the Play listing alone does not verify that combination.
Do I need to patch my Hermes server?
This guide does not require custom server patches. Use the supported stock API contract and report an incompatible deployment instead of changing server code to follow these steps.