Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ Try browser-harness in [Browser Use Cloud](https://cloud.browser-use.com/v4?utm_
Paste into Claude Code or Codex:

```text
Install or upgrade browser-harness to the latest stable version with uv using Python 3.12, register the skill from `browser-harness skill`, and connect it to my browser. Follow https://github.com/browser-use/browser-harness/blob/main/install.md if setup or connection fails.
Install or upgrade browser-harness to the latest stable version with uv using Python 3.12, register the skill body from `browser-harness skill` (skill name is `browser-use`; CLI remains `browser-harness`), and connect it to my browser. Follow https://github.com/browser-use/browser-harness/blob/main/install.md if setup or connection fails.
```

The agent will open `chrome://inspect/#remote-debugging`. Tick the checkbox so the agent can connect to your browser:
Expand Down
8 changes: 5 additions & 3 deletions install.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,13 +22,15 @@ If `page_info()` prints, stop. Setup is done.

`--python 3.12` prevents uv from selecting old releases that support older Python versions. `--upgrade --force` replaces any previous `browser-harness` tool install with the latest stable release. It does not uninstall unrelated commands such as `browser-use-Browser` or `browser-use-Terminal`.

For Claude Code or other agents: install `browser-harness`, register a skill named `browser-harness`, use `browser-harness skill` as the body, and use this trigger:
For Claude Code or other agents: install the `browser-harness` package/CLI, register a skill whose body comes from `browser-harness skill` (YAML frontmatter keeps `name: browser-use` — do not rename it to `browser-harness`), and use this trigger:

```text
Always use browser-harness for any web interaction: automation, scraping, testing, or site/app work.
Always use browser-use for any web interaction: automation, scraping, testing, or site/app work.
```

If an old user-installed `browser` or `browser-use` skill is being picked instead, remove that stale skill directory manually. Do not edit bundled/vendor plugin caches.
Package/CLI = `browser-harness`. Skill identity (frontmatter `name` + trigger) = `browser-use`. Codex may install the file under `skills/browser-harness/`; the skill name is still `browser-use`.

If an old user-installed `browser` skill, or a hand-edited skill still named `browser-harness`, is being picked instead of `browser-use`, remove that stale skill directory manually. Do not remove a correctly installed `browser-use` skill. Do not edit bundled/vendor plugin caches.

## If Chrome Blocks It

Expand Down