| FMRS | 34 / 100 · D | 76 / 100 · B |
|---|
| Reliability | 4 / 20 | 13 / 20 |
|---|
| Security and permissions | 5 / 20 | 12 / 20 |
|---|
| Maintenance | 10 / 20 | 17 / 20 |
|---|
| Documentation | 8 / 20 | 17 / 20 |
|---|
| Setup experience | 7 / 20 | 17 / 20 |
|---|
| Best for | - Developers who need agents to automate real workflows in logged-in sessions (e.g., personal email, social media, CRM)
- Users who prefer local browser automation with data privacy
- Those who need to run multiple AI agents in parallel and monitor their activity
| - Frontend developers who want AI-assisted web debugging and performance analysis
- Scenarios that need browser automation and performance diagnostics in the same tool
|
|---|
| Not for | - CI/CD testing in stateless, login-free environments (use Playwright or browser-use instead)
- Users who prefer cloud browser services over local execution
- Those who don't need browser automation or only need simple web scraping
| - Cases that only need to scrape page text without performance analysis or complex interaction (a lighter scraping tool is a better fit)
|
|---|
| Required permissions | - Read and import browser logins (from Chrome)
- Access user browser sessions for agent automation
- Store session recordings, screenshots, and history locally under ~/.browserclaw/
- Send anonymous product usage events (agent connect/disconnect, version, OS) – never URLs, page content, prompts, tool results, or screenshots
| - Requires a local Chrome browser instance to run
- navigate_page can visit any URL; type_text/fill_form and similar tools can enter arbitrary content into the page
|
|---|
| Risks and side effects | - Agents use your real login sessions and may perform unintended actions (e.g., sending emails, posting content) – approve with caution
- Malicious prompts could lead to sensitive data exposure or unauthorized actions
- Although data is stored locally, inherent risks of browser automation (e.g., mis-clicks, form errors) remain
- Open-source version is AGPL-3.0 licensed, which may not suit all commercial use cases
| - Browser automation tools can access and manipulate the content of open pages — use only in a trusted development/test environment
- performance_start_trace and similar tracing tools continuously record browser activity — avoid leaving them running on pages containing sensitive information
|
|---|
| Supported clients | Claude Desktop, Claude Code, Codex, Cursor, VS Code, Zed, OpenCode, Antigravity | Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Cline, Amp, Kiro, Antigravity |
|---|
| Tools | 0 | 22 |
|---|