Summary

Fixes #16423 - Dashboard now uses localhost URL to avoid browser secure context errors

Problem

When gateway.bind="lan", the openclaw dashboard command generated URLs with LAN IP (e.g., http://192.168.31.137:18789/). Browsers rejected WebSocket connections to these URLs due to secure context policy requiring "HTTPS or localhost."

Solution

Force dashboard command to always use localhost (127.0.0.1) regardless of gateway bind configuration.

Changes

Modified src/commands/dashboard.ts:

• Force bind: "loopback" in resolveControlUiLinks() call
• Removed unused bind variable
• Added explanatory comment

Rationale

• Dashboard is local-only: Always accessed from the same machine as gateway
• Gateway accepts both: When bound to 0.0.0.0 or LAN, still accepts localhost connections
• Browser security: Localhost satisfies secure context without requiring HTTPS
• No functionality loss: All features work identically via localhost

Before

const bind = cfg.gateway?.bind ?? "loopback";
const links = resolveControlUiLinks({
  port,
  bind,  // Uses LAN IP when bind="lan"
  customBindHost,
  basePath,
});

After

// Dashboard always uses localhost regardless of bind mode
const links = resolveControlUiLinks({
  port,
  bind: "loopback",  // Always localhost
  customBindHost,
  basePath,
});

Testing

• ✅ Lint check passed
• ✅ Format check passed

🤖 Generated with Claude Code

Greptile Overview

Greptile Summary

Forces dashboard command to always use localhost (127.0.0.1) instead of respecting gateway.bind configuration. This prevents browser secure context errors when gateway is bound to LAN IP addresses, since browsers require HTTPS or localhost for WebSocket connections. The change is safe because:

• The dashboard is always accessed locally from the same machine as the gateway
• Gateway accepts localhost connections even when bound to 0.0.0.0 or LAN addresses
• The status command (src/commands/status.command.ts:199-206) still respects the bind configuration for display purposes
• Tests verify the behavior expects bind: "loopback" (src/commands/dashboard.e2e.test.ts:80-85)

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The change is minimal, well-justified, and correctly addresses a browser security policy issue. The hardcoded bind: "loopback" is appropriate for dashboard command since it's always accessed locally. Tests confirm the expected behavior, and the change doesn't affect other parts of the system (status command still shows actual bind configuration).
• No files require special attention

_{Last reviewed commit: dda36bb}