#330330th of 389 in Skills, plugins and prompts

browser-control

Rust CLI that lets coding agents drive Chrome over the DevTools Protocol

Stars
3.2k
License
MIT
Last commit
Aug 2026
Last release
Jun 2026
Language
Rust
Stars, last 29 weeks+69
21 Apr 2026: 3,091 stars28 Apr 2026: 3,091 stars5 May 2026: 3,092 stars12 May 2026: 3,092 stars19 May 2026: 3,092 stars26 May 2026: 3,095 stars2 Jun 2026: 3,095 stars9 Jun 2026: 3,095 stars16 Jun 2026: 3,097 stars23 Jun 2026: 3,099 stars30 Jun 2026: 3,103 stars7 Jul 2026: 3,105 stars14 Jul 2026: 3,107 stars21 Jul 2026: 3,110 stars28 Jul 2026: 3,113 stars4 Aug 2026: 3,116 stars11 Aug 2026: 3,119 stars18 Aug 2026: 3,121 stars25 Aug 2026: 3,123 stars1 Sept 2026: 3,129 stars8 Sept 2026: 3,130 stars15 Sept 2026: 3,137 stars22 Sept 2026: 3,140 stars29 Sept 2026: 3,143 stars6 Oct 2026: 3,144 stars13 Oct 2026: 3,150 stars20 Oct 2026: 3,150 stars27 Oct 2026: 3,152 stars3 Nov 2026: 3,156 stars10 Nov 2026: 3,160 stars

3,091 on 21 Apr 20263,160 on 10 Nov 2026

From GitHub's daily star counts.

Checked on GitHub.

Overview

browser-control is a single Rust binary that exposes a local or cloud Chrome as shell subcommands: snapshot with stable @e1-style refs, click, fill, eval, screenshot, raw CDP calls and tab management. It contains no LLM and does not require MCP, so any agent that can run shell commands can use it. A background daemon keeps event, network and console history, and failed commands write a trace to disk.

Who it is for: Developers giving shell-capable coding agents a scriptable browser

Strengths

  • Snapshot returns stable @e refs; CSS selectors and x,y coordinates also work
  • Raw `cdp` and `eval` commands cover anything the helper commands cannot
  • Same commands drive local Chrome or Browser Use, Steel, Hyperbrowser, Browserbase, or any CDP provider
  • Failed commands write a trace with daemon events, network and console history

Weaknesses

  • No MCP server; integration depends on the agent running shell commands
  • Requires a Chrome or Chromium install reachable over CDP
  • Chrome-family only, since it speaks CDP; no Firefox or WebKit support is mentioned
  • Cloud providers each need their own API key and account

What it needs

  • Needs Chrome or Chromium, Rust toolchain (only when building from source), Optional cloud browser API: Browser Use, Steel, Hyperbrowser, Browserbase

Quick answers

Is browser-control open source?

Yes. Its code is on GitHub under the MIT license.

Also in Skills, plugins and prompts

See all 389
Also in Skills, plugins and prompts
RankProjectScore
1claude-memPersistent cross-session memory plugin for Claude Code and other coding agents116.1k stars+16,557 (+17%) in 30 daysApache-2.097 out of 100
2impeccableDesign skill with 24 slash commands for AI coding agents' frontend output Live demo ↗ (opens in a new tab)108k stars+28,186 (+35%) in 30 daysApache-2.097 out of 100
3gstackMarkdown slash-command skills that give Claude Code planning, review, QA and ship roles141.2k stars+5,515 (+4.1%) in 30 daysMIT96 out of 100
#4rufloAgent harness adding swarms, memory and hooks to Claude Code and Codex Live demo ↗ (opens in a new tab)81.5k stars+7,413 (+10%) in 30 daysMIT96 out of 100
#5cavemanShortens coding-agent replies and compresses tool output before the model reads it Live demo ↗ (opens in a new tab)119k stars+8,390 (+7.6%) in 30 daysApache-2.095 out of 100