Global symlink install fix: verify Control UI assets load under nvm/fnm/Homebrew

Scenario: globally installed OpenClaw via symlinked Node managers may miss Control UI assets. Upgrade and validate dashboard asset resolution from a symlinked binary path.

GITHUBDiscovered 2026-02-14Author @aynorica + @gumadeiras

Prerequisites

OpenClaw is installed globally via symlinked runtime (nvm/fnm/Homebrew-like path).
You can access local Control UI and compare before/after behavior.

Steps

Upgrade to a build containing PR #14919 and restart gateway.
Open Control UI through the normal local entrypoint and observe static asset loading.
Hard-refresh browser cache and re-open to ensure no stale cache masks missing assets.
Test one interactive view (sessions/agents panel) to confirm JS bundle actually executes.

Commands

openclaw gateway status

openclaw gateway restart

openclaw logs --local-time

Verify

Control UI loads without missing-asset errors and interactive panels function correctly from symlinked install path.

Caveats

Browser cache and reverse-proxy cache can produce false positives; test in private window too.
If binary path keeps changing between shells, reproducibility may still vary（需验证）.

Source attribution

This tip is aggregated from community/public sources and preserved with attribution.

Open original source ↗

Visit original post