fix(ux): correct token error message UI location

Update error message and docs to point to 'Overview → Gateway Access'
instead of non-existent 'Control UI settings'.

Closes #2032

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Glucksberg 2026-01-26 04:04:57 +00:00
parent 13685c86b8
commit 5924701e99
3 changed files with 4 additions and 4 deletions

View File

@ -115,7 +115,7 @@ openclaw gateway --port 18789 --verbose
```
Dashboard (local loopback): `http://127.0.0.1:18789/`
If a token is configured, paste it into the Control UI settings (stored as `connect.params.auth.token`).
If a token is configured, paste it into **Overview → Gateway Access** (stored as `connect.params.auth.token`).
⚠️ **Bun warning (WhatsApp + Telegram):** Bun has known issues with these
channels. If you use WhatsApp or Telegram, run the Gateway with **Node**.

View File

@ -255,7 +255,7 @@ describe("gateway server auth/connect", () => {
},
});
expect(res.ok).toBe(false);
expect(res.error?.message ?? "").toContain("Control UI settings");
expect(res.error?.message ?? "").toContain("Overview → Gateway Access");
ws.close();
});

View File

@ -83,7 +83,7 @@ function formatGatewayAuthFailureMessage(params: {
const isCli = isGatewayCliClient(client);
const isControlUi = client?.id === GATEWAY_CLIENT_IDS.CONTROL_UI;
const isWebchat = isWebchatClient(client);
const uiHint = "open a tokenized dashboard URL or paste token in Control UI settings";
const uiHint = "open a tokenized dashboard URL or paste token in Overview → Gateway Access";
const tokenHint = isCli
? "set gateway.remote.token to match gateway.auth.token"
: isControlUi || isWebchat
@ -92,7 +92,7 @@ function formatGatewayAuthFailureMessage(params: {
const passwordHint = isCli
? "set gateway.remote.password to match gateway.auth.password"
: isControlUi || isWebchat
? "enter the password in Control UI settings"
? "enter the password in Overview → Gateway Access"
: "provide gateway auth password";
switch (reason) {
case "token_missing":