メニュー
Drive the machine Chrome debug browser via OpenClaw-managed MCP (chrome-devtools). Use for page navigation, snapshots, screenshots, clicks, forms, console/network inspection — not for host shell risk.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Ledger development tasks to Feishu Base via dev-task-ledger.sh. Write roots from ~/.openclaw/tasks-allowlist.json (per agent). Use on accept/confirm/close of coding/ops work; not for pure Q&A.
Allowlisted development (wezdeck (+ optional team roots in local config)) under OpenClaw: wezdeck defaults to primary master; claw worktrees when parallel/isolation needed; 团队仓 still prefers claw-*; human/Claw rails (H1/H2, C1/C2/C3), ACP access layer.
Full error closed-loop for Dex (Main): diagnose, safe self-fix, verify, report; platform Exec failed handling; escalation with options. Load when handling failures or writing failure reports.
Host shell MUST go through claw-run (gate then exec). Three layers: rules → Grok re-check → human only if still danger. Prefer claw-run over bare exec.
Multi-role adversarial code review for allowlisted repos. Agent loads this skill and runs host scripts (find → refute → sandbox repro); humans only state intent (e.g. 审一下 / 对抗审查). Use when user asks for adversarial review, task acceptance recommends review, or runtime code changed before merge.
Multi-role adversarial code review for this repo. Agent loads this skill and runs host scripts (find → refute → sandbox repro). Humans only state intent (审一下 / 对抗审查). Use when user asks for adversarial review, acceptance recommends review, or runtime code changed before merge.
| name | chrome-devtools |
| description | Drive the machine Chrome debug browser via OpenClaw-managed MCP (chrome-devtools). Use for page navigation, snapshots, screenshots, clicks, forms, console/network inspection — not for host shell risk. |
Dex (Main) can control the Windows host debug Chrome through OpenClaw MCP:
| Piece | Where |
|---|---|
| CDP endpoint | http://127.0.0.1:9222 (WezDeck helper auto-start) |
| MCP server name | chrome-devtools in local ~/.openclaw/openclaw.json → mcp.servers |
| Package | npx -y chrome-devtools-mcp@latest --browser-url=http://127.0.0.1:9222 |
This is not the same MCP session as Grok/Claude CLI; all clients share the same Chrome process on port 9222. Avoid concurrent multi-agent browser wars.
Workflow detail for launch / badge / inspect:
repo root docs/browser-debug.md.
| Trigger | Action |
|---|---|
| User: open/check URL, click, form, screenshot | MCP navigate + snapshot (not curl HTML) |
| You just changed UI (allowlisted repo) | Before 验收通过: open relevant URL/path, snapshot |
| “页面坏了 / 控制台报错 / 按钮点不了” | list pages / console / network as needed |
Coding agents on the host have their own browser/MCP/profile — this skill is for main when main is looking at the page. No bridge required.
claw-run / exec-risk — browser MCP is
separate.# CDP must answer first
curl -sS -m 3 http://127.0.0.1:9222/json/version
openclaw mcp add chrome-devtools \
--command npx \
--arg -y \
--arg chrome-devtools-mcp@latest \
--arg --browser-url=http://127.0.0.1:9222 \
--timeout 90 \
--connect-timeout 60
openclaw mcp probe chrome-devtools # expect ~29 tools
openclaw mcp reload
# or: systemctl --user restart openclaw-gateway.service
Health:
openclaw mcp list
openclaw mcp status
If probe fails: start debug Chrome (helper auto-start / Alt+b), confirm
port, then openclaw mcp reload.
curl HTML scraping when interaction matters.docs/browser-debug.md); do not invent success.Exact projected names depend on OpenClaw (often chrome-devtools__… or code-mode
MCP.chromeDevtools.*). Discover via the tool list for this session; common
capabilities include: list/navigate pages, snapshot, screenshot, click, fill,
console, network, performance.