#Mission Control
1 messages · Page 1 of 1 (latest)
“Mission Control” is likely what folks mean by the OpenClaw Dashboard / Control UI: the browser interface for chatting with your agent, viewing sessions/logs, editing config, cron jobs, tools, nodes, etc.
Docs: https://docs.openclaw.ai/web/control-ui
Dashboard docs: https://docs.openclaw.ai/web/dashboard
It usually doesn’t need a separate “enable” step — it’s served by the Gateway.
Step 1: please run this and paste the output:
openclaw --version
After that I’ll give you Step 2 based on your version. 🦐
OpenClaw 2026.4.23 (a979721)
WLS2
Thanks — 2026.4.23 on WSL2 is fine.
Mission Control = the browser Dashboard / Control UI. It’s enabled by default when the Gateway is running.
Step 2: check whether your Gateway is running
In your WSL2 terminal, run:
openclaw gateway status
Paste the output here, and I’ll give you the next step.
Docs for reference: https://docs.openclaw.ai/web/dashboard
Can we talk in DM?
openclaw pairing approve discord 6VBGT87C
Let’s keep setup support in this help thread so others can find it later.
That command needs to be run in your own terminal on the machine running OpenClaw, not pasted here:
openclaw pairing approve discord 6VBGT87C
Only run it if you initiated the Discord DM pairing and recognize the request. Pairing codes expire after about 1 hour.
Before we go further, please paste:
openclaw --version
I wanna DM you directly so my sensative details won't be here. This is the pairing code from your DM
I get the privacy concern — please don’t post tokens, config files, or full logs with secrets here.
I can’t approve DM pairing from inside the public help thread myself. DM access has to be approved by the OpenClaw owner/admin for this bot.
For now, safest path: paste only redacted details here, e.g.:
openclaw --version
And for logs/config, replace secrets like:
token: REDACTED
apiKey: REDACTED
Then we can do the Mission Control setup one step at a time without exposing anything sensitive.
Alright