browser-harness · Issues· 357 open

Daemon fails to start from npm-installed package because `tsx` is missing

uv-present-but-not-uv-managed installs still get a raw uv tool upgrade error

Cold-start auto-launch fails: daemon exits before the chrome-not-running rescue branch can fire

mac-approve requires Accessibility and has no fallback, hard-blocking unattended agents

Daemon startup is not mutually exclusive: two concurrent invocations can both bind, and the second silently orphans the first

AI Skill Shield scan report: browser-use/browser-harness (3 skills)

Want to add your plugin to awesome-ai-plugins?

`mac-approve` match the Allow sheet ("Allow remote debugging?" / "Allow") in non-English Chrome

`auth login`'s OAuth callback server can hang past its own timeout on a browser preconnect

MCP server: `browser_switch_tab` advertises URL-substring matching that does not exist; `browser_cdp` uses a mutable default

`mac-approve` only works for stock Google Chrome — Brave/Edge/Canary/Arc users get "setup-required" for a toggle they already enabled

Telemetry uploads the user's script, stdout, and every helper argument — the redaction filter is applied to the wrong code path

Unit suite cannot run on Windows: 9 failures from POSIX-only test scaffolding

No CI runs the test suite — `release.yml` publishes to PyPI with no test gate

`browser-harness --update` crashes with `FileNotFoundError` when `uv` isn't installed