OpenClaw macOS app 2026.8.2 sticks on native-importing and the handshake times out

After the macOS app moves from 2026.7.1 to 2026.8.2, the native gateway connection never finishes. Each launch renames the identity file and leaves it there.

Difficulty

Easy

Time

~5 min

Steps

Fixed in

—

Last checked

Oct 18, 2026

Not fixed upstream yet: the issue is open. Source: issue open. Last checked 2026-10-18.

Symptom

After the macOS app moves from 2026.7.1 to 2026.8.2, the native gateway connection never finishes. Each launch renames the identity file and leaves it there.

Evidence what you'll see

The gateway log shows closed before connect ... phase=ws_upgrade_started and handshake timeout ... phase=ws_upgrade_started.
The app renames device.json to device.json.native-importing under ~/Library/Application Support/OpenClaw/identity/ and does not write a new identity.
The in-app web UI still chats. Deleting the identity files did not make the app create another identity.

Why it happens

The report says the 2026.8.2 native-import step never finishes, so the native handshake has nothing to sign. Pairing rows on the gateway already listed this device, and the connection still timed out.

Affected versions

macOS 15.x on MacBookPro16,1. The app is 2026.8.2 (2608000290, commit 0965053fe6b9). The CLI and gateway are 2026.8.2 (0965053). The previous app was 2026.7.1.

Fix steps

0 of 2 done

Step 1The linked issue does not give a command that finishes the import or replaces the identity file.
Step 2The report's own try, deleting the identity files, left the native connection on handshake timeout.

Your check marks stay in this browser only.

How to check it worked

A native connection from user agent OpenClaw/2608000290 gets past phase=ws_upgrade_started without handshake timeout, and device.json.native-importing is not the file left on disk.

If it still fails

The report says device_pairing_paired and device_auth_tokens already contained this device. The linked issue does not name a later app build.

Sources and credit

Summarized in our own words from these public reports. Credit goes to their authors.

openclaw issue #137085 ↗

Provided as is, without warranty. Try changes in a non-production environment and back up first. Security-related steps: verify against the official docs. Terms · Request removal or attribution change

Hit an error we don't cover? Submit it