open-browser-use
馃敭 Platform-neutral Browser Use for AI agents: real Chrome automation with a CLI + SDKs, no lock-in, dead simple.
Not yet testedsource: GitHubhomepageJavaScriptMITcommit 1489c22e357a
JavaScript, MIT licensed. The project labels itself: ai agent, ai agents, browser automation, browser use, browser use agent, cdp, chrome automation and chrome devtools protocol.
open-browser-use has not been verified yet.
Measured by Argusic on a fresh machine every time. Every number links to its evidence.
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
No recorded runs.
Topics (from GitHub)
ai-agentai-agentsbrowser-automationbrowser-usebrowser-use-agentcdpchrome-automationchrome-devtools-protocolchrome-extensionclicodexjavascript-sdkmcpmodel-context-protocolnative-messagingopen-browser-useopenai-codexpython-sdksdkweb-automation
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/open-browser-use)Questions
- Does open-browser-use run?
- open-browser-use has not been fully verified yet. No recorded run has produced a verdict yet.
- How did Argusic test open-browser-use?
- On a fresh, disposable machine, with every command recorded. 0 attempts are recorded, and the full method is on the methodology page.
- Where is the evidence for open-browser-use?
- All 0 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.