openclaw - 💡(How to fix) Fix [Bug]: openclaw dashboard logs bare URL despite token auto-auth and can hang on Linux/KDE browser launch

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 OpenClaw 2026.5.12, openclaw dashboard resolves a tokenized dashboard URL internally, but logs the bare URL:

const dashboardUrl = includeTokenInUrl
  ? `${links.httpUrl}#token=${encodeURIComponent(token)}`
  : links.httpUrl;

runtime.log(`Dashboard URL: ${links.httpUrl}`);

So when browser launch does not complete and the operator manually opens the printed URL, Control UI prompts for a token even though openclaw dashboard had already resolved one.

On Linux/KDE, the normal dashboard open path also hangs after printing the first few lines. In this environment, openclaw dashboard --no-open and openclaw dashboard both needed external timeout before a local hotfix.

Root Cause

On OpenClaw 2026.5.12, openclaw dashboard resolves a tokenized dashboard URL internally, but logs the bare URL:

const dashboardUrl = includeTokenInUrl
  ? `${links.httpUrl}#token=${encodeURIComponent(token)}`
  : links.httpUrl;

runtime.log(`Dashboard URL: ${links.httpUrl}`);

So when browser launch does not complete and the operator manually opens the printed URL, Control UI prompts for a token even though openclaw dashboard had already resolved one.

On Linux/KDE, the normal dashboard open path also hangs after printing the first few lines. In this environment, openclaw dashboard --no-open and openclaw dashboard both needed external timeout before a local hotfix.

Fix Action

Fix / Workaround

On Linux/KDE, the normal dashboard open path also hangs after printing the first few lines. In this environment, openclaw dashboard --no-open and openclaw dashboard both needed external timeout before a local hotfix.

Observed before local patch:

A local hotfix that resolved the operator-facing issue changed the log line to print dashboardUrl instead of links.httpUrl, suppressed the stale manual-token warning once the tokenized URL is printed, and used a detached browser launch for the dashboard opener on Linux.

Code Example

const dashboardUrl = includeTokenInUrl
  ? `${links.httpUrl}#token=${encodeURIComponent(token)}`
  : links.httpUrl;

runtime.log(`Dashboard URL: ${links.httpUrl}`);

---

http://127.0.0.1:18789/#token=<redacted>

---

Dashboard URL: http://127.0.0.1:18789/
Token auto-auth included in browser/clipboard URL.
Copy to clipboard unavailable.
Token auto-auth not delivered. Append your gateway token (from OPENCLAW_GATEWAY_TOKEN or gateway.auth.token) as a URL fragment with key `token` to authenticate.

---

Dashboard URL: http://127.0.0.1:18789/
Token auto-auth included in browser/clipboard URL.
Copy to clipboard unavailable.

---

/home/phil/.npm-global/lib/node_modules/openclaw

---

runtime.log(`Dashboard URL: ${links.httpUrl}`);
RAW_BUFFERClick to expand / collapse

Bug type

Regression / behavior bug

Summary

On OpenClaw 2026.5.12, openclaw dashboard resolves a tokenized dashboard URL internally, but logs the bare URL:

const dashboardUrl = includeTokenInUrl
  ? `${links.httpUrl}#token=${encodeURIComponent(token)}`
  : links.httpUrl;

runtime.log(`Dashboard URL: ${links.httpUrl}`);

So when browser launch does not complete and the operator manually opens the printed URL, Control UI prompts for a token even though openclaw dashboard had already resolved one.

On Linux/KDE, the normal dashboard open path also hangs after printing the first few lines. In this environment, openclaw dashboard --no-open and openclaw dashboard both needed external timeout before a local hotfix.

Steps to reproduce

Environment where gateway auth is token-based and gateway.controlUi.allowInsecureAuth is false.

  1. Run openclaw dashboard --no-open.
  2. Observe the command prints Dashboard URL: http://127.0.0.1:18789/ even though it also says token auto-auth is included.
  3. Manually open the printed URL.
  4. Control UI prompts for/presents missing token auth instead of auto-authing.
  5. On Linux/KDE, run openclaw dashboard and observe the command can hang after clipboard/browser handling.

Expected behavior

When includeTokenInUrl is true, the visible fallback URL should be the same tokenized URL used for browser launch and clipboard:

http://127.0.0.1:18789/#token=<redacted>

The command should also exit cleanly after launching or failing to launch the browser, instead of hanging.

Actual behavior

openclaw dashboard --no-open prints the bare URL and then advises manual auth/token appending.

Observed before local patch:

Dashboard URL: http://127.0.0.1:18789/
Token auto-auth included in browser/clipboard URL.
Copy to clipboard unavailable.
Token auto-auth not delivered. Append your gateway token (from OPENCLAW_GATEWAY_TOKEN or gateway.auth.token) as a URL fragment with key `token` to authenticate.

The normal openclaw dashboard path similarly prints the bare URL and can hang after:

Dashboard URL: http://127.0.0.1:18789/
Token auto-auth included in browser/clipboard URL.
Copy to clipboard unavailable.

OpenClaw version

2026.5.12 (f066dd2)

Operating system

Kubuntu / KDE Plasma 5, Linux

Install method

npm global

Additional context

Installed package path in this environment:

/home/phil/.npm-global/lib/node_modules/openclaw

Source inspection of current upstream src/commands/dashboard.ts still shows the bare URL being logged:

runtime.log(`Dashboard URL: ${links.httpUrl}`);

A local hotfix that resolved the operator-facing issue changed the log line to print dashboardUrl instead of links.httpUrl, suppressed the stale manual-token warning once the tokenized URL is printed, and used a detached browser launch for the dashboard opener on Linux.

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…

FAQ

Expected behavior

When includeTokenInUrl is true, the visible fallback URL should be the same tokenized URL used for browser launch and clipboard:

http://127.0.0.1:18789/#token=<redacted>

The command should also exit cleanly after launching or failing to launch the browser, instead of hanging.

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 [Bug]: openclaw dashboard logs bare URL despite token auto-auth and can hang on Linux/KDE browser launch