Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

gateway-control-ui

v1.0.0

Step-by-step guide to log into the OpenClaw Control UI, enter gateway token, approve device pairing, and verify connection

0· 321· 1 versions· 0 current· 0 all-time· Updated 9h ago· MIT-0

Install

openclaw skills install gateway-control-ui

Gateway Control UI Login & Pairing

Use when a user needs to access the OpenClaw Gateway Control UI, authenticate, pair a device, and confirm connectivity.

Prerequisites

  • OpenClaw gateway running (openclaw status)
  • Control UI URL configured in gateway.controlUi.allowedOrigins
  • Gateway token available in config (/data/.openclaw/openclaw.json)
  • Device pairing approval (CLI)

Steps

1. Open Control UI

  • URL: use your configured OpenClaw service URL (from gateway.controlUi.allowedOrigins)
  • HTTP Basic Auth:
    • Username: use your SERVICE_USER_OPENCLAW value
    • Password: use your SERVICE_PASSWORD_OPENCLAW value
  • Optional embedded form:
    • https://<user>:<pass>@<your-openclaw-domain>/

2. Get Gateway Token

cat /data/.openclaw/openclaw.json | grep -A 2 '"token"'

Token is under:

"gateway": { "auth": { "token": "YOUR_TOKEN_HERE" } }

3. Enter Token in UI

  • On Overview page, click Gateway Token field
  • Paste token
  • Click Connect

4. Approve Pairing (CLI)

openclaw devices list
openclaw devices approve <requestId>

5. Verify Success

  • In Control UI: status shows green “OK” and dashboard loads
  • CLI:
    openclaw status --deep
    
    Check Gatewayreachable and channels show OK.

Troubleshooting

  • Page stays on form? WebSocket URL may need to be filled (usually left blank for remote)
  • Pairing fails? Run openclaw devices list again to see pending requests
  • Token invalid? Check /data/.openclaw/openclaw.json for correct value

Version tags

latestvk976haq4n9y5sbrzxkemcpk7fd82qx7c

Runtime requirements

🔧 Clawdis
Binsopenclaw, cat