fix: preserve local OpenClaw shim in dashboard launcher - #58
Open
jontsai wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary\n- move final PATH setup after nvm loads in scripts/run-server.sh\n- prefer ~/.local/bin and ~/bin so the dashboard uses the source-installed OpenClaw shim instead of an nvm global CLI\n\n## Test\n- npm test\n- verified command -v openclaw resolves to /Users/jontsai/.local/bin/openclaw after the launcher PATH setup\n\n## Context\nHeartbeat found the dashboard reachable only after a manual start, while async dashboard widgets logged config validation failures from the nvm global OpenClaw CLI. This launcher PATH ordering keeps the runtime on the intended local shim.