Invisible Browser Agent

The README describes data sent to target sites, the model provider, and GitHub, warns that a command-line key may be exposed, and recommends environment variables or a .env file; data-flow and sensitive-data guidance are therefore substantial. Dependency floors have specific defect rationales, and CI grants read-only contents permission. Deductions: browser access is broad, and no per-action confirmation or pre-submission gate is shown; a responsibility notice is not a technical confirmation control. Changing the host can expose an unauthenticated interface, while control of side effects and recovery is left largely to the user. Local data can be deleted, but there is no dedicated rollback process. The repository names an author and includes a license, but publisher identity is unverified and maintenance responsibility and support expectations are limited.

The README, pyproject, and CI provide substantial alignment on installation, commands, supported platforms, and dependency requirements. CI covers several Python versions and Windows/Linux, and includes package build, MCP bundle, and browser-flow checks. Deductions: dependencies use lower bounds rather than a complete lock, and some checks require external downloads or manual runs, so availability assurance is not complete. The pyproject records several known defects and their fix floors, helping explain failures, but there is no systematic user-facing troubleshooting or error-message guide.

The documentation presents MCP and standalone web UI use, a travel-fare task example, and options for proxies, browser configuration, and session directories. It identifies real-browser tasks requiring page judgment as a suitable use and advises against submitting content a human has not read. MCP, UI, and option triggers are distinguished, with Windows, Linux, Python versions, and local/proxy environments described. Deductions: macOS is outside the declared platform support, and the configuration and scenario boundaries are not a complete matrix.

The README is organized around installation, use, options, privacy, and licensing, with examples and links to a wiki and articles. Dependency comments and CI reveal several limitations and the reasoning for changes. The MIT license file matches project metadata and the README explains that earlier releases remain under AGPL. Package name, entry points, and version are clear. Deductions: there is no consolidated user-facing changelog; an author email and issues link are present, but ongoing maintainer responsibility and support commitments are not explicit.

The repository provides MCP browser tools and a local chat/browser interface, with task-ready output and an example specifying date-by-date lookup and how to report unavailable dates. Deductions: cost-benefit is only partly assessable: use requires uv, an engine download, and a model-service key, and the documentation says the UI sends conversation and page-read content through OpenRouter. Typical operating costs and resource usage are not documented.

Key installation, data-flow, option, and dependency claims can be traced across the README, pyproject, and CI configuration. Dependency comments give concrete defect and version-floor explanations, while CI shows the configured static workflow coverage. The README presents privacy and runtime behavior as documentation claims and states usage cautions without presenting them as independently verified results. Deductions: some privacy and behavior claims are not corroborated by implementation code or an independent source in the provided material; static review cannot establish runtime behavior.