360 Secure SkillHub
360 安全技能中心

Claude Chrome

该 Skill 说明如何在具备桌面环境的节点上，借助 Claude Code 的 --chrome 集成驱动 Chrome 完成浏览、点击、填表与内容读取；通过 nodes.run 调用 claude CLI，需先确认原生宿主进程，并给出超时与性能基准。它是 OpenClaw 内置浏览器工具的替代方案。

dgriffin831
dgriffin831
热度 73.70
最近更新 2026-05-18 11:56:27
分类：自动化依赖：联网浏览搜索 / 代码执行应用场景：自动化脚本 / 工作流

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add claude-chrome
Metadata
name
claude-chrome
description
Use Claude Code with Chrome browser extension for web browsing and automation tasks. Alternative to OpenClaw's built-in browser tools.
metadata
{"clawdbot":{"emoji":"🌐","requires":{"anyBins":["claude"]}}}

Claude Chrome — Browser Automation via Claude Code

Use Claude Code's Chrome integration to browse the web, interact with pages, and automate browser tasks. This is an alternative to OpenClaw's built-in browser tools (Chrome Relay, OpenClaw profile).

Prerequisites

  1. Claude Code installed on the node (e.g. /opt/homebrew/bin/claude)
  2. Claude Code Chrome extension installed and enabled in Chrome
  3. Chrome running on the node

How It Works

Claude Code can connect to Chrome via its built-in browser extension (MCP server). When enabled, Claude Code gains browser tools — it can navigate pages, click elements, fill forms, read content, and more.

Step 1: Check if Chrome Extension is Active

Look for the native host process to confirm the Chrome extension is running:

nodes.run node=<your-node-id> command='["bash", "-lc", "pgrep -f \"claude --chrome-native-host\""]'

If this returns a PID, the Chrome extension bridge is active and ready.

Step 2: Run Claude Code with Chrome

Use nodes.run with your node to execute browser tasks:

nodes.run node=<your-node-id> commandTimeoutMs=120000 command='["bash", "-lc", "claude --dangerously-skip-permissions --chrome -p \"Go to example.com and read the headline\""]'

Flags:

  • --dangerously-skip-permissions — auto-approve all actions (required for automation)
  • --chrome — enable Chrome browser integration
  • -p / --print — non-interactive print mode (required for automated use)
  • bash -lc — login shell to ensure PATH is loaded

Timeout: See benchmarks below for guidance. Recommended defaults:

  • Simple tasks (single page read): commandTimeoutMs=30000 (30 seconds)
  • Medium complexity (multi-step navigation): commandTimeoutMs=120000 (2 minutes)
  • Complex workflows (multiple pages + summarization): commandTimeoutMs=180000 (3 minutes)

Performance Benchmarks

Task Type Example Duration Recommended Timeout
Simple Read button text on Google 13s 30s (30000ms)
Medium Wikipedia search + navigate + summarize 76s 2min (120000ms)
Complex Multi-page navigation + external links ~90s+ 3min (180000ms)

Gateway timeout note: OpenClaw's gateway has a hardcoded 10-second connection timeout. Commands will error immediately but continue running in the background. Results arrive via system messages when complete.

Limitations

  • Domain permissions: Claude Code's Chrome extension may require user approval for new domains (cannot be automated)
  • Gateway timeout: Initial connection times out at 10s, but commands continue running
  • Desktop required: Only works on nodes with a desktop environment, Chrome, and the extension active

Tips

  • Always use --dangerously-skip-permissions for automated runs
  • Always use -p / --print for non-interactive output
  • Always use bash -lc for login shell (PATH loading)
  • Be aggressive with timeouts - commands complete in background even after gateway timeout
  • Claude Code can combine coding and browsing in a single session
  • Check the native host process before attempting browser tasks
  • For simple data scraping, consider web_fetch instead (faster, no domain permissions needed)