browser automation
A native Rust CLI that automates browser actions for AI agents.
Same problem, same approach. Swapping one for another is a config change, not a rewrite.
choose if you prefer a Python CLI with built-in anti-bot bypass and parallel sessions over a Rust binary.
Browser automation CLI built for AI agents. Break through anti-bot walls, hand off to humans across platforms when stuck. Parallel multi-task execution, independent multi-session operation, isolated multi-account browsing.
Solves the same problem with a different architecture or at a different layer. Expect to rewrite the integration.
choose if you need a self-hosted service/API instead of a local CLI.
Automate browser based workflows with AI
choose if your app speaks MCP and needs a server endpoint rather than a CLI.
Browser MCP is a Model Context Provider (MCP) server that allows AI applications to control your browser
choose if you need an MCP server that bypasses anti-bot systems rather than a CLI.
The only browser automation that bypasses anti-bot systems. AI writes network hooks, clones UIs pixel-perfect via simple chat.
choose if you want a Python library to embed in your own code instead of a CLI.
🌐 Make websites accessible for AI agents. Automate tasks online with ease.
choose if you want a TypeScript toolkit to build agents rather than a standalone CLI.
Let AI agents browse the web. An autonomous toolkit for browser-based AI agents.
choose if you want a prebuilt vision-based browser agent instead of a CLI.
Open-source, vision-first browser agent
choose if you need an infrastructure layer that reduces token spend rather than a plain CLI.
The Browser Infra that learns and cuts token spend by upto 90%
choose if you want a managed AI browser automation service.
AI Browser Automation
choose if you want to reuse your real logged-in browser via a CLI+extension instead of a separate Chrome instance.
Let AI agents use your real, logged-in browser without interrupting your work. CLI + extension for browser automation across any shell-capable AI agent.
choose if you want a self-hostable JavaScript library instead of a Rust CLI.
Open source and self-hostable browser automation library for AI agents
choose if you want an MCP server that drives your existing Chrome via extension.
Chrome MCP Server is a Chrome extension-based Model Context Protocol (MCP) server that exposes your Chrome browser functionality to AI assistants like Claude, enabling complex browser automation, content analysis, and semantic search.
An earlier or more limited way to do the job. Still the right call when you need something small, proven, or CPU-only.
choose only if you must use an unmaintained legacy Node.js library for browser automation.
A high-level browser automation library.
choose if you need an old scriptable headless browser, but it is archived.
Scriptable Headless Browser
Does the same job, but ships as an app. Useful to a person, not swappable into a codebase.
choose if you want a Chrome extension GUI for AI web automation.
Open-Source Chrome extension for AI-powered web automation. Run multi-agent workflows using your own LLM API key. Alternative to OpenAI Operator.
choose if you want a visual block-based browser automation extension.
A browser extension for automating your browser by connecting blocks
These projects were analysed and named agent-browser among their alternatives. The relationship is not symmetric — how agent-browser rates them is a separate judgement, made when agent-browser is analysed in its own right.
calls agent-browser “Fast Rust CLI for AI browser automation; choose it for a minimal, dependency-light alternative to OpenCLI's browser commands.”
Make Any Website into CLI & Use your logged-in browser by AI agent.
calls agent-browser “Choose for a Rust CLI with Vercel tooling when you want a lightweight agent-browser command without the seed's browser extension.”
Let AI agents use your real, logged-in browser without interrupting your work. CLI + extension for browser automation across any shell-capable AI agent.
calls agent-browser “choose it for a Rust-native CLI with similar shell-composable browser commands for agents”
A tiny, fast Rust CLI that drives a real browser over the Chrome DevTools Protocol — built for coding agents.
calls agent-browser “If you want a Rust CLI instead of a Python library for the same agent-driven browser control.”
🌐 Make websites accessible for AI agents. Automate tasks online with ease.
calls agent-browser “Rust CLI for browser automation; choose when you want a lightweight terminal tool instead of an MCP server.”
Chrome DevTools for coding agents
calls agent-browser “Rust-based CLI for browser automation; choose if you prefer a fast, standalone command-line tool over a Python SDK.”
Automate browser based workflows with AI
calls agent-browser “Choose when you need a lightweight Rust CLI for scripted agent browser control rather than a Gradio web UI.”
🖥️ Run AI Agent in your browser.
calls agent-browser “Use it when you prefer a Rust/Apache-2.0 CLI for browser automation over a custom browser.”
The fastest browser for AI agents to run browser automation, built for sharing your logged-in browser state with your AI agents, like Codex or Claude Code, without disturbing you. Zero cost, zero config.
calls agent-browser “When you want a fast Rust CLI for browser automation instead of MCP.”
Chrome MCP Server is a Chrome extension-based Model Context Protocol (MCP) server that exposes your Chrome browser functionality to AI assistants like Claude, enabling complex browser automation, content analysis, and semantic search.
calls agent-browser “Choose agent-browser when you need a fast local Rust CLI for coding agents to inspect and control a browser, not a managed remote sandbox.”
🔥 Open Source Browser API for AI Agents & Apps. Steel Browser is a batteries-included browser sandbox that lets you automate the web without worrying about infrastructure.
calls agent-browser “Rust CLI for browser automation; choose it when your agent can shell out and you don't want to run an MCP server.”
Browser MCP is a Model Context Provider (MCP) server that allows AI applications to control your browser
calls agent-browser “Use this lightweight Rust CLI for browser control instead of a full agent platform.”
Open-source AI coworkers that each get a computer of their own: a browser, files and tools, with every action decided before it happens and recorded after. Bring any AG-UI agent.
calls agent-browser “Choose when you want a Rust CLI to drive browsers for AI agents rather than Playwright scripts.”
🏝️ A CLI Tool to Automate Your Everyday Web Browser.
calls agent-browser “A CLI that agents use to drive a browser, not an engine you can embed in your own codebase.”
The headless browser for AI agents and web scraping
calls agent-browser “Use as a Rust CLI for quick browser automation from the terminal, not an embeddable SDK.”
The SDK For Browser Agents
calls agent-browser “A Rust CLI tool, not an embeddable library; use it as a command-line utility or subprocess.”
Browser Harness | Self-healing harness that enables LLMs to complete any task.
calls agent-browser “Rust CLI for browser automation built for coding agents; fast and minimal but not embeddable.”
Let AI agents browse the web. An autonomous toolkit for browser-based AI agents.