# After updating, the OpenClaw command exists but its package files are missing **URL:** \ **Category:** Troubleshooting\ **Tags:** gateway, installation, linux, troubleshooting, updates\ **Created:** [September 14, 2026, 10:31pm UTC](https://community.openclaw.ai/t/after-updating-the-openclaw-command-exists-but-its-package-files-are-missing/80 "2026-09-14T22:31:12Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![ArchivedMember](https://avatars.discourse-cdn.com/v4/letter/a/e56c9b/32.png) [@ArchivedMember](https://community.openclaw.ai/u/ArchivedMember)\ **Post date:** [September 14, 2026, 10:31pm UTC](https://community.openclaw.ai/t/after-updating-the-openclaw-command-exists-but-its-package-files-are-missing/80/1 "2026-09-14T22:31:12Z")
> **Adapted community discussion:** Paraphrased and condensed from an anonymized public OpenClaw Discord support conversation from September 2026. Technical guidance was reviewed for OpenClaw 2026.9.3. After an update on my Linux box, the `openclaw` command no longer runs. I am connected over Tailscale SSH, and checking the service with a root-level systemctl command does not show anything. ---
**Author:** ![OpenClawSupport](https://avatars.discourse-cdn.com/v4/letter/o/49beb7/32.png) [@OpenClawSupport](https://community.openclaw.ai/u/OpenClawSupport)\ **Post date:** [September 14, 2026, 10:31pm UTC](https://community.openclaw.ai/t/after-updating-the-openclaw-command-exists-but-its-package-files-are-missing/80/2 "2026-09-14T22:31:12Z")
Tailscale is only the SSH transport. A minimal login shell can have a different PATH, and `sudo systemctl` checks the wrong service manager. Use the same non-root account that installed OpenClaw, then inspect: ```bash whoami command -v openclaw || true node --version npm prefix -g export XDG_RUNTIME_DIR=/run/user/$(id -u) systemctl --user status openclaw-gateway.service --no-pager ``` ---
**Author:** ![ArchivedMember](https://avatars.discourse-cdn.com/v4/letter/a/e56c9b/32.png) [@ArchivedMember](https://community.openclaw.ai/u/ArchivedMember)\ **Post date:** [September 14, 2026, 10:31pm UTC](https://community.openclaw.ai/t/after-updating-the-openclaw-command-exists-but-its-package-files-are-missing/80/3 "2026-09-14T22:31:12Z")
The launcher resolves, but Node says it cannot find OpenClaw’s `dist/index.js` under the global package root. I am using the same normal account as before. ---
**Author:** ![OpenClawSupport](https://avatars.discourse-cdn.com/v4/letter/o/49beb7/32.png) [@OpenClawSupport](https://community.openclaw.ai/u/OpenClawSupport)\ **Post date:** [September 14, 2026, 10:31pm UTC](https://community.openclaw.ai/t/after-updating-the-openclaw-command-exists-but-its-package-files-are-missing/80/4 "2026-09-14T22:31:12Z")
That is an incomplete global package, not a Tailscale problem. Confirm the package root and installed version record before repairing it: ```bash command -v openclaw npm root -g npm --version npm list -g --depth=0 openclaw 2>&1 ``` Repair the same installation method and package root. Do not create a second package-manager installation. ---
**Author:** ![ArchivedMember](https://avatars.discourse-cdn.com/v4/letter/a/e56c9b/32.png) [@ArchivedMember](https://community.openclaw.ai/u/ArchivedMember)\ **Post date:** [September 14, 2026, 10:31pm UTC](https://community.openclaw.ai/t/after-updating-the-openclaw-command-exists-but-its-package-files-are-missing/80/5 "2026-09-14T22:31:12Z")
The global package listing shows `openclaw@` without a version, while the launcher points into that same global npm installation. ---
**Author:** ![OpenClawSupport](https://avatars.discourse-cdn.com/v4/letter/o/49beb7/32.png) [@OpenClawSupport](https://community.openclaw.ai/u/OpenClawSupport)\ **Post date:** [September 14, 2026, 10:31pm UTC](https://community.openclaw.ai/t/after-updating-the-openclaw-command-exists-but-its-package-files-are-missing/80/6 "2026-09-14T22:31:12Z")
That confirms a partial npm install. Reinstall the current stable package into that same global prefix, then verify the CLI: ```bash sudo npm install -g openclaw@latest --allow-scripts=openclaw openclaw --version ``` If the CLI returns but the user service still names the older release, align its service metadata and restart it as the same non-root user: ```bash openclaw gateway install --force openclaw gateway restart openclaw gateway status --deep ``` If your npm release does not support `--allow-scripts`, use the installer documented for your platform rather than creating another package prefix. ---
**Author:** ![ArchivedMember](https://avatars.discourse-cdn.com/v4/letter/a/e56c9b/32.png) [@ArchivedMember](https://community.openclaw.ai/u/ArchivedMember)\ **Post date:** [September 14, 2026, 10:31pm UTC](https://community.openclaw.ai/t/after-updating-the-openclaw-command-exists-but-its-package-files-are-missing/80/7 "2026-09-14T22:31:13Z")
That brought the Gateway back up. ---
**Author:** ![OpenClawSupport](https://avatars.discourse-cdn.com/v4/letter/o/49beb7/32.png) [@OpenClawSupport](https://community.openclaw.ai/u/OpenClawSupport)\ **Post date:** [September 14, 2026, 10:31pm UTC](https://community.openclaw.ai/t/after-updating-the-openclaw-command-exists-but-its-package-files-are-missing/80/8 "2026-09-14T22:31:13Z")
Finish with a smoke test: ```bash openclaw gateway status --deep openclaw channels status --probe ``` A complete recovery shows a running runtime, an OK connectivity probe, and healthy configured channels.