← Claude plugins
CLAUDE PLUGIN

browser-harness

Browser Use v0.1.0

Open-source browser agent driven via CDP — direct browser control, 79K stars, YC W25. browser-harness gives Claude Code direct, low-level control of a real Chrome browser via the Chrome DevTools P...

Create a free account to save this plugin.

From the developer

License

MIT

Works with

Claude Code

Description

From the marketplace listing

Open-source browser agent driven via CDP — direct browser control, 79K stars, YC W25. browser-harness gives Claude Code direct, low-level control of a real Chrome browser via the Chrome DevTools Protocol. Coordinate-level clicks pass through iframes, shadow DOM, and cross-origin frames at the compositor level — no selector hunting, no Playwright wrappers. Connects to a long-running Browser Use Cloud or local browser session, so logins persist across runs. Highlights: - Screenshot-first workflow: capture → read pixel → click_at_xy → re-capture to verify - Bulk HTTP fetch helper for static pages (no browser overhead) - Raw CDP escape hatch for anything helpers don’t cover - Interaction skills for dialogs, dropdowns, iframes, shadow DOM, file uploads, cross-origin frames - Remote browsers via Browser Use Cloud — share a live URL with a human when login/CAPTCHA blocks the agent

What changed

No changes recorded yet. Follow this plugin to keep track of future changes.

Keywords

Files & skills

browser-harness · catalog manifest

Saved declaration

{}
browser-harness · catalog manifest

Saved declaration

{
  "name": "browser-harness",
  "source": {
    "sha": "f5eaf904b221dde0118eba1496961c3dc20fda88",
    "url": "https://github.com/browser-use/browser-harness.git",
    "source": "url"
  },
  "homepage": "https://browser-use.com",
  "description": "Open-source browser agent driven via CDP — direct browser control, 79K stars, YC W25.\n\nbrowser-harness gives Claude Code direct, low-level control of a real Chrome browser via the Chrome DevTools Protocol. Coordinate-level clicks pass through iframes, shadow DOM, and cross-origin frames at the compositor level — no selector hunting, no Playwright wrappers. Connects to a long-running Browser Use Cloud or local browser session, so logins persist across runs.\n\nHighlights:\n- Screenshot-first workflow: capture → read pixel → click_at_xy → re-capture to verify\n- Bulk HTTP fetch helper for static pages (no browser overhead)\n- Raw CDP escape hatch for anything helpers don’t cover\n- Interaction skills for dialogs, dropdowns, iframes, shadow DOM, file uploads, cross-origin frames\n- Remote browsers via Browser Use Cloud — share a live URL with a human when login/CAPTCHA blocks the agent"
}
browser-harness · catalog manifest

Saved declaration

{
  "name": "browser-harness",
  "author": {
    "url": "https://browser-use.com",
    "name": "Browser Use"
  },
  "license": "MIT",
  "version": "0.1.0",
  "homepage": "https://github.com/browser-use/browser-harness",
  "keywords": [
    "browser",
    "automation",
    "cdp",
    "chrome",
    "scraping",
    "screenshot",
    "browser-use",
    "browser-harness"
  ],
  "repository": "https://github.com/browser-use/browser-harness",
  "description": "Direct browser control via CDP. Drives the user's real Chrome (or a Browser Use cloud browser) with coordinate clicks, screenshots, and Python helpers — no selector hunting. Requires the one-time `browser-harness` CLI install (see the skill's references/install.md)."
}

plugin.json observed Nov 6, 2026 · 10:41 UTC. Manifest source ↗

Catalog declarations and available plugin.json metadata are saved. Referenced skills and executable source files are not downloaded or tested. Missing components in a manifest do not prove that the plugin has none.

Installation instructions

Community

/plugin marketplace add anthropics/claude-plugins-community
/plugin install browser-harness@claude-community

Claude Code installation documentation

Technical details
Sources
Community
First seen
Oct 3, 2026 · 22:13 UTC
Last seen
Nov 7, 2026 · 06:00 UTC
Latest observed change
Oct 3, 2026 · 22:13 UTC
Collection status
Listed
Reported installs
Not provided

Installation counts are source-reported, not independently verified active users. Observation dates are not release dates.

Download plugin data (JSON)

Plugin history: freshly prepared. Prepared . Refreshed when catalog data changes or after 6 hours. Your account and Follow status are live.