Summary

In Mission Control, links to OpenClaw documentation (e.g. "Workspace concept", "Agent workspace", and various inline [link](/concepts/...) references throughout the UI) navigate to 127.0.0.1:4317/... instead of https://docs.openclaw.ai/.... Port 4317 has no docs server running, so the browser shows a generic 404 ("This page could not be found").

Environment

• Version: OpenClaw 2026.5.27 (commit 27ae826)
• Platform: macOS 26.5 (Build 25F71), Apple Silicon
• Gateway: running on 127.0.0.1:18789, loopback
• Surface: Mission Control web UI in desktop browser

Steps to reproduce

1. Open Mission Control at http://127.0.0.1:18789/
2. Find any link in Mission Control that points at a docs path — e.g. on a project view, in workspace markdown that includes [Workspace concept](/concepts/agent-workspace), or sidebar concept links
3. Click the link

Expected

The link opens the relevant docs page on https://docs.openclaw.ai/concepts/agent-workspace (in a new tab is fine).

Actual

Browser navigates to http://127.0.0.1:4317/concepts/agent-workspace and renders a 404 page. The host:port has no service listening.

Root cause guess

Doc links are treated as same-origin relative URLs and resolved against the current dev-server origin (which happens to land on 4317 in some build configs, or the bundled UI hardcoded 127.0.0.1:4317). The intended target is the public docs host docs.openclaw.ai.

Workaround

Manually edit the URL in the browser bar: replace 127.0.0.1:4317 with docs.openclaw.ai and reload.

Notes

• Affects multiple doc-link types throughout Mission Control (project pages, sidebar, inline markdown).
• Distinct from Mission Control: clicking on cron job cards does nothing (no detail view) #89462 (cron card clicks dead) and the file-list-not-clickable bug — those are missing click handlers; this one is a URL rewrite issue.
• A clean fix is either to absolute-link all docs references to https://docs.openclaw.ai, or to serve the docs locally at the configured port.