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

# OpenClaw Core Update

This note started with the 2026-03-25 update / repair pass and now includes the follow-up state through 2026-03-27.

## 2026-03-25 update pass

OpenClaw was updated to `2026.3.23-2`.

### Post-update verification
- `dist/control-ui/` assets 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` even though the actual installed package was correct.

### Fix
Replaced `~/.local/bin/openclaw` with a stable wrapper targeting:
- `/home/openclaw/.local/share/pnpm/5/node_modules/openclaw/openclaw.mjs`

### Additional work completed
- Removed stale `openclaw@2026.3.13` from the global store
- Updated the instance registry so `orb` and `sun` now show as stopped
- Backed up the post-upgrade config to the local mirror and MinIO

## 2026-03-26 follow-up update

OpenClaw was then updated again to `2026.3.24` using the safe update workflow.

### Notes from that pass
- prior dist/hotfix workarounds were fixed upstream; no local patch re-application was needed
- `openclaw-update-safe.sh` was updated so it also patches the systemd service unit after future updates when needed
- MinIO backup was taken during the update run

## Current live state (checked 2026-03-27)

- `openclaw status` reports runtime version `2026.3.24`
- gateway reachable and healthy
- Telegram enabled (`WARN` posture note only)
- Discord enabled (`OK`)

## Outstanding watch item

Still keep watching future OpenClaw releases for a fix to advisory `GHSA-7xr2-q9vf-x4r5` (symlink traversal via `IDENTITY.md` appendFile).

## Operational note

For future OpenClaw updates:
- run `openclaw status` immediately after the update
- if it points at an older package path, inspect `which openclaw` and the launcher contents before assuming the install itself is broken
