Skip to content

openclaw status shows stale Gateway app version after npm upgrade (CLI 2026.3.2, app shown as 2026.2.21) #32647

@eguchi-lab

Description

@eguchi-lab

Summary

After upgrading OpenClaw via npm, openclaw --version reports the new version correctly, but openclaw status still shows an older version in the Gateway line (app 2026.2.21).

Environment

  • Device: Raspberry Pi (arm64)
  • OS: Linux 6.12.47+rpt-rpi-2712
  • Node.js: 22.22.0
  • Install mode: global npm package
  • Channel: stable

Steps to Reproduce

  1. Upgrade OpenClaw:
    sudo npm i -g openclaw@2026.3.2
  2. Restart gateway:
    openclaw gateway restart
  3. Check CLI version:
    openclaw --version
  4. Check status:
    openclaw status

Actual Behavior

  • openclaw --version => 2026.3.2
  • openclaw status Gateway row includes:
    • ... auth token ... app 2026.2.21 ...

Expected Behavior

openclaw status should display the currently running Gateway app version consistently with the installed/running version (or clearly indicate what that field represents if it is not app runtime version).

Additional Notes

Operationally, the system appears healthy:

  • openclaw gateway status => running, RPC probe ok
  • Slack probe => ok
  • Cron notifications => delivered

So this looks like a status/version reporting inconsistency rather than a runtime failure.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions