Possible Bug: OPENCLAW_SERVICE_VERSION in LaunchAgent plist not updated on openclaw update (macOS)
Version: 2026.3.2 (upgraded from 2026.3.1)
Platform: macOS / LaunchAgent
What happens:
After running openclaw update, the gateway binary is correctly upgraded but the LaunchAgent plist at ~/Library/LaunchAgents/ai.openclaw.gateway.plist retains the old OPENCLAW_SERVICE_VERSION env var. The gateway process reads this env var as its reported version, so the Control UI shows the old version number even though the binary is current.
Root cause (traced through source):
openclaw update upgrades the binary but never regenerates the plist
openclaw gateway restart just reloads the existing plist via launchctl — no regeneration
openclaw gateway install detects the service is already loaded and exits early unless --force is passed
The plist generation code in daemon-install-helpers-CnQ4h1UP.js correctly sets OPENCLAW_SERVICE_VERSION: VERSION — it just never gets called during an update
Workaround:
openclaw gateway install --force
Or manually edit the plist and update OPENCLAW_SERVICE_VERSION, then reload.
Suggested fix:
openclaw update (or the post-update flow) should call openclaw gateway install --force to regenerate the plist with the new version, or at minimum patch the OPENCLAW_SERVICE_VERSION env var in the existing plist.
Platform: macOS / LaunchAgent
What happens:
After running openclaw update, the gateway binary is correctly upgraded but the LaunchAgent plist at ~/Library/LaunchAgents/ai.openclaw.gateway.plist retains the old OPENCLAW_SERVICE_VERSION env var. The gateway process reads this env var as its reported version, so the Control UI shows the old version number even though the binary is current.
Root cause (traced through source):
openclaw update upgrades the binary but never regenerates the plist
openclaw gateway restart just reloads the existing plist via launchctl — no regeneration
openclaw gateway install detects the service is already loaded and exits early unless --force is passed
The plist generation code in daemon-install-helpers-CnQ4h1UP.js correctly sets OPENCLAW_SERVICE_VERSION: VERSION — it just never gets called during an update
Workaround:
openclaw gateway install --force
Or manually edit the plist and update OPENCLAW_SERVICE_VERSION, then reload.
Suggested fix:
openclaw update (or the post-update flow) should call openclaw gateway install --force to regenerate the plist with the new version, or at minimum patch the OPENCLAW_SERVICE_VERSION env var in the existing plist.
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
134,827Members
Resources
Similar Threads
Was this page helpful?
