choose it for a Rust-native CLI with similar shell-composable browser commands for agents
Browser automation CLI for AI agents
- 44.0k
- Rust
- Apache-2.0
browser automation for AI agents
A tiny Rust CLI that drives a real browser over the Chrome DevTools Protocol for coding agents, exposing shell-native browser commands without LLM or MCP requirements.
Same problem, same approach. Swapping one for another is a config change, not a rewrite.
choose it for a Rust-native CLI with similar shell-composable browser commands for agents
Browser automation CLI for AI agents
choose it for a Python-based browser automation CLI aimed at AI agents with anti-bot features
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 it when you want to expose specific websites as CLI commands instead of raw browser control
Make Any Website into CLI & Use your logged-in browser by AI agent.
choose it for Python-based AI workflow automation with LLM planning rather than a no-LLM shell CLI
Automate browser based workflows with AI
choose it when you need a self-hosted browser sandbox/API rather than a local CLI
๐ฅ 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.
choose it for stealth automation over MCP/CDP when your agent speaks MCP
The only browser automation that bypasses anti-bot systems. AI writes network hooks, clones UIs pixel-perfect via simple chat.
choose it for a self-learning TypeScript agent browser if you do not need a Rust CLI
The Browser Infra that learns and cuts token spend by upto 90%
choose it for a Python LLM-agent framework that controls browsers rather than a standalone CLI
๐ Make websites accessible for AI agents. Automate tasks online with ease.
choose it for a TypeScript SDK with cloud/browserbase integration instead of shell commands
The SDK For Browser Agents
choose it for a TypeScript toolkit for autonomous browser agents, accepting less active maintenance
Let AI agents browse the web. An autonomous toolkit for browser-based AI agents.
choose it for a cloud-oriented AI browser automation framework rather than a local CDP CLI
AI Browser Automation
choose it when you want MCP control through a Chrome extension instead of a standalone process
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.
choose it for a CLI plus extension that shares your logged-in browser across shell-capable agents
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 it for an MCP server wrapping Playwright if your stack already uses MCP/Playwright
Playwright Model Context Protocol Server - Tool to automate Browsers and APIs in Claude Desktop, Cline, Cursor IDE and More ๐
choose it for vision-first browser automation when your agent relies on screenshots instead of DOM refs
Open-source, vision-first browser agent
choose it for official Chrome DevTools access via MCP rather than a shell CLI
Chrome DevTools for coding agents
choose it for an MCP-native browser agent with human-in-the-loop controls
Give your AI agent a real browser โ with a human in the loop. Open-source MCP-native browser agent.
choose it to let coding agents drive your real logged-in Chrome via browser-use's harness
Browser Harness | Self-healing harness that enables LLMs to complete any task.
An earlier or more limited way to do the job. Still the right call when you need something small, proven, or CPU-only.
choose it as an older self-hostable browser automation library, but expect less maintenance than the seed
Open source and self-hostable browser automation library for AI agents
choose it only for archived Oxylabs AI Studio integration, not for new work
AI Browser Agent is an advanced Browser AI tool developed by Oxylabs AI Studio that automates real user browsing tasks using natural language instructions.
choose it only for an older MCP browser-control server; it has been unmaintained for 1.5 years
Browser MCP is a Model Context Provider (MCP) server that allows AI applications to control your browser
Does the same job, but ships as an app. Useful to a person, not swappable into a codebase.
choose it as a full AI-coworker application with a browser, not a library you embed
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.
choose it as a standalone browser app for agents, not a CLI to swap into existing code
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.
These projects were analysed and named browser-control among their alternatives. The relationship is not symmetric โ how browser-control rates them is a separate judgement, made when browser-control is analysed in its own right.
calls browser-control โChoose for a tiny Rust CLI over CDP when you want a lightweight coding-agent browser driver without the seed's 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 browser-control โMinimal Rust CLI driving browser via CDP for coding agents; choose for a tiny dependency-free CLI instead of MCP.โ
Chrome DevTools for coding agents
calls browser-control โChoose if you need a minimal Rust CLI driving Chrome for coding agents instead of a web UI.โ
๐ฅ๏ธ Run AI Agent in your browser.
calls browser-control โWhen you need a tiny Rust CLI for browser control over CDP.โ
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 browser-control โMinimal Rust CLI that drives a real browser over CDP; choose it for a tiny, fast shell-controllable bridge without MCP overhead.โ
Browser MCP is a Model Context Provider (MCP) server that allows AI applications to control your browser
calls browser-control โChoose this tiny Rust CLI only when a coding agent needs basic local CDP page control, not Steel's full session/proxy/stealth infrastructure.โ
๐ฅ 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 browser-control โUse this tiny Rust CLI to drive a browser over CDP if you need a minimal tool.โ
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 browser-control โA Rust CLI for CDP browser control; use it from the command line.โ
Browser Harness | Self-healing harness that enables LLMs to complete any task.