OpenClaw Dashboard Disconnecting After 2026.5.27 Update? Fix: Remove Stuck Update Launchd Job

After upgrading to OpenClaw 2026.5.27, a user reports dashboard WebSocket disconnects, unreliable Telegram responses, and the gateway repeatedly unloading. The root cause: a stuck update process registered as a launchd job that kept respawning and interfering with the gateway.

Symptoms

• Dashboard repeatedly disconnects with WebSocket/gateway errors.
• Telegram responds intermittently.
• openclaw gateway status --deep alternates between healthy and completely unloaded.
• Gateway restarts at random; logs show repeated SIGTERM/shutdown/restart cycles.

Fix

Run this command to remove the stuck update launchd job:

launchctl bootout gui/501/openclaw-update-2026-05-27

Then restart the gateway. The update script will stop reappearing, the gateway will stay loaded, Telegram will respond consistently, and the dashboard will stabilize.

Root Cause

The openclaw-update-2026-05-27 job remained registered with launchd even after the update script finished. It kept restarting, interfering with the gateway. Telegram was never the problem, nor was OpenAI auth. The gateway often appeared healthy before being killed again.

This may be a bug in the 2026.5.27 update process itself, or at least a scenario where the update gets stuck on certain machines. If anyone finds a cleaner fix, please share.