- Users evaluating AI-native browsers
- Teams comparing browser agents and browser automation stacks
- Developers interested in Chromium-based agentic browsing
AGPL-3.0 · Agents
BrowserOS
Open-source agentic browser positioned as an alternative to AI-native browsers and browser assistants.
11K stars 1.2K forks AGPL-3.0 license 2026-06-10 verified
$
# BrowserOS$
pip install browseros$
npx browseros --help Open sourceLocal first
Overview
What is BrowserOS?
BrowserOS is an open-source agentic browser project built around the idea that the browser itself can be the AI agent workspace. It is relevant for teams comparing browser agents, browser automation tools, and AI-native browsing environments.
Browser-native agent workspace
BrowserOS frames the browser itself as an agentic environment.
Many user workflows already happen in the browser, so agent capabilities close to the browser surface can reduce integration friction.Open-source browser alternative
The project is positioned as an open-source alternative to AI-native browsers.
Open implementation makes it easier to inspect privacy, extension behavior, and agent boundaries.Local AI orientation
The repository topics emphasize local LLM and browser-agent workflows.
Local model support is important for users who do not want every browsing action routed through a hosted agent. Use cases
What teams use it for
Ecosystem
Tags & capabilities
Comparison
How it stacks up
When to choose BrowserOS
Compare it with nearby agents by looking at hosting model, integration surface, license, and whether the official docs show the workflow you need.
FAQ
Questions
Is BrowserOS open source?
Yes. The GitHub repository is listed under the AGPL-3.0 license.
How is BrowserOS different from browser automation libraries?
BrowserOS is an agentic browser environment, while browser automation libraries are usually developer tools that control a browser from outside.
Decision brief
JSON
Should you use BrowserOS?
- Teams that only need a library for scripted browser automation
- Users who need a stable enterprise browser today without evaluating project maturity
- Verified 2026-06-10
- License: AGPL-3.0
- Repo: browseros-ai/BrowserOS
- Open-source signal
Deployment
local, cloud
Permission surface
browser
Decision signals
Local first
Agent packet
Structured decision data for BrowserOS
This packet is the compact machine-readable view agents should use before following source links or taking action.
Capabilities
browser, browser automation, local inference, workflow orchestration
Constraints
open source, local first
Deployment
local, cloud
Permission surface
browser
Recommended workflows
Browser automation, Coding agent workflow, Local or private AI stack
Overview
What BrowserOS does
What it is
It is a browser-centered AI agent environment rather than a standalone automation script.
Why it matters
The browser is the main surface where many agents need to act, inspect, and help users.
How to evaluate it
Evaluate it against a few real browsing workflows, then compare with browser automation libraries and external browser agents.
Facts
Known metadata and operating surface
These fields are separated from editorial interpretation so agents can reason over facts and missing checks.
Resource type agent
Category Agents
Maturity active
Difficulty Unknown
License AGPL-3.0
Pricing open source
Verified 2026-06-10
Source confidence high
Risk level moderate
Fit matrix
Where BrowserOS fits in an agent stack
strong
Browser automation
BrowserOS has multiple signals for browser automation, including matching tags, capabilities, category, or positioning.
- Run one non-sensitive website task and inspect clicks, waits, retries, and changed URLs.
- Confirm official docs, current maintenance, license, and runtime constraints before production use.
strong
Coding agent workflow
BrowserOS has multiple signals for coding agent workflow, including matching tags, capabilities, category, or positioning.
- Run a small repository change and inspect the diff, tests, and rollback path.
- Confirm official docs, current maintenance, license, and runtime constraints before production use.
strong
Local or private AI stack
BrowserOS has multiple signals for local or private ai stack, including matching tags, capabilities, category, or positioning.
- Verify hardware requirements, data path, storage, and whether all calls stay in your environment.
- Confirm official docs, current maintenance, license, and runtime constraints before production use.
partial
Evaluation and observability
BrowserOS has at least one signal for evaluation and observability, but should be checked against a real task before adoption.
- Add one repeatable test case and confirm results can run again in review or CI.
- Confirm official docs, current maintenance, license, and runtime constraints before production use.
partial
Reusable skill workflow
BrowserOS has at least one signal for reusable skill workflow, but should be checked against a real task before adoption.
- Run one skill end to end and check whether it produces evidence or structured output.
- Confirm official docs, current maintenance, license, and runtime constraints before production use.
weak
Connector or protocol layer
BrowserOS is not primarily positioned for connector or protocol layer in the current metadata.
- Connect one low-risk service, then inspect schemas, auth scope, errors, and logs.
- Confirm official docs, current maintenance, license, and runtime constraints before production use.
Inputs and outputs
What an agent should inspect
Likely inputs
- Web pages, DOM state, screenshots, forms, or browser sessions
- Repositories, files, issues, terminal output, and test results
- Official setup instructions and a small real workflow
Likely outputs
- Action traces, changed pages, extracted data, or completed browser steps
- Diffs, commits, explanations, test results, or review notes
- Scores, traces, regression results, dashboards, or failure cases
- A decision on whether this resource fits the target workflow
Evidence
Sources, claims, and missing checks
Claims are marked separately from source links so future crawlers and reviewers can update them without rewriting the page.
GitHub github
Repository source for code, license, issues, releases, and implementation details.
Homepage homepageOfficial or project-controlled source for this resource profile.
BrowserOS is listed as open source.
License metadata: AGPL-3.0BrowserOS has a recorded GitHub repository: browseros-ai/BrowserOS.
Resource facts and GitHub source link.BrowserOS supports these recorded deployment modes: local, cloud.
OpenAgent decision signal metadata.BrowserOS is tagged with browser, browser automation, local inference, workflow orchestration capabilities.
OpenAgent capability taxonomy.- Dedicated docs link is missing.
- Repository freshness has not been recorded.
Next action
How to start evaluating BrowserOS
Inspect repository
Check license, recent activity, issues, examples, and security-sensitive code paths.
Open sourceOpen Homepage
Start from the official source before adopting third-party instructions.
Open source Compare
Alternatives and nearby resources
Use related resources to compare category fit, license, deployment model, and first-workflow behavior.
FAQ
Common questions about BrowserOS
Is BrowserOS open source?
Yes. The GitHub repository is listed under the AGPL-3.0 license.
How is BrowserOS different from browser automation libraries?
BrowserOS is an agentic browser environment, while browser automation libraries are usually developer tools that control a browser from outside.