Bug Description
When using openclaw gateway restart via Discord (or any remote channel), the CLI incorrectly reports "Gateway service not loaded" even when the Gateway is actually running.
Steps to Reproduce
- Have OpenClaw Gateway installed as a user LaunchAgent (~/.openclaw/launchd.plist or via
openclaw gateway install)
- Gateway is running (verified via
launchctl list | grep openclaw shows PID)
- Run
openclaw gateway restart
- CLI reports "Gateway service not loaded" and suggests running
openclaw gateway install
Expected Behavior
CLI should correctly detect that the user LaunchAgent is running and allow restart without reinstalling.
Workaround
Using launchctl kickstart -k gui/502/ai.openclaw.gateway works correctly.
Additional Context
- macOS user LaunchAgents (in ~/Library/LaunchAgents/) only run when a user is logged in
- For headless Macs, the Gateway may not auto-start after Mac reboot
- The CLI's status check appears to have a false-negative bug for the gui/* domain
Bug Description
When using
openclaw gateway restartvia Discord (or any remote channel), the CLI incorrectly reports "Gateway service not loaded" even when the Gateway is actually running.Steps to Reproduce
openclaw gateway install)launchctl list | grep openclawshows PID)openclaw gateway restartopenclaw gateway installExpected Behavior
CLI should correctly detect that the user LaunchAgent is running and allow restart without reinstalling.
Workaround
Using
launchctl kickstart -k gui/502/ai.openclaw.gatewayworks correctly.Additional Context