7.5k★by dgriffin831
claude-chrome – OpenClaw Skill
claude-chrome is an OpenClaw Skills integration for coding workflows. Use Claude Code with Chrome browser extension for web browsing and automation tasks. Alternative to OpenClaw's built-in browser tools.
Skill Snapshot
| 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. OpenClaw Skills integration. |
| owner | dgriffin831 |
| repository | dgriffin831/claude-chrome |
| language | Markdown |
| license | MIT |
| topics | |
| security | L1 |
| install | openclaw add @dgriffin831/claude-chrome |
| last updated | Feb 7, 2026 |
Maintainer

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
- Claude Code installed on the node (e.g.
/opt/homebrew/bin/claude) - Claude Code Chrome extension installed and enabled in Chrome
- 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-permissionsfor automated runs - Always use
-p/--printfor non-interactive output - Always use
bash -lcfor 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_fetchinstead (faster, no domain permissions needed)
No README available.
Permissions & Security
Security level L1: Low-risk skills with minimal permissions. Review inputs and outputs before running in production.
Requirements
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
FAQ
How do I install claude-chrome?
Run openclaw add @dgriffin831/claude-chrome in your terminal. This installs claude-chrome into your OpenClaw Skills catalog.
Does this skill run locally or in the cloud?
OpenClaw Skills execute locally by default. Review the SKILL.md and permissions before running any skill.
Where can I verify the source code?
The source repository is available at https://github.com/openclaw/skills/tree/main/skills/dgriffin831/claude-chrome. Review commits and README documentation before installing.
