Help Captain CTE with his stupid claw box

[vernal bane]

5:23:58 PM
warn
gateway/ws
protocol mismatch conn=8dc8b531-619a-4c07-a4f2-fffc1e89089f remote=127.0.0.1 client=openclaw-control-ui webchat v2026.5.6
5:23:58 PM
warn
gateway/ws
closed before connect conn=8dc8b531-619a-4c07-a4f2-fffc1e89089f peer=127.0.0.1:60970->127.0.0.1:18789 remote=127.0.0.1 fwd=n/a origin=http://127.0.0.1:18789/ host=127.0.0.1:18789 ua=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/26.4 Safari/605.1.15 code=1002 reason=protocol mismatch

what's happening? @hearty hemlock

[hybrid wave]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[vernal bane]

@lyric shale help

[lyric shale]

That log means the browser Control UI connected, sent its WS connect handshake, and the gateway rejected it because the client protocol range doesn’t match the gateway protocol. In plain terms: the UI bundle and gateway are from different builds/versions, or the UI assets are stale.

First check the version mismatch:

openclaw --version
openclaw status
openclaw gateway status

Then run the repair path:

openclaw doctor

If this is a source/git install, rebuild the UI assets and restart the gateway:

[lyric shale]

pnpm install
pnpm build
pnpm ui:build
openclaw gateway restart

If it’s a packaged/global install, update/reinstall OpenClaw so the gateway and Control UI come from the same version, then restart the gateway. The log shows openclaw-control-ui webchat v2026.5.6, so I’d specifically compare that against openclaw --version.

Relevant docs: https://docs.openclaw.ai/help/faq and https://docs.openclaw.ai/gateway/protocol

[hearty hemlock]

i hate you

[vernal bane]

that looks legit answer, are you building your openclaw from a local cloned directory?

[lyric shale]

Yeah, that’s the key question. If they’re running from a local cloned/source checkout, stale built UI assets are very plausible: the gateway code can be newer than the ui bundle it’s serving.

For source checkout, I’d have them run from the repo root:

git status --short
openclaw --version
pnpm install
pnpm build
pnpm ui:build
openclaw gateway restart

If they’re not on a source checkout, then it’s more likely a mixed install/version problem: update/reinstall OpenClaw and restart the gateway so the bundled Control UI and gateway match.

[vernal bane]

^^

[hearty hemlock]

mlabidsr@Macdaddy .openclaw % git status --short
fatal: not a git repository (or any of the parent directories): .git

[lyric shale]

Big Poppa, that just means you ran git status inside ~/.openclaw, which is runtime data/config, not the source repo.

Next useful checks:

openclaw --version
which openclaw
openclaw status
openclaw gateway status

If which openclaw points into a git checkout, cd to that checkout and rebuild from there. If it points to a global/package install, skip the git/source commands and update/reinstall OpenClaw, then restart the gateway. The important bit is getting the gateway and served Control UI onto the same version.

[hearty hemlock]

mlabidsr@Macdaddy .openclaw % openclaw --version
OpenClaw 2026.5.12 (f066dd2)
mlabidsr@Macdaddy .openclaw % which openclaw
/Users/mlabidsr/.nvm/versions/node/v24.14.0/bin/openclaw

[lyric shale]

Big Poppa, there’s the mismatch: your CLI is 2026.5.12, but the log says the browser UI is 2026.5.6. So the gateway/served Control UI is stale or the daemon is still running from an older install path.

Check what the running daemon is actually using:

openclaw gateway status
openclaw status

Because this is under nvm, I’d restart/reinstall the gateway service from the same Node/OpenClaw that which openclaw shows:

openclaw gateway restart

If it still serves 2026.5.6, do the stronger service refresh:

openclaw gateway uninstall

[lyric shale]

openclaw gateway install --force
openclaw gateway restart

Then hard-refresh the browser tab or reopen http://127.0.0.1:18789/. If gateway status shows a different Node path than /Users/mlabidsr/.nvm/versions/node/v24.14.0/bin/openclaw, that’s the stale LaunchAgent problem.

[hearty hemlock]

mlabidsr@Macdaddy .openclaw % openclaw gateway status
Config warnings:

• plugins.entries.openclaw-web-search: plugin openclaw-web-search: installed plugin package requires compiled runtime output for TypeScript entry index.ts: expected ./dist/index.js, ./dist/index.mjs, ./dist/index.cjs, index.js, index.mjs, index.cjs. This is a plugin packaging issue, not a local config problem; update or reinstall the plugin after the publisher ships compiled JavaScript, or disable/uninstall the plugin until then. TypeScript source fallback is only supported for source checkouts and local development paths.

🦞 OpenClaw 2026.5.12 (f066dd2) — Hot reload for config, cold sweat for deploys.

│
◇
Service: LaunchAgent (loaded)
File logs: /tmp/openclaw/openclaw-2026-05-15.log
Command: /opt/homebrew/bin/node /Users/mlabidsr/.nvm/versions/node/v24.14.0/lib/node_modules/openclaw/dist/index.js gateway --port 18789
Service file: ~/Library/LaunchAgents/ai.openclaw.gateway.plist
Working dir: ~/.openclaw
Service env: OPENCLAW_GATEWAY_PORT=18789

Config (cli): ~/.openclaw/openclaw.json
Config (service): ~/.openclaw/openclaw.json

Gateway: bind=loopback (127.0.0.1), port=18789 (service args)
Probe target: ws://127.0.0.1:18789
Dashboard: http://127.0.0.1:18789/
Probe note: Loopback-only gateway; only local clients can connect.

CLI version: 2026.5.12 (~/.nvm/versions/node/v24.14.0/bin/openclaw)
Gateway version: 2026.5.12

Runtime: running (pid 95036, state active)
Connectivity probe: ok
Capability: admin-capable

Listening: 127.0.0.1:18789
Troubles: run openclaw status
Troubleshooting: https://docs.openclaw.ai/troubleshooting

[lyric shale]

This is cleaner: CLI and gateway are both 2026.5.12, so the daemon itself is not the old one.

The remaining suspicious bit is the browser client still reporting openclaw-control-ui webchat v2026.5.6. That’s either cached/stale browser UI assets or stale served UI files inside the install.

Try this first:

openclaw doctor
openclaw gateway restart

Then in Safari, fully clear/reload the local dashboard: close the tab, reopen http://127.0.0.1:18789/, and use a hard reload / clear website data for 127.0.0.1 if Safari keeps the old bundle.

The openclaw-web-search plugin warning is separate. It means that plugin package is missing compiled JS output; disable/uninstall/update that plugin later, but it’s not the websocket protocol mismatch.

[hearty hemlock]

refresh expiring oauth tokens now?

[lyric shale]

Yes, answer yes to that doctor prompt. It only targets OAuth/token profiles that are expired, expiring, or missing; static tokens may still need re-auth, which the prompt says.

If refresh fails with invalid_grant, refresh_token_reused, or similar, then rerun the auth login command doctor prints for that provider. Docs: https://docs.openclaw.ai/gateway/doctor#5-model-auth-health-oauth-expiry

[hearty hemlock]

OAuth refresh errors ───────────────────────────────────────────────────────────────────╮
│ │
│ - openai-codex:default: re-auth required [refresh_token_reused] — Run openclaw models │ │ auth login --provider openai-codex. │
│ │
├──────────────────────────────────────────────────────────────────────────────────────────╯
│
◇ Model auth ─────────────────────────────────────────────────────────────────────╮
│ │
│ - openai-codex:default: expired (0m) — Re-auth via openclaw models auth login │ │ --provider openai-codex or openclaw configure. │
│ │
├─────────────────────────────────────────────────────────────────────

i have done this 14x

[lyric shale]

Big Poppa, if re-auth has worked 14x and doctor still says the same openai-codex:default token is expired/reused, I’d treat this as stale auth state being reused, not “try login again.”

Do this with the gateway stopped so it can’t keep an old snapshot around:

openclaw gateway stop

Then find the OpenAI Codex auth stores, but don’t paste file contents here because they contain tokens:

find ~/.openclaw -path '*auth-profiles.json' -o -path '*auth.json' -o -path '*credentials/oauth.json'
rg -n 'openai-codex|refresh_token' ~/.openclaw/agents ~/.openclaw/credentials

The current main store is usually:

~/.openclaw/agents/main/agent/auth-profiles.json