openclaw - 💡(How to fix) Fix Upgrade can leave old OpenClaw install in place and create split-path versions [1 comments, 2 participants]

An upgrade should replace/remove the old install, or at least detect and warn clearly when multiple OpenClaw installs exist and different entrypoints may resolve to different versions.

TL;DR

The issue can be mitigated by manually removing the old system install of OpenClaw and updating the /usr/bin/openclaw symlink to point to the new install.

Guidance

• Verify the existence of multiple OpenClaw installs by checking the versions reported by /usr/bin/openclaw --version and the active NVM-managed CLI.
• Manually remove the old system install under /usr/lib/node_modules/openclaw to prevent version conflicts.
• Update the /usr/bin/openclaw symlink to point to the new install location, ensuring consistency across the system.
• Consider adding a check to the upgrade process to detect and warn about multiple installs, ensuring a smooth upgrade experience.

Notes

This solution assumes that the old system install is no longer needed and can be safely removed. If the old install is still required, alternative solutions such as using version managers or modifying the PATH environment variable may be necessary.

Recommendation

Apply workaround: Manually remove the old system install and update the symlink, as this provides a straightforward solution to the observed issue and ensures consistency across the system.