keon/browser-control

A tiny, fast Rust CLI that drives a real browser over the Chrome DevTools Protocol — built for coding agents.

View on GitHub ↗Jump to charts ↓

keon/browser-control has 3k+ stars and 200+ forks on GitHub, is written in Rust, and was last pushed on Aug 27, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 minutes ago
Added to GitGenius on September 22nd, 2026
Created on December 21st, 2016
Open Issues & Pull Requests: 1 (+0)
GitHub issues: Enabled
Number of forks: 234
Total Stargazers: 3,151 (+0)
Total Subscribers: 78 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2415.4 days
Mean response time: 2078.3 days
90th percentile: 3442.9 days
Tracked items: 7

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

browser-control is a command-line tool that automates browser interactions by communicating with Chrome DevTools Protocol.

The tool solves the problem of programmatically controlling a real browser instance, which is essential for coding agents and automation workflows that need to interact with web applications. It works by establishing a connection to a browser via Chrome DevTools Protocol and sending commands to perform actions like navigation, clicking, and form submission. The approach targets scenarios where agents need to execute tasks that require actual browser behavior rather than just parsing HTML.

The tool is designed for developers building coding agents or automation systems that require browser control capabilities. It suits projects where lightweight, fast browser automation is needed without the overhead of heavier frameworks. The README positions it as built specifically for coding agents, suggesting it prioritizes the integration patterns and performance characteristics those systems demand.

The project shows active development with regular commits addressing bug fixes and feature additions. Work spans multiple areas including protocol handling improvements, command-line interface refinements, and performance optimizations. The codebase receives ongoing maintenance with attention to both core functionality and user-facing reliability.