bb-browser: why it is not safe to use

What we found

Our review found no signs of hidden instructions, hardcoded secrets, obfuscation, privilege escalation, or undisclosed telemetry in the inspected repo pages. The project also documents localhost use by default, with remote exposure described as an explicit user option.

The review still produced a warning because the tool is designed to operate through the user's real Chrome session. Based on the README, that can include authenticated fetches with existing cookies, access to page content, network traffic, and user activity in memory. In practice, this means the skill may reach private logged-in data that is already open in the browser.

We also found that the documented features include click, fill, eval, traffic capture, and site adapters, but the inspected README did not show a built-in confirmation layer before potentially irreversible site actions. In addition, the docs say `site update` pulls community adapters from `bb-sites`, and `AGENTS.md` says a precompiled `bb-viewer` binary is downloaded on first stream.

What to do instead

Prefer browser tools that use isolated profiles, limit access to authenticated sessions, require clear user confirmation before sensitive actions, and avoid runtime retrieval of adapters or binaries unless you have reviewed and approved them.