---
title: OpenClaw Core Update
area: infrastructure
tags: [infrastructure, assistant, automation, health]
created: 2026-03-25
updated: 2026-03-25
status: active
related: [[Infrastructure/Architecture]]
---

# OpenClaw Core Update

Updated OpenClaw core to `2026.3.23-2`.

## Post-update verification

- `dist/control-ui/` assets are present in the installed package
- Discord message tool schema includes `Type.Optional(createDiscordMessageToolComponentsSchema())`
- gateway/runtime verified healthy after launcher repair

## Issue found

The global CLI launcher at `~/.local/bin/openclaw` was stale after the update and still pointed at a removed version-pinned pnpm path for `2026.3.22`. That broke commands like `openclaw status` with `Cannot find module ... /openclaw.mjs` even though the actual installed package was correct.

## Fix

Replaced `~/.local/bin/openclaw` with a stable wrapper that launches the symlinked package path at:

- `/home/openclaw/.local/share/pnpm/5/node_modules/openclaw/openclaw.mjs`

This avoids depending on a removed version-specific pnpm path.

## Additional work completed

- Removed stale `openclaw@2026.3.13` from the global store, freeing about 185 MB
- Updated the instance registry so `orb` and `sun` now show as stopped
- Backed up the post-upgrade config to the local mirror and MinIO

## Upgrade workarounds used

- pnpm virtual-store conflict: used `pnpm install` in the global store directory instead of `pnpm add -g`
- non-interactive SSH PATH issue: exported PATH manually before running OpenClaw commands

## Snapshot limitation

The current VM uses pflash-based firmware, which prevents libvirt internal snapshots. If pre-upgrade VM snapshots are wanted later, either:

- convert the NVRAM to qcow2, or
- use external file-based snapshots instead

## Outstanding watch item

No fix yet for advisory `GHSA-7xr2-q9vf-x4r5` (symlink traversal via `IDENTITY.md` appendFile). Keep watching future OpenClaw releases for a patch.

## Operational note

For future OpenClaw updates, verify `openclaw status` immediately after the update. If it fails with an older package path, inspect `which openclaw` and the launcher contents before assuming the package install itself is broken.
