Skip to content

feat: add browser_harness plugin — drive a real Chromium through browser-harness - #52

Open
mpfaffenberger wants to merge 1 commit into
mainfrom
feat/browser-harness-plugin
Open

feat: add browser_harness plugin — drive a real Chromium through browser-harness#52
mpfaffenberger wants to merge 1 commit into
mainfrom
feat/browser-harness-plugin

Conversation

@mpfaffenberger

@mpfaffenberger mpfaffenberger commented Sep 1, 2026

Copy link
Copy Markdown
Owner

What

Opt-in CDP browser control for Code Puppy, backed by browser-use/browser-harness.

  • Three opt-in tools: browser_harness (Python with the harness helpers pre-imported), browser_screenshot (inline Kitty-protocol capture), and browser_doctor (health report with the documented fix)
  • /browser status|enable|disable|doctor|connect|disconnect|install|recordings, with consent persisted so the tools stay unregistered until the user opts in
  • Honest browser support: Chrome/Chromium/Brave/Edge/Arc/Helium are drivable; Firefox and Safari are reported as present but undrivable (no CDP endpoint)
  • Endpoint precedence: ambient BU_CDP_WS/BU_CDP_URL, then a saved endpoint, then harness auto-discovery; known harness errors map to their documented fix

Verification

  • tests/browser_harness: 76 passed
  • ruff check + ruff format --check clean

Note: full-suite green depends on #51 landing first (pre-existing shell_safety import breakage against code_puppy main, unrelated to this plugin).

…ser-harness

Opt-in CDP browser control for Code Puppy, backed by browser-use/browser-harness.

- three opt-in tools: browser_harness (Python with the harness helpers
  pre-imported), browser_screenshot (inline Kitty-protocol capture), and
  browser_doctor (health report with the documented fix)
- /browser status|enable|disable|doctor|connect|disconnect|install|recordings,
  with consent persisted so the tools stay unregistered until the user opts in
- honest browser support: Chrome/Chromium/Brave/Edge/Arc/Helium are drivable,
  Firefox and Safari are reported as present but undrivable (no CDP endpoint)
- endpoint precedence is ambient BU_CDP_WS/BU_CDP_URL, then a saved endpoint,
  then harness auto-discovery; known harness errors map to their documented fix
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant