Why is openclaw devices list failing?

A regression in v2026.3.12 breaks the WebSocket handshake for CLI device commands against localhost gateway.

How to fix openclaw devices approve error?

Downgrade to v2026.3.8 or wait for the patch. The issue is a CLI-specific WebSocket closure timing bug.

Is openclaw devices command broken?

Yes, in v2026.3.12. The CLI returns 'gateway closed' while the web dashboard continues working.

What broke in OpenClaw v2026.3.12?

WebSocket connections close prematurely against local loopback gateways after 10 seconds.

Can I still pair devices in OpenClaw 3.12?

Yes, through the web UI. The CLI commands are broken but pairing works through the browser.

← Back to dashboard

clawsmith.com/signal/openclaw-v2026-3-12-device-cli-loopback-regression

⚠ IssueUnknownLive

OpenClaw v2026.3.12 Breaks Device CLI Commands Against Local Loopback Gateway

After upgrading to v2026.3.12, openclaw devices list and devices approve fail with WebSocket closure errors against localhost gateway while web UI works.

Product Idea from this Signal

A CLI tool that dry-runs OpenClaw upgrades against your config and skills before applying them

97 ▲

Every OpenClaw release breaks something different. pnpm users lose dependencies, npm users get broken CLI, permissions decouple after updates, CPU spikes from plugin registration, and device management commands fail. Users have no way to test if an upgrade will break their specific setup. This tool snapshots your current config, installed skills, environment, and package manager, spins up the target version in an isolated environment, runs your workflows against it, and reports exactly what will break before you commit to the upgrade.

developer-toolsupgrade-testingregression-preventionclicompatibility

CompetitiveView Opportunity →