#MacOS broke openclaw setup
1 messages · Page 1 of 1 (latest)
This sounds like the macOS app may have changed/rehomed the gateway LaunchAgent or CLI version, so both dashboard + Telegram would go down because the Gateway isn’t actually running/reachable.
First thing: what does this show?
openclaw --version
which openclaw
openclaw status --all
openclaw gateway status --deep
Then try the safe recovery path:
openclaw doctor
openclaw gateway install --force
openclaw gateway restart
openclaw gateway status
On macOS, also check the app-managed launchd log:
tail -n 120 /tmp/openclaw/openclaw-gateway.log
If you paste the outputs here, please redact tokens/secrets. status --all should be safe/redacted.
Useful context: the macOS app doesn’t bundle its own Gateway anymore; it expects an external openclaw CLI and manages/attaches to the per-user LaunchAgent. So if the app installed a different CLI or rewrote the service, this is likely a split-brain/version/path issue.