Ext Ops Panel
Open dashboard
Comparison

openbrowser vs browser-control

openbrowser is a plugin bundle for AI coding tools published by OpenBrowser Team. Marketplaces we read that list it: 1 (Community GitHub marketplaces). browser-control is a plugin bundle for AI coding tools published by AIWG Contributors. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-24. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceopenbrowserbrowser-control
Community marketplace billy-enrizky/openbrowser-ai Listed
Version: 0.1.54
Forks (GitHub): 31
Stars (GitHub): 279
Not marked · First seen
Not listed
Community marketplace jmagly/aiwg Not listed Listed
Version: 2026.10.5
Forks (GitHub): 34
Stars (GitHub): 225
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

openbrowser vs browser-control
Factopenbrowserbrowser-control
Marketplaces that list it11
Stars (GitHub) (differs)279 (better)225 (worse)
Forks (GitHub) (differs)31 (worse)34 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (openbrowser-ai)Installs as a plugin bundle
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)85
LicenceMITMIT
Repository (differs)github.com/billy-enrizky/openbrowser-aigithub.com/jmagly/aiwg
Changes in the last 7 days (differs)02
First seen (differs)2026-10-142026-10-23

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

openbrowser

In its own words, on Community GitHub marketplaces:

Browser automation MCP server with progressive disclosure design -- uses 3.2x fewer tokens than Playwright MCP across 6 tasks. Single execute_code tool runs Python with async browser functions, persisted login sessions, CLI daemon workflows, and compact description mode for token optimization.

browser-control

In its own words, on Community GitHub marketplaces:

Drive a real, user-installed Chromium-derived browser from an AIWG agent. Wraps @playwright/mcp with a setup wizard, health-check doctor, allow-list enforcement, and an opinionated agent persona that respects authorization and audit boundaries.

How to run each

openbrowser As a Claude Code plugin

Claude Code
/plugin marketplace add billy-enrizky/openbrowser-ai
/plugin install openbrowser@openbrowser-ai

browser-control As a Claude Code plugin

Claude Code
/plugin marketplace add jmagly/aiwg
/plugin install browser-control@aiwg

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: openbrowser · What it can do: browser-control · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built