openclaw - 💡(How to fix) Fix [Bug]:TUI cannot connect to gateway after version mismatch (device identity required) [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#73661Fetched 2026-04-29 06:16:46
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
labeled ×2closed ×1commented ×1

TUI fails to connect to gateway after upgrading gateway version, returning "device identity required".

Root Cause

TUI fails to connect to gateway after upgrading gateway version, returning "device identity required".

Fix Action

Fix / Workaround

  1. Upgrade to 2026.4.24: npm install -g [email protected]

Code Example

TUI output:

device identity required
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

TUI fails to connect to gateway after upgrading gateway version, returning "device identity required".

Steps to reproduce

  1. Install OpenClaw 2026.3.15: npm install -g [email protected]

  2. Upgrade to 2026.4.24: npm install -g [email protected]

  3. Run: openclaw gateway

  4. In another terminal: openclaw tui

  5. Observe connection failure

Expected behavior

TUI should successfully connect to the gateway and establish a session.

Actual behavior

TUI fails to connect and shows: "device identity required"

In some cases, the connection closes immediately.

OpenClaw version

2026.4.24

Operating system

macOS 15.4

Install method

npm global

Model

NOT_RELEVANT

Provider / routing chain

NOT_RELEVANT

Additional provider/model setup details

NOT_RELEVANT

Logs, screenshots, and evidence

TUI output:

device identity required

Impact and severity

Affected: Users upgrading gateway without reinstalling TUI Severity: High (TUI unusable) Frequency: Always (reproduced multiple times) Consequence: CLI cannot connect to gateway

Additional information

Reinstalling the latest version resolves the issue:

npm install -g openclaw@latest

Downgrading gateway also restores connectivity:

npm install -g [email protected]

extent analysis

TL;DR

Reinstalling the latest version of OpenClaw or downgrading the gateway to a previous version may resolve the connection issue between TUI and the gateway.

Guidance

  • The error "device identity required" suggests a potential compatibility issue between the TUI and the upgraded gateway version.
  • Reinstalling the latest version of OpenClaw (npm install -g openclaw@latest) has been reported to resolve the issue, indicating a possible version mismatch or configuration problem.
  • Downgrading the gateway to a previous version (npm install -g [email protected]) also restores connectivity, further supporting the idea of a version compatibility issue.
  • To mitigate the problem, users upgrading their gateway should also reinstall the TUI to ensure version consistency.

Example

No specific code snippet is necessary for this issue, as the solution involves managing package versions rather than modifying code.

Notes

The exact cause of the compatibility issue between the TUI and the gateway after the upgrade is not specified, but it is clear that version consistency is key to resolving the problem. This solution assumes that the latest version of OpenClaw includes fixes for the identified issue.

Recommendation

Apply workaround: Reinstall the latest version of OpenClaw (npm install -g openclaw@latest) after upgrading the gateway to ensure compatibility and resolve the connection issue. This approach is recommended because it has been explicitly mentioned as a resolution method in the issue description.

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

TUI should successfully connect to the gateway and establish a session.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING