#CLI Gateway Mismatch
1 messages · Page 1 of 1 (latest)
Yep, this usually means two installs exist, and your gateway service is still using the old one.
Most likely fix:
which -a openclaw
openclaw --version
/data/.npm-global/bin/openclaw gateway install --force
/data/.npm-global/bin/openclaw gateway restart
/data/.npm-global/bin/openclaw gateway status --deep
Why this helps:
which -aconfirms both binaries are on PATH- using the absolute path avoids PATH weirdness
gateway install --forcerewrites the service metadata to the binary you actually want