browser-use--browser-harness
Alezander9
a2443d1d51
Cross-checked AGENTS.md, README.md, SKILL.md, install.md, and profile-sync.md for accuracy. Tightened the sync_local_profile docstring and the chrome://inspect stderr message to match. Cloud-bootstrap test updated to set BU_AUTOSPAWN. All unit tests pass.
25 行
941 B
Markdown
25 行
941 B
Markdown
browser-harness is a thin layer that connects agents to browsers via an editable CDP harness.
|
|
|
|
# Code priorities
|
|
- Clarity
|
|
- Precision
|
|
- Low verbosity
|
|
- Versatility
|
|
|
|
# Overview
|
|
Core code lives in `src/browser_harness/`:
|
|
- `admin.py` — daemon lifecycle, diagnostics, updates, profile management
|
|
- `daemon.py` — the long-lived middleman process between the browser and the agent
|
|
- `helpers.py` — CDP wrapper and core browser primitives auto-imported into `-c` scripts
|
|
- `run.py` — the `browser-harness` CLI
|
|
|
|
`SKILL.md` tells agents how to use the harness and CLI.
|
|
`install.md` tells agents how to install it, attach a browser, and troubleshoot.
|
|
|
|
An agent operating the harness only edits inside `agent-workspace/`:
|
|
- `agent_helpers.py` — task-specific browser helpers the agent adds
|
|
- `domain-skills/` — skills the agent writes and reads
|
|
|
|
# Contributing
|
|
Consider what is really needed. Prefer the smallest diff that fixes the bug.
|