Problem
After running ./install.sh, the onboarding wizard completes and prints a summary including the dashboard URL:
Dashboard http://localhost:18789/
However, the dashboard requires a gateway token to authenticate. The token is never shown to the user, creating a circular experience — you're told to visit the dashboard but can't log in.
Current workaround
SSH into the sandbox and manually retrieve the token:
ssh openshell-nemoclaw "openclaw dashboard --no-open"
This outputs a URL like:
http://127.0.0.1:18789/#token=961dc4bc7ae8237e6835f45863ee8da482aaec0efa9766f1
Expected behavior
The printDashboard() function in bin/lib/onboard.js (line 438) should retrieve the token from the sandbox and include it in the dashboard URL shown to the user at the end of onboarding.
Suggested fix
After sandbox creation completes, run openclaw dashboard --no-open inside the sandbox via SSH, parse the #token=... from the output, and append it to the dashboard URL in the summary output.
🤖 Generated with Claude Code
Problem
After running
./install.sh, the onboarding wizard completes and prints a summary including the dashboard URL:However, the dashboard requires a gateway token to authenticate. The token is never shown to the user, creating a circular experience — you're told to visit the dashboard but can't log in.
Current workaround
SSH into the sandbox and manually retrieve the token:
ssh openshell-nemoclaw "openclaw dashboard --no-open"This outputs a URL like:
Expected behavior
The
printDashboard()function inbin/lib/onboard.js(line 438) should retrieve the token from the sandbox and include it in the dashboard URL shown to the user at the end of onboarding.Suggested fix
After sandbox creation completes, run
openclaw dashboard --no-openinside the sandbox via SSH, parse the#token=...from the output, and append it to the dashboard URL in the summary output.🤖 Generated with Claude Code