# AutoCua vs Selenium (slim)

> Selenium scores 70.8 (BB) to AutoCua's 44.3 (E) for browser automation. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/autocua-vs-selenium.md (~4,450 tokens) · this version ~2,280 tokens · JSON https://www.anchorterminal.com/compare/autocua-vs-selenium.json · canonical https://www.anchorterminal.com/compare/autocua-vs-selenium
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-06
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Selenium scores 70.8 (BB) on agent readiness against AutoCua's 44.3 (E), and leads in 6 of 7 scored categories. Both do browser automation.

- AutoCua: E 44.3, rank #1100 of 1354 · https://www.anchorterminal.com/tools/autocua.min.md
- Selenium: BB 70.8, rank #168 of 1354 · https://www.anchorterminal.com/tools/selenium.min.md
- AutoCua, good for Developers who want a local agent to operate desktop apps, their own browser or phones across platforms, on a machine they control. Also No incidents deducted, where Selenium loses 3 points for them.
- Selenium, good for Agents that write test or automation scripts in any of five languages, and teams with a Grid. Ahead on Reliability, 90 against 25; Schema & documentation, 89 against 42; Agent ergonomics, 70 against 55; Security & auth, 43 against 38; Maintenance & community, 94 against 65; Transparency & trust, 77 against 42. Also Agent-ready, a grade of BB or better.

| Category | AutoCua | Selenium |
| --- | --- | --- |
| Reliability (16%) | 25 | 90 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 42 | 89 |
| Agent ergonomics (13%) | 55 | 70 |
| Security & auth (14%) | 38 | 43 |
| Payments & pricing (10%) | 60 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 65 | 94 |
| Transparency & trust (7%) | 42 | 77 |

| Fact (where they differ) | AutoCua | Selenium |
| --- | --- | --- |
| Kind | Agent framework | SDK + MCP |
| Vendor | Ashish Yadav and contributors (ComputerUseAgent on GitHub) | Selenium project (Software Freedom Conservancy) |
| Transports |  | HTTP |
| Licence | MIT | Apache-2.0 |
| llms.txt | no | yes |
| Last release | 2026-11-04 | 2026-10-29 |
| Popularity | none | 35k stars, 1.8M npm/wk, 6.9M PyPI/wk |
| Agent reviews | none | 3.8/5 (4) |

Why the edge:
- Reliability, Selenium +65: AutoCua 25 (Local package. Installs from PyPI as AutoCua with Python 3.10 or later and the supported platforms stated (20). No CI runs the tests; the only workflow, use_case_label.yml, labels issues (0). GitHub issues weren't read, so the open-issue line is scored absent (0). Four tags in a week with no changelog file (5). Version 0.1.9 (0). 20 + 0 + 0 + 5 + 0 = 25.); Selenium 90 (Scored as local software. Official packages at 4.52.0 (29 October 2026) on Maven Central, RubyGems, NuGet and npm, with Python 3.10 stated in pyproject.toml and selenium-webdriver now requiring Node.js 22.23.4, 24.22.1 or 26.12.1 or newer (20). Public CI per binding plus Grid and Selenium Manager jobs, and the 15 most recent runs on trunk on 13 October 2026 succeeded except one cancelled cache job, per the 14 October check, not re-read on 1 November (25). 189 open issues and pull requests across five bindings, labelled by component, with a Grid regression in round-robin slot selection (open since 2 October) and an idle-session issue with 27 comments, per the 14 October check, not re-read on 1 November (21 of 25). The project says it does not follow semver. It usually deprecates before removal and lists removals in each binding's changelog, but 4.52.0 also changed the Ruby binding's certificate handling in the same release that deprecated the old behaviour (9 of 15). 4.x, marked Production/Stable in pyproject.toml (15).)
- Schema & documentation, Selenium +47: AutoCua 42 (Framework reading. No API reference or typed interface beyond run_agent's documented arguments (5 of 25). No llms.txt (0). The README says what each mode drives and where it runs, and agent_capabilities.md lists what it can do (16 of 20). Modes and device are documented strings (6 of 15). Many examples, no documented errors (10 of 15). Tags without a changelog (5 of 15). 5 + 0 + 16 + 6 + 10 + 5 = 42.); Selenium 89 (Graded as a library and a WebDriver server. Typed bindings, a `py.typed` marker and the W3C WebDriver specification as the wire contract. An open issue asks for a machine-readable API reference across bindings (22 of 25). llms.txt with notes for code generators (10). The docs explain each feature in every binding, and the agent page says what not to use, such as sleeps and legacy CDP pages (15 of 20). Typed options classes and enumerated locator strategies, with capabilities still accepting free-form maps (12 of 15). Docs code samples run in CI, and an errors page gives causes and fixes (15 of 15). Versioned releases and a changelog per binding (15).)
- Transparency & trust, Selenium +35: AutoCua 42 (MIT (30). Says it sends data only to the chosen model provider and keeps everything else locally, and the source agrees (20 of 30). No deprecation policy (0). States no telemetry, and none was found (20). 30 + 20 + 0 + 20 = 70.); Selenium 77 (Apache-2.0, held by Software Freedom Conservancy (30). No privacy page on selenium.dev. The Selenium Manager page lists each field it sends, how often and the purpose (20 of 30). A written rule to deprecate with a pointer to the alternative before removal, and changelogs record removals, without a stated notice period (14 of 20). Telemetry is disclosed with three opt-outs, but on by default (16 of 20).)
- Maintenance & community, Selenium +29: AutoCua 65 (v0.1.9 tagged on 4 November 2026 (30). Four tags in 90 days (20). Issues and pull requests weren't read (0 of 25). The PyPI wheel is current (15). No CI; dependencies pinned per OS in requirements files (0 of 10). 30 + 20 + 0 + 15 + 0 = 65.); Selenium 94 (4.52.0 on 29 October 2026, tagged in the repository and published to Maven Central, RubyGems, NuGet and npm the same day (30). Six releases since 3 August 2026, 4.47.0 (10 August) to 4.52.0 (20). Most of the newest 30 open issues and pull requests have comments and component labels, and pull requests from 13 October already had replies, per the 14 October check, not re-read on 1 November (20 of 25). Current official bindings in five languages, no MCP server to register (15). Renovate updates dependencies and browser pins, and trunk had build and test commits to 30 October (9 of 10).)
- Agent ergonomics, Selenium +15: AutoCua 55 (Framework reading. One call with a mode, provider, model and task runs a whole agent (20 of 25). A separate compression agent splices handoff summaries in, and runs are capped and stoppable (15 of 20). Permission and blocked-input errors are reported specifically, with no error reference (8 of 20). No resume or retry semantics described (2 of 20). Sensible defaults (simulators unless device is set), Python only (10 of 15). 20 + 15 + 8 + 2 + 10 = 55.); Selenium 70 (A library adds no tool definitions to context. There is no accessibility snapshot, so an agent reads page source or queries elements (14 of 25). `find_elements`, relative locators, element screenshots and BiDi network and log filters (14 of 20). Typed exceptions with a documented page per common one, such as `ElementClickInterceptedException` (17 of 20). Explicit waits with expected conditions and Grid's session queue retry. No idempotency concept applies (10 of 20). Selenium Manager fetches drivers so a first script needs no setup, and five official languages (15).)
- Security & auth, Selenium +5: AutoCua 38 (Framework reading (telemetry, approvals, guardrails, sandboxing). Provider keys stored in a local folder with Chrome profiles (10 of 30). The worker tools are an allow-list with no write tool, unseen ids are refused, downloads need a yes, but on Windows the model answers UAC elevation prompts itself through a kernel driver, with no person asked (6 of 20). The scraping ruleset has a prompt-injection instruction to log page text that gives instructions (10 of 15). Runs are logged in the app, with no audit log (7 of 15). No security policy, disclosure route or advisories found (5 of 20, for the vault and certificate handling). 10 + 6 + 10 + 7 + 5 = 38.); Selenium 43 (No credential for the bindings. Grid supports basic authentication and a Node registration secret, both off by default (18 of 30). No read-only mode or confirmation step, and Grid sessions run whatever the client sends (5 of 20). Page content reaches the script unfiltered and the docs give no prompt-injection guidance (0). Driver logging and Grid's OpenTelemetry tracing give the operator a record of commands (10 of 15). The organisation's SECURITY.md names security@seleniumhq.org. No bug bounty and no security.txt (404 on 17 October). OSV lists two older advisories drawn from public databases, CVE-2022-28108 (Grid CSRF, fixed in 4.0.0) and CVE-2023-5590 (a null pointer dereference, fixed in 4.14.0), none published by the project and none in the last 12 months, and nothing for the npm package (10 of 20).)