browser-harness

Control live Chrome browsers over CDP via a Rust daemon and CLI.

9|Updated Apr 23, 2026

Search Tags:#cli #rust #cdp #wasm #daemon #browser-harness

Ready to run

npx skills add https://github.com/yangchuansheng/browser-harness-rust --skill browser-harness-yangchuansheng

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: browser-harness
Source: https://github.com/yangchuansheng/browser-harness-rust/tree/main
Command: npx skills add https://github.com/yangchuansheng/browser-harness-rust --skill browser-harness-yangchuansheng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The Browser Harness Skill provides a durable, Rust-native runtime that owns the browser session, exposes a stable CLI, and coordinates domain-specific knowledge with site-specific guests to drive real browsers over CDP.

Core Features & Use Cases

Durable daemon: a Rust-based runtime that owns the browser connection and session state, exposing a small, typed surface for automation.
Domain-aware workflows: site-specific knowledge under domains/ is loaded through SKILL.md and optional guests to implement repeatable tasks.
Local and remote operation: attach to a locally running Chrome or provision Browser Use cloud browsers with a consistent, typed protocol.

Quick Start

Launch the harness by installing the Rust binaries, starting the daemon, and then issuing browser-harness commands against a live Chrome.

Frequently Asked Questions about browser-harness

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

FAQPage Schema

How do I automate a live Chrome session over CDP using Rust?▼

Browser automation over CDP is handled by a Rust-based daemon that owns the browser connection, runs a typed runner, and exposes a CLI to execute goto, waits, and js commands against a live local Chrome session.

Can I run browser automation tasks in the cloud without a local Chrome instance?▼

Yes, browser automation can provision Browser Use cloud browsers by providing a BROWSER_USE_API_KEY, allowing the Rust daemon to control remote sessions with the same typed protocol used for local Chrome.

What is a Rust-native daemon for browser control and how does it work?▼

A Rust-native daemon is a durable runtime that owns the browser session state and exposes a small, typed surface over CDP, coordinating domain-specific knowledge to drive real browsers reliably.

Do I need a Rust toolchain to use CDP for end-to-end browser automation?▼

Yes, a Rust toolchain is required to install the binaries and start the daemon that manages the CDP connection and executes the typed runner commands for end-to-end browser automation.

How do I coordinate domain-specific workflows during a browser automation session?▼

Domain-specific workflows are coordinated by loading site-specific knowledge through SKILL.md and optional guests, enabling the Rust daemon to execute repeatable tasks over CDP.