Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Feature]: 2026.4.24 v2 profile creates dual plugin-runtime-deps trees and ENOTEMPTY on plugin-sdk alias setup; upgrade path blocked despite gateway healthy

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

On macOS with profile-scoped state (OPENCLAW_STATE_DIR=~/.openclaw-v2), OpenClaw 2026.4.24 installed via npm global still creates two parallel plugin-runtime-deps install roots and intermittently hits ENOTEMPTY when rebuilding the plugin-sdk alias directory.

The gateway can run and channels can connect, but the CLI / bundled-channel registration / upgrade path remains unsafe.

Related issues #72528, #72956, #72521, #71812, and #74818 are all closed. #72528 was closed as fixed on main, but our released npm 2026.4.24 deployment still shows the dual-tree + ENOTEMPTY symptom family. We are requesting confirmation of the released version that contains the fix and the recommended migration steps before upgrading.

Root Cause

On macOS with profile-scoped state (OPENCLAW_STATE_DIR=~/.openclaw-v2), OpenClaw 2026.4.24 installed via npm global still creates two parallel plugin-runtime-deps install roots and intermittently hits ENOTEMPTY when rebuilding the plugin-sdk alias directory.

The gateway can run and channels can connect, but the CLI / bundled-channel registration / upgrade path remains unsafe.

Related issues #72528, #72956, #72521, #71812, and #74818 are all closed. #72528 was closed as fixed on main, but our released npm 2026.4.24 deployment still shows the dual-tree + ENOTEMPTY symptom family. We are requesting confirmation of the released version that contains the fix and the recommended migration steps before upgrading.

Code Example

openclaw-2026.4.24-da6bdffc3d96/
openclaw-unknown-b06c60528ba3/

### Problem to solve

### Summary

On macOS with profile-scoped state (`OPENCLAW_STATE_DIR=~/.openclaw-v2`), **OpenClaw 2026.4.24** installed via npm global still creates **two parallel** `plugin-runtime-deps` install roots and intermittently hits **`ENOTEMPTY`** when rebuilding the `plugin-sdk` alias directory.

The gateway can run and channels can connect, but the CLI / bundled-channel registration / upgrade path remains unsafe.

Related issues **#72528**, **#72956**, **#72521**, **#71812**, and **#74818** are all closed. #72528 was closed as fixed on `main`, but our released npm `2026.4.24` deployment still shows the dual-tree + ENOTEMPTY symptom family. We are requesting confirmation of the released version that contains the fix and the recommended migration steps before upgrading.

---

### Environment

| Item | Value |
|---|---|
| Host OS | macOS 26.5, arm64 |
| OpenClaw CLI | 2026.4.24, npm global |
| OpenClaw.app | 2026.5.20 installed, but not used by gateway LaunchAgents |
| Runtime authority | npm global CLI |
| Profile | v2 |
| Gateway | `:18790`, LaunchAgent uses npm-global `dist/index.js` |

---

### Dual runtime tree

Active roots under `~/.openclaw-v2/plugin-runtime-deps/`:

---

openclaw-2026.4.24-da6bdffc3d96/
openclaw-unknown-b06c60528ba3/

### Alternatives considered

_No response_

### Impact

### Summary

On macOS with profile-scoped state (`OPENCLAW_STATE_DIR=~/.openclaw-v2`), **OpenClaw 2026.4.24** installed via npm global still creates **two parallel** `plugin-runtime-deps` install roots and intermittently hits **`ENOTEMPTY`** when rebuilding the `plugin-sdk` alias directory.

The gateway can run and channels can connect, but the CLI / bundled-channel registration / upgrade path remains unsafe.

Related issues **#72528**, **#72956**, **#72521**, **#71812**, and **#74818** are all closed. #72528 was closed as fixed on `main`, but our released npm `2026.4.24` deployment still shows the dual-tree + ENOTEMPTY symptom family. We are requesting confirmation of the released version that contains the fix and the recommended migration steps before upgrading.

---

### Environment

| Item | Value |
|---|---|
| Host OS | macOS 26.5, arm64 |
| OpenClaw CLI | 2026.4.24, npm global |
| OpenClaw.app | 2026.5.20 installed, but not used by gateway LaunchAgents |
| Runtime authority | npm global CLI |
| Profile | v2 |
| Gateway | `:18790`, LaunchAgent uses npm-global `dist/index.js` |

---

### Dual runtime tree

Active roots under `~/.openclaw-v2/plugin-runtime-deps/`:
RAW_BUFFERClick to expand / collapse

Summary

Summary

On macOS with profile-scoped state (OPENCLAW_STATE_DIR=~/.openclaw-v2), OpenClaw 2026.4.24 installed via npm global still creates two parallel plugin-runtime-deps install roots and intermittently hits ENOTEMPTY when rebuilding the plugin-sdk alias directory.

The gateway can run and channels can connect, but the CLI / bundled-channel registration / upgrade path remains unsafe.

Related issues #72528, #72956, #72521, #71812, and #74818 are all closed. #72528 was closed as fixed on main, but our released npm 2026.4.24 deployment still shows the dual-tree + ENOTEMPTY symptom family. We are requesting confirmation of the released version that contains the fix and the recommended migration steps before upgrading.

Environment

ItemValue
Host OSmacOS 26.5, arm64
OpenClaw CLI2026.4.24, npm global
OpenClaw.app2026.5.20 installed, but not used by gateway LaunchAgents
Runtime authoritynpm global CLI
Profilev2
Gateway:18790, LaunchAgent uses npm-global dist/index.js

Dual runtime tree

Active roots under ~/.openclaw-v2/plugin-runtime-deps/:

openclaw-2026.4.24-da6bdffc3d96/
openclaw-unknown-b06c60528ba3/

### Problem to solve

### Summary

On macOS with profile-scoped state (`OPENCLAW_STATE_DIR=~/.openclaw-v2`), **OpenClaw 2026.4.24** installed via npm global still creates **two parallel** `plugin-runtime-deps` install roots and intermittently hits **`ENOTEMPTY`** when rebuilding the `plugin-sdk` alias directory.

The gateway can run and channels can connect, but the CLI / bundled-channel registration / upgrade path remains unsafe.

Related issues **#72528**, **#72956**, **#72521**, **#71812**, and **#74818** are all closed. #72528 was closed as fixed on `main`, but our released npm `2026.4.24` deployment still shows the dual-tree + ENOTEMPTY symptom family. We are requesting confirmation of the released version that contains the fix and the recommended migration steps before upgrading.

---

### Environment

| Item | Value |
|---|---|
| Host OS | macOS 26.5, arm64 |
| OpenClaw CLI | 2026.4.24, npm global |
| OpenClaw.app | 2026.5.20 installed, but not used by gateway LaunchAgents |
| Runtime authority | npm global CLI |
| Profile | v2 |
| Gateway | `:18790`, LaunchAgent uses npm-global `dist/index.js` |

---

### Dual runtime tree

Active roots under `~/.openclaw-v2/plugin-runtime-deps/`:

```text
openclaw-2026.4.24-da6bdffc3d96/
openclaw-unknown-b06c60528ba3/

### Proposed solution

### Summary

On macOS with profile-scoped state (`OPENCLAW_STATE_DIR=~/.openclaw-v2`), **OpenClaw 2026.4.24** installed via npm global still creates **two parallel** `plugin-runtime-deps` install roots and intermittently hits **`ENOTEMPTY`** when rebuilding the `plugin-sdk` alias directory.

The gateway can run and channels can connect, but the CLI / bundled-channel registration / upgrade path remains unsafe.

Related issues **#72528**, **#72956**, **#72521**, **#71812**, and **#74818** are all closed. #72528 was closed as fixed on `main`, but our released npm `2026.4.24` deployment still shows the dual-tree + ENOTEMPTY symptom family. We are requesting confirmation of the released version that contains the fix and the recommended migration steps before upgrading.

---

### Environment

| Item | Value |
|---|---|
| Host OS | macOS 26.5, arm64 |
| OpenClaw CLI | 2026.4.24, npm global |
| OpenClaw.app | 2026.5.20 installed, but not used by gateway LaunchAgents |
| Runtime authority | npm global CLI |
| Profile | v2 |
| Gateway | `:18790`, LaunchAgent uses npm-global `dist/index.js` |

---

### Dual runtime tree

Active roots under `~/.openclaw-v2/plugin-runtime-deps/`:

```text
openclaw-2026.4.24-da6bdffc3d96/
openclaw-unknown-b06c60528ba3/

### Alternatives considered

_No response_

### Impact

### Summary

On macOS with profile-scoped state (`OPENCLAW_STATE_DIR=~/.openclaw-v2`), **OpenClaw 2026.4.24** installed via npm global still creates **two parallel** `plugin-runtime-deps` install roots and intermittently hits **`ENOTEMPTY`** when rebuilding the `plugin-sdk` alias directory.

The gateway can run and channels can connect, but the CLI / bundled-channel registration / upgrade path remains unsafe.

Related issues **#72528**, **#72956**, **#72521**, **#71812**, and **#74818** are all closed. #72528 was closed as fixed on `main`, but our released npm `2026.4.24` deployment still shows the dual-tree + ENOTEMPTY symptom family. We are requesting confirmation of the released version that contains the fix and the recommended migration steps before upgrading.

---

### Environment

| Item | Value |
|---|---|
| Host OS | macOS 26.5, arm64 |
| OpenClaw CLI | 2026.4.24, npm global |
| OpenClaw.app | 2026.5.20 installed, but not used by gateway LaunchAgents |
| Runtime authority | npm global CLI |
| Profile | v2 |
| Gateway | `:18790`, LaunchAgent uses npm-global `dist/index.js` |

---

### Dual runtime tree

Active roots under `~/.openclaw-v2/plugin-runtime-deps/`:

```text
openclaw-2026.4.24-da6bdffc3d96/
openclaw-unknown-b06c60528ba3/

### Evidence/examples

_No response_

### Additional information

_No response_

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Feature]: 2026.4.24 v2 profile creates dual plugin-runtime-deps trees and ENOTEMPTY on plugin-sdk alias setup; upgrade path blocked despite gateway healthy