openclaw - 💡(How to fix) Fix [Bug]: openclaw dashboard fails to auto-launch browser in v2026.4.23 [1 comments, 2 participants]

Bug type

Regression (worked before, now fails)

Beta release blocker

Yes

Summary

The openclaw dashboard command in version 2026.4.23 fails to trigger the automatic launch of the system's default browser despite successfully outputting the dashboard URL.

Steps to reproduce

Environment: Windows (PowerShell). Version: OpenClaw 2026.4.23 (a979721). Action: Execute openclaw dashboard. Observation: Verify the terminal outputs "Opened in your browser" while no browser window is actually launched. Implementation Details: I have developed and verified a hotfix that addresses this silent failure on Windows environments. The root cause was identified as an improper invocation of the start command on the win32 platform, where certain URL characters (such as & or # in tokens) were not correctly escaped, causing the shell process to exit prematurely without launching the UI. Hotfix Repository: https://github.com/xinhanliu0216-droid/openclaw-force-open-url Technical Changes: Added platform-specific logic to detect win32. Implemented robust URL character escaping for the Windows shell. Ensured the sub-process properly inherits the environment to trigger the default system browser. Verification: System: Windows 10/11 (PowerShell & CMD). Result: Executing openclaw dashboard now consistently launches the default browser and navigates to the authenticated URL.

Expected behavior

Based on the behavior of version 2026.4.9, the openclaw dashboard command is expected to automatically launch the default system browser and navigate to the generated URL upon execution.

Actual behavior

The terminal output explicitly states "Opened in your browser. Keep that tab to control OpenClaw" (Evidence: openclaw.cmd dashboard logs) despite the browser failing to launch in the system environment. No explicit error messages or failure codes are visible in the command-line interface.

OpenClaw version

2026.4.23

Operating system

Windows11

Install method

npm global

Model

minimax

Provider / routing chain

CLI -> Local Gateway -> Browser

Additional provider/model setup details

Effective Provider/Environment Context: 1.Environment: Global npm installation on Windows 11/10 (Node.js v24.13.0). 2.Execution Path: CLI entry point located in AppData\Roaming\npm\node_modules\openclaw. 3.Configuration Context: The dashboard command initializes a local gateway (defaulting to 127.0.0.1:18789) and attempts to route the initial user session to the system browser via an internal browser-open utility. 4.Auth-Profile Interaction: The failure occurs before any auth-profile or agent-specific routing (e.g., Feishu/Lark, Telegram) can be managed via the UI, as the initial routing to the browser environment is blocked. 5.Routing Chain: openclaw CLI -> child_process (internal module) -> Windows Shell (failed invocation).

Logs, screenshots, and evidence

# Command execution on Windows 11
$ openclaw dashboard
[2026-04-25] INFO: Starting OpenClaw Gateway...
[2026-04-25] INFO: Gateway listening on http://127.0.0.1:18789
[2026-04-25] INFO: Loading configuration from C:\Users\<USER>\.openclaw\config.yaml
Opened in your browser. Keep that tab to control OpenClaw.

# Observation: 
# The process hangs as expected to keep the gateway alive, 
# but no browser window or tab is opened. 
# Manual navigation to http://127.0.0.1:18789 works perfectly.

Impact and severity

·Affected users/systems/channels: Windows users (specifically those using PowerShell/CMD) running OpenClaw version 2026.4.23 (a979721). ·Severity: Annoying. It does not block the core functionality as the service starts and the URL is provided, but it breaks the expected automation and ·misleads the user with a false success message. ·Frequency: Always. The provided logs show the failure is consistent across consecutive attempts on the affected version. ·Consequence: Failed automated onboarding. Users must manually copy and paste the URL into a browser to access the dashboard, despite the CLI stating "Opened in your browser."

Additional information

Regression Information Last Known Good Version: 2026.4.9 First Known Bad Version: 2026.4.23

Additional Grounded Context Build Metadata: The affected binary identifies as build hash a979721. Execution Environment: The logs show the tool is being invoked via openclaw.cmd in a Windows PowerShell environment (C:\Users\23022>). Logical Contradiction: The CLI logic explicitly triggers a success message—"Opened in your browser. Keep that tab to control OpenClaw"—immediately after the URL and clipboard confirmation. This indicates the internal process responsible for spawning the browser returned a "success" status to the CLI, or the CLI does not verify the exit code of the browser-opening sub-process.