Most browser automation projects pick one integration and make you live with it. This one ships the same extension-plus-CLI core behind MCP, a skill, and SDKs in three languages, which means the choice of agent runtime stops being a lock-in decision. It drives your real Chrome through a native host rather than a headless copy, so sessions and logins are the ones you already have.
A browser automation layer that does not tie itself to one agent runtime, positioned as an open alternative to the Chrome browser-use capability shipped in Codex.app. Under the hood it pairs a Chrome extension with the `open-browser-use` CLI, and you reach it through MCP, an installable skill, or the JavaScript, Python and Go SDKs.
- Browser tools over MCP for tab listing, opening and claiming, navigation, CDP, action plans and cleanup
- The same capability as an installable skill for Codex or Claude Code, added with `npx skills add` and updatable in place
- Three SDKs over one CLI — `open-browser-use-sdk` on npm and PyPI, and a Go package imported as `obu`
- A one-command Chrome setup that registers the native host and opens the Web Store page for the matching extension, with a keyed beta ZIP as a fallback for manual installation
- Downloadable `.skill` and `.zip` packages published in GitHub Releases
Chrome, plus the CLI: `npm i -g open-browser-use` (Homebrew also works on macOS and Linux), then `open-browser-use setup` to register the native host and install the extension. For MCP, `npx add-mcp "obu mcp" --name open_browser_use --all -g -y` writes the config into every supported agent, or you point a client at the `obu` command with the `mcp` argument yourself. Licensed MIT.
One command — npm i -g open-browser-use