Chrome Relay 卡顿别先怪模型：按“浏览器链路/状态/模型”三层拆分排障

问题/场景：社区反馈“模型回答正常但 Chrome Relay 浏览器体验差”，容易误判为模型问题。前置条件：已启用 Browser Relay（Chrome 扩展）并可访问 OpenClaw browser 状态工具。实施步骤：先验证扩展附着与 tab 连接，再检查 targetId/ref 传递稳定性，最后才调整模型。关键命令：browser status/tabs/snapshot/act。验证：同一模型下 relay 成功率提升，失败集中在可定位链路而非随机。风险与边界：帖子为讨论线索，具体模型优选需结合你的任务类型实测。来源：Reddit 讨论帖 1rc2xh2 + OpenClaw 浏览器文档交叉整理。

REDDITDiscovered 2026-02-23Author u/Feel-Groundbreaking

Prerequisites

Chrome extension relay is installed and the target tab can be attached (badge ON).
You can run browser tool calls (`status`, `tabs`, `snapshot`, `act`) for diagnostics.

Steps

Check relay connection first: ensure extension tab is attached and visible in `browser tabs`.
Capture snapshot and keep the same `targetId`; run actions using refs from that exact snapshot.
Only after transport/ref stability is confirmed, test model changes for instruction quality differences.
Record failure class (attach failure / ref mismatch / model reasoning) for each run.

Commands

browser status --profile chrome

browser tabs --profile chrome

browser snapshot --profile chrome --refs aria

Verify

Most failures become reproducible transport/ref issues; successful runs no longer depend on random model retries.

Caveats

Discussion thread does not provide controlled benchmark data; model rankings remain environment-specific（需验证）.
If no tab is attached, model changes cannot fix relay failures; resolve attachment first.

Source attribution

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

Open original source ↗

Visit original post