buildingopen

Openbrowser — AI skill for Claude Code

AI community

Give AI your browser.

How to install Openbrowser

This entry records only its repository, not the path inside it, so there is no exact command to give. Open buildingopen/openbrowser and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Openbrowser does

Give AI your browser. Check email, track orders, download receipts -- all authenticated, no API keys. Open source MCP server + CLI.

Alternatives in AI

Vibeproxy — Native macOS menu bar app to use your Claude Code & ChatGPT subscriptions with AI coding tools - no API keys n 3.3k ★
Dsh Plugin Subscriptions — Use ChatGPT (Codex), Claude, and Grok (X Premium) subscriptions as DeepSeek Harness LLM providers — OAuth logi 283 ★
Kru — Local-first MCP password and credential manager for AI agents 125 ★

README

OpenBrowser

![OpenBrowser logo](docs/assets/brand/openbrowser-logo.png)

[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](LICENSE) [![Python 3.12+](https://img.shields.io/badge/Python-3.12%2B-blue.svg)](pyproject.toml) [![MCP](https://img.shields.io/badge/MCP-ready-black.svg)](docs/browser-routing.md) [![Remote API](https://img.shields.io/badge/API-remote%20browser%20control-purple.svg)](docs/openbrowser-api.md)

OpenBrowser is browser infrastructure for AI agents: real Chrome sessions, persistent profiles, human login handoff, a remote API, and MCP tools.

It lets Claude, Codex, Cursor, browser-use, OpenBrowser-style agents, and custom workers share real browsers without fighting over one CDP port. Agents lease a browser, use a named profile when account state is needed, hand login challenges to a human, and leave behind telemetry plus issue reports that can be audited later. Identities can also pin proxy, locale, and timezone settings when an account requires consistent routing.

![OpenBrowser architecture](docs/assets/openbrowser-architecture.svg)

flowchart LR
  Agent["Agent\nClaude / Codex / Cursor / worker"] --> Client["MCP or API client"]
  Client --> Broker["OpenBrowser Broker"]
  Broker --> Lease["Lease manager"]
  Broker --> Profiles["Profile + identity manager"]
  Broker --> Proxy["Proxy router"]
  Broker --> Observability["Telemetry + feedback + audit"]
  Lease --> Pool["Chrome pool"]
  Profiles --> Pool
  Proxy --> Pool
  Pool --> Slots["pool-a ... pool-h\nisolated CDP sessions"]

Why

Most browser agents break in the same ways:

several agents connect to the same Chrome instance and block each other
logged-in sessions are tied to one fragile browser profile
passwords and 2FA prompts become unsafe chat messages
rich-text apps such as Slack, Discord, Notion, Linear, and X ignore DOM fill calls
failures vanish into logs, so the next agent repeats the same mistake

OpenBrowser gives agents one operating c