browser-harness

Automates browser control via Chrome DevTools Protocol for web interaction and testing.

1|Updated May 25, 2020
One-click install
npx skills add https://github.com/titaneric/dotfiles --skill browser-harness-titaneric
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-harness
Source: https://github.com/titaneric/dotfiles/tree/main/dot_agents/skills/browser-harness
Command: npx skills add https://github.com/titaneric/dotfiles --skill browser-harness-titaneric

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually driving a browser for automation, scraping, or testing tasks is slow and error-prone. This Skill gives an AI agent direct control of a local Chrome instance or isolated cloud browsers through the Chrome DevTools Protocol (CDP), so web tasks can be executed programmatically. ## Core Features & Use Cases - Direct CDP Browser Control: Navigate pages, click by coordinates, run JavaScript, capture screenshots, and inspect the DOM through pre-imported helper functions. - Local and Remote Browsers: Attach to a running local Chrome via remote debugging, or spin up isolated Browser Use cloud browsers for parallel tasks and captcha-prone scraping. - Interaction Skill References: Consult dedicated guides for tricky mechanics like iframes, shadow DOM, downloads, drag-and-drop, and network requests. - Use Case: Ask the agent to log into a dashboard, navigate to a reports page, screenshot the visible state, and extract table data with JavaScript — all without writing a custom Playwright script. ## Quick Start Use browser-harness to open example.com in a new tab and print the current page info.

Frequently Asked Questions about browser-harness

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Chrome with the DevTools Protocol?

Run the browser-harness CLI with a heredoc script calling pre-imported helpers like new_tab(url), click_at_xy(x, y), and js(...) for DOM work. The daemon attaches to your running Chrome instance through its CDP endpoint automatically.

How do I run parallel browser automation tasks?

Use Browser Use cloud browsers, one per task, started with start_remote_daemon(name) and targeted via the BU_NAME environment variable. Local Chrome is a single shared browser, so parallel tasks would fight over tabs and focus.

Why can't browser-harness connect to my local Chrome?

Run browser-harness --doctor to diagnose the connection. Usually Chrome remote debugging is not enabled; open chrome://inspect/#remote-debugging, allow remote debugging, and approve any permission popup, then retry.

Can browser automation avoid captchas and bot blocking?

Cloud browsers from Browser Use run with clean managed IPs and stealth settings, reducing captcha walls and rate limits on bot-sensitive sites. They also keep your own IP and local browser out of the scraping activity.

What should I do when a site shows a login wall during automation?

Stop and ask the user before proceeding past login walls. The exception is SSO when Chrome is already signed in; still stop for passwords, MFA, consent screens, or ambiguous account choices.