openclaw - 💡(How to fix) Fix [Bug]: All CLI commands (except --version) hang indefinitely [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#68642Fetched 2026-04-19 15:09:10
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Author
Participants
Timeline (top)
labeled ×2commented ×1

All openclaw CLI commands (except --version) hang indefinitely after initiating a WebSocket connection to the Gateway.

Error Message

CLI commands complete normally with output, or show a proper error message.

Root Cause

Commands hang indefinitely with no output. No connection is ever established. Only openclaw --version works, because it does not connect to the Gateway via WebSocket RPC.

Code Example

No logs produced — command hangs before any output. Verified with strace: process blocks on socket read during device auth handshake.
RAW_BUFFERClick to expand / collapse

Bug type

Crash (process/app exits or hangs)

Beta release blocker

No

Summary

All openclaw CLI commands (except --version) hang indefinitely after initiating a WebSocket connection to the Gateway.

Steps to reproduce

  1. Run any openclaw CLI command other than --version (e.g., openclaw status, openclaw gateway status, openclaw doctor)
  2. Command hangs forever with no output
  3. Press Ctrl+C to terminate

Expected behavior

CLI commands complete normally with output, or show a proper error message.

Actual behavior

Commands hang indefinitely with no output. No connection is ever established. Only openclaw --version works, because it does not connect to the Gateway via WebSocket RPC.

OpenClaw version

2026.4.15

Operating system

Ubuntu (unknown version — user can provide on request)

Install method

npm

Model

minimax

Provider / routing chain

N/A

Additional provider/model setup details

No response

Logs, screenshots, and evidence

No logs produced — command hangs before any output. Verified with strace: process blocks on socket read during device auth handshake.

Impact and severity

No response

Additional information

Root cause: The Gateway uses WebSocket RPC with device auth v2. The CLI does not implement the device auth v2 handshake response (connect.challenge nonce). Control UI works because it implements the full handshake. Only --version works because it bypasses Gateway connection entirely.

extent analysis

TL;DR

Implement the device auth v2 handshake response in the openclaw CLI to fix the indefinite hang issue.

Guidance

  • The root cause is the missing implementation of the device auth v2 handshake response (connect.challenge nonce) in the openclaw CLI.
  • To verify the issue, run the command with strace to confirm that the process blocks on socket read during device auth handshake.
  • Implementing the device auth v2 handshake response in the openclaw CLI should resolve the issue, allowing CLI commands to complete normally with output.
  • As a temporary workaround, consider using the Control UI, which already implements the full handshake.

Example

No code snippet is provided as the issue does not contain sufficient information about the implementation details.

Notes

The provided information suggests that the issue is specific to the openclaw CLI and its interaction with the Gateway via WebSocket RPC. The fact that openclaw --version works because it bypasses the Gateway connection entirely supports this conclusion.

Recommendation

Apply workaround: Use the Control UI for now, as it implements the full device auth v2 handshake, while the openclaw CLI implementation is updated to include the missing device auth v2 handshake response.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

CLI commands complete normally with output, or show a proper error message.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING