Chrome Relay 显示未连接？用 CLI 对照法定位 401 token 头缺失

问题/场景：Chrome 扩展已点亮 ON，但 agent 的 browser 工具仍报 no tab connected。前置条件：已启用 Chrome relay 并能运行 OpenClaw CLI。实施步骤：先用 CLI 验证 relay 正常→再用工具调用复现空 tabs→对照日志锁定 401 与 relay token 头缺失→临时改为 CLI/host 侧浏览器流程。关键命令：openclaw browser --browser-profile chrome tabs。验证：CLI 能列出 tab 且 agent 侧问题可稳定复现。风险：这是版本缺陷，修复前不应把关键流程仅依赖该链路。

GITHUBDiscovered 2026-02-19Author accek

Prerequisites

OpenClaw browser relay is enabled and a Chrome tab is attached via Browser Relay icon (badge ON).
You have shell access to run OpenClaw CLI and can read gateway logs.

Steps

Run CLI baseline check: openclaw browser --browser-profile chrome tabs to confirm relay actually sees the connected tab.
From agent/browser tool, call tabs and snapshot with profile=chrome; record empty list or no tab connected error.
Correlate timestamps in relay logs; if you see HTTP 401 and missing relay token header, classify as issue #20457 path.
Use workaround for production tasks: run browser actions from CLI/host process or switch to non-relay profile until patch lands.

Commands

openclaw browser --browser-profile chrome tabs

openclaw gateway status

openclaw gateway restart

Verify

CLI consistently lists connected Chrome tabs while agent tool path fails with relay-auth symptoms, proving a tool/relay auth gap rather than user attach error.

Caveats

This entry is based on an open bug report; exact fix version must be confirmed from release notes（需验证）.
Do not expose relay tokens while debugging (screenshots/log sharing).

Source attribution

This tip is aggregated from community/public sources and preserved with attribution.

Open original source ↗

Visit original post