#Auto update killing openclaw
1 messages · Page 1 of 1 (latest)
First thing, can you paste openclaw --version? Version mismatch stuff is super version-sensitive.
Short answer: the safer pattern is usually not to let plugin-heavy setups auto-apply updates blindly.
A lot of people handle it by:
- staying on stable
- doing manual
openclaw update - then updating plugins in the same window:
openclaw plugins update --all - or pinning the core/plugin version until the plugin catches up
That lines up with the docs too:
- the auto-updater is off by default: https://docs.openclaw.ai/install/updating
- channel changes also sync plugin sources, and npm plugins update after core: https://docs.openclaw.ai/install/development-channels
- plugin commands: https://docs.openclaw.ai/tools/plugin
So if auto-update is upgrading core first and a plugin is lagging, I’d honestly disable auto-apply for now and update intentionally.