Description

Description

After deploying NemoClaw via Brev Launchable and clicking CHAT WITH AGENT , the OpenClaw Web UI displays pairing required in red. There is no way to complete
device pairing from the browser — Brev Launchable users only have web access, not terminal access to run openclaw devices list and approve the request.

Environment Device: Brev Launchable (Cloud VM)
OS: Ubuntu (Brev-provisioned)
Architecture: x86_64
Instance type: CPU · 4 CPUs · 16 GiB RAM
Cloud Provider: GCP
Storage: 256 GiB
NemoClaw: latest (Brev Launchable default)
URL: nemoclaw0-rdymxxi8.brevlab.com/chat?session=main

Reproduction Steps

1. Deploy NemoClaw via Brev Launchable (brev.nvidia.com)
2. Wait for AGENT CREATED SUCCESSFULLY
3. Click CHAT WITH AGENT
4. Observe pairing required in red badge and pairing required message in chat

Actual Result

 Web UI should be ready to chat without pairing — Brev Launchable deployment should auto-approve device pairing, or dangerouslyDisableDeviceAuth should be set for Launchable deployments.

Expected Result

• Red badge: pairing required
• Chat: Disconnected from gateway. + pairing required
• No way to complete pairing from browser (no terminal access in Launchable flow)

Impact:
​​​​​​​Blocks all Brev Launchable users from using the chat UI after deployment. The entire Launchable 1-click deploy experience is broken at the last step.

Bug Details

[NVB#6107301]