---
title: "openbrowser-ai"
pageType: "tool-profile"
schemaVersion: "1.0"
snapshotId: "tv-20260915-f4c107995a2e"
generatedAt: "2026-09-15T07:02:20.000Z"
canonicalUrl: "https://toolvitals.com/tools/openbrowser-ai/"
jsonUrl: "https://toolvitals.com/api/agent/tools/openbrowser-ai"
indexable: true
---

# openbrowser-ai

OpenBrowser is a framework for intelligent browser automation. It combines direct CDP communication with a CodeAgent architecture, where the LLM writes Python code executed in a persistent namespace, to navigate, interact with, and extract information from web pages autonomously.

## Decision context

- Status: critical
- ToolVitals score: 40/100
- Health score: 45/100
- Shipping score: 32/100
- Score mode: verdict
- Data confidence: 90/100
- Source coverage: 90/100
- Last evidence check: 2026-09-15

## Classification

- Use case: Browser Automation (browser-automation)
- Category: Automation (automation)
- Tool mode: Library Framework
- Openness: OSI-approved OSS
- License: MIT
- Tags: communication, open-source, ai, ai-agents, ai-browser, ai-browser-automation, artificial-intelligence, browser-automation, web-automation, web-scraping, cdp, llm, developer-tools, api-first, agent-skills, claude-code

## Public repository signals

- Repository: [billy-enrizky/openbrowser-ai](https://github.com/billy-enrizky/openbrowser-ai)
- Stars: 242 (adoption context only)
- Forks: 21
- Open issues: 4
- Last commit date: 2026-07-08
- Releases in 90 days: 5

## Source receipts

- [Official website](https://docs.openbrowser.me/) — checked 2026-09-15
- [Source repository](https://github.com/billy-enrizky/openbrowser-ai) — checked 2026-09-15

## Discovery status

- Search indexable: yes
- Reason: sufficient tool evidence

## Interpretation limits

- ToolVitals scores summarize bounded public maintenance, shipping, openness, and evidence signals. They are not user-review ratings.
- GitHub stars and related popularity metrics are adoption context, not quality evidence.
- Missing values mean not collected or not confidently established; they do not mean zero.
- Public signals do not prove security, uptime, support quality, customer satisfaction, or production suitability.
- Verify material decisions against the linked first-party sources and your own requirements.