Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Developer Tools
Stable Browser
Set up reliable browser automation using Chrome DevTools Protocol (CDP) instead of the flaky browser extension relay. Use when browser relay keeps disconnect...
skill openclawclawhub Free
Set up reliable browser automation using Chrome DevTools Protocol (CDP) instead of the flaky browser extension relay. Use when browser relay keeps disconnect...
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md, references/manual-setup.md, scripts/setup-cdp.sh
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
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.
Upgrade existing
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.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.0
Provenance
- Publisher
- jarvis563
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Stable Browser
Replace the unreliable browser extension relay with a direct Chrome DevTools Protocol connection.
The Problem
The OpenClaw browser extension relay (profile="chrome") frequently breaks: WebSocket 403 errors Port confusion (gateway port vs relay port) Dropped connections mid-automation "Can't reach browser control service" errors Badge/tab attachment confusion
The Fix: Chrome CDP
Launch Chrome with a debug port and connect directly. No extension needed.
Quick Setup
Run the setup script to configure everything: bash scripts/setup-cdp.sh This will: Create a dedicated Chrome profile at ~/.chrome-debug-profile Add browser.cdpUrl to your OpenClaw config Create a LaunchAgent (macOS) so Chrome starts on login Verify the connection works
Manual Setup
If you prefer to set things up manually, see references/manual-setup.md.
Usage
After setup, always use profile="openclaw" (not profile="chrome"): browser(action="snapshot", profile="openclaw") browser(action="navigate", profile="openclaw", targetUrl="https://example.com") browser(action="screenshot", profile="openclaw")
Key Differences from Extension Relay
FeatureExtension RelayCDP DirectStabilityFrequent disconnectsRock solidSetupInstall extension + attach tabOne-time scriptAuth/CookiesShares your main ChromeDedicated profileSpeedExtra hop through extensionDirect protocolHeadlessNoOptional (--headless=new)
Dedicated Profile
The CDP browser uses ~/.chrome-debug-profile โ a separate Chrome profile. This means: Log into sites once, stays logged in Your main Chrome is untouched No extension conflicts Survives Chrome updates
Tips
First run: Log into any sites you need (Google, GitHub, X, LinkedIn, etc.) Multiple tabs: CDP manages all tabs โ use targetId to pin a specific tab Headless mode: Add --headless=new to the launch command for invisible operation Port conflict: If port 9222 is taken, change it in both the launch command and config Restart Chrome: pkill -f 'remote-debugging-port=9222' && sleep 1 && bash scripts/setup-cdp.sh
Troubleshooting
"Can't reach browser": Chrome isn't running with debug port. Run setup-cdp.sh or launch manually Port 9222 in use: Another Chrome or process grabbed it. Kill it: lsof -i :9222 Stale session: Chrome crashed. Kill and restart: pkill -f chrome-debug-profile Profile corruption: Delete ~/.chrome-debug-profile and re-run setup
Category context
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
2 Docs1 Scripts
- SKILL.md
- references/manual-setup.md
- scripts/setup-cdp.sh