Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Use Claude Code with Chrome browser extension for web browsing and automation tasks. Alternative to OpenClaw's built-in browser tools.
Use Claude Code with Chrome browser extension for web browsing and automation tasks. Alternative to OpenClaw's built-in browser tools.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
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).
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
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.
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.
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)
Task TypeExampleDurationRecommended TimeoutSimpleRead button text on Google13s30s (30000ms)MediumWikipedia search + navigate + summarize76s2min (120000ms)ComplexMulti-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.
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
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)
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.