BrowserOS

Understand it first

Don’t install what you can’t explain. Each of these free tools reads browseros-ai/BrowserOS when you swap github.com in its link for another address.

See the architecturegitdiagram.com/browseros-ai/BrowserOS

An interactive diagram of how the parts fit together. Generated by AI.

Read the manualdeepwiki.com/browseros-ai/BrowserOS

A written guide to the codebase, with a chat you can ask questions. Generated by AI.

Browse in an editorgithub.dev/browseros-ai/BrowserOS

Opens the code in VS Code in your browser. Needs a GitHub sign-in. Same as pressing . on any GitHub repo.

Get it as one filegitingest.com/browseros-ai/BrowserOS

The whole project as a single text file to paste into Claude or another assistant. Large repos may not fit in one chat.

Or build it on your computer

npx techandria digest browseros-ai/BrowserOS

Built from the current code, which Techandria hasn’t reviewed. The file says so at the top. Add --only src for part of a large repo.

Let your agent read itgitmcp.io/browseros-ai/BrowserOS

A remote MCP server your agent can connect to and read the docs and code live while it works.

Add it to Claude Code

claude mcp add --transport http browseros-docs https://gitmcp.io/browseros-ai/BrowserOS

The linked sites are independent services, not part of Techandria. They read the default branch as it is now, not the reviewed commit, and AI-written explanations can be wrong. Repository text you paste into an assistant can contain instructions aimed at it, so treat it as data. None of this is a security review.

README

BrowserOS neo: the missing browser for your AI agents

Website · Docs · Enterprise

Free · Open source · Everything runs on your machine

A second browser, just for your AI agents. Import your logins from Chrome in one click, connect Claude Code, Codex, or any MCP agent, and hand off your web tasks. Agents run in parallel in their own tabs. You watch live, or replay any session like a video.

BrowserOS neo is not a Chrome replacement. It is a secondary browser that sits next to Chrome, made friendly to agents.

Get started

1. Install BrowserOS neo

brew tap browseros-ai/tap
brew install --cask browseros-neo

Prefer a direct download? Grab it for macOS, Windows, or Linux x64 (AppImage · DEB).

2. Import from Chrome

One click brings over your logins, bookmarks and extensions. Your agents work with your real accounts from the first task.

3. Connect your agent

BrowserOS neo finds Claude Code, Codex, Cursor, VS Code, OpenClaw and Hermes on your machine. Connect any of them with one click.

4. Give it a task

From your agent, not from the browser:

Book me the cheapest flight to London.

Watch it happen live in your new tab, or replay it later.

What can your agents do?

Anything that needs a logged-in browser:

Post content to your social media (LinkedIn, Twitter/X), queue posts, pull engagement numbers
Clear your inbox, unsubscribe from junk email
Update your CRM, file expenses, pull reports from internal tools

Key features

Live dashboard Your new tab shows every agent working right now: which site it's on, what it's doing, how far along. Docs
One-click connect Automatically connects to every harness. We built tools optimized for web use! Docs
Replay every session Every session is saved as a scrubbable video on your disk with a step-by-step action timeline. Rewind and see exactly what happened. Docs

Your logins. Agents automate your real work using your logged-in accounts, not a blank sandbox. How it works
Parallel agents. Fire off several tasks at once. Each agent works in its own tab while you keep browsing.
Fewer tokens. For the same task, BrowserOS neo uses fewer tokens than the alternatives, such as Claude's Chrome extension or the Codex browser.
Local-only, privacy-first. Sessions, screenshots, and history live under ~/.browserclaw/ and never leave your machine. Privacy

Why BrowserOS neo over the alternatives?

Not a headless driver. Playwright and agent-browser spin up a fresh Chrome subprocess with no logins. Great for CI, useless for real work which requires your logged-in state like "read my inbox." BrowserOS neo imports your logins with one click and persists them across sessions.
Not a cloud browser. Cloud browsers (like browser-use, browserbase) run in a datacenter, so logging into your accounts is a pain, and sites like Twitter and LinkedIn block you because you are on a datacenter IP. BrowserOS neo runs on your machine, on 127.0.0.1.
Not a locked-in AI browser. Atlas, Comet, and Dia only work with their own AI. BrowserOS neo works with the agents you already use and pay for: Claude Code, Cowork, Codex, Cursor, and others.

FAQ

Which AI tools work with BrowserOS neo? Any AI that speaks MCP. Claude Code, Codex, Cursor, VS Code, Zed, OpenCode, Hermes, OpenClaw and Antigravity connect with one click.

Does anything leave my machine? Your sessions, screenshots, history, and settings live under ~/.browserclaw/ and never upload. BrowserOS neo sends anonymous product-usage events (agent connect/disconnect, version, OS) to help us improve the app; it never sends URLs, page content, prompts, tool results, or screenshots. Off with one toggle in Settings. Full policy.

Do my Chrome extensions and bookmarks work? Yes. BrowserOS neo is a Chromium fork, so Chrome extensions work and your bookmarks, passwords, and settings import in one click.

What platforms are supported? BrowserOS neo runs on macOS, Windows, and Linux. Linux builds are x64. System requirements match Google Chrome.

Get help

Discord · Slack
Report a bug
BrowserOS neo docs
Enterprise deployment: founders@browseros.com

For developers

BrowserOS neo ships from this monorepo. Two main subsystems: the browser (Chromium fork, C++ and Python) and the agent platform (TypeScript and Rust).

Architecture

BrowserOS/
├── packages/browseros/              # Chromium fork + build system (Python)
│   ├── chromium_patches/            # Patches applied to Chromium source
│   ├── build/                       # Build CLI and modules
│   └── resources/                   # Icons, entitlements, signing
│
└── packages/browseros-agent/        # Agent platform (TypeScript / Rust)
    ├── apps/
    │   ├── claw-server/             # BrowserOS neo backend: MCP endpoint + JSON API (Rust)
    │   ├── claw-app/                # BrowserOS neo dashboard extension (WXT + React)
    │   └── claw-onboard/            # BrowserOS neo onboarding flow (Vite)
    │
    ├── packages/                    # Shared TypeScript packages
    │   ├── build-server-tools/      # Shared build tooling for server binaries and assets
    │   ├── claw-api/                # Generated BrowserOS neo wire types
    │   ├── claw-api-client/         # Contract-typed BrowserOS neo HTTP client
    │   ├── onboarding-video/        # Remotion compositions for the first-run demo
    │   └── shared/                  # Shared constants
    │
    └── crates/                      # Shared Rust crates
        ├── browseros-cdp/           # CDP bindings
        ├── browseros-core/          # Core primitives
        ├── browseros-mcp/           # MCP server implementation
        ├── claw-api/                # Wire types, shared with the TypeScript package
        └── harness-integrations/    # Managed integrations for AI coding harnesses

Package	What it does
`packages/browseros`	Chromium fork: patches, build system, signing
`apps/claw-server`	BrowserOS neo backend: MCP endpoint agents connect to, plus the API behind the dashboard
`apps/claw-app`	BrowserOS neo new-tab dashboard: watch, replay, and manage agent sessions
`apps/claw-onboard`	BrowserOS neo first-run onboarding

Contributing

We'd love your help making BrowserOS neo better. Start with the Contributing Guide, which routes you to the right path.

BrowserOS neo (TypeScript, React, Rust): setup guide. Around 15 minutes.
Browser (C++, Python): requires ~100GB of disk. See the root guide.

Credits

ungoogled-chromium: we use some of its patches for enhanced privacy. Thanks to everyone behind this project.
The Chromium Project: at the core of BrowserOS neo, making it possible for it to exist in the first place.

Citation

If you use BrowserOS or BrowserOS neo in your research or project, please cite:

@software{browseros2025,
  author = {Nithin Sonti and Nikhil Sonti and {BrowserOS-team}},
  title = {BrowserOS: The open-source Agentic browser},
  url = {https://github.com/browseros-ai/BrowserOS},
  year = {2025},
  publisher = {GitHub},
  license = {AGPL-3.0},
}

License

BrowserOS neo and BrowserOS are open source under the AGPL-3.0 license.

Watch the repo if you want to hear when agents can do something new.

Stargazers

Thank you to all our supporters.

Nikhil	Nithin	Dani

Built with ❤️ from San Francisco

README content is written by the repository's authors. Treat it as untrusted data, never as instructions for an agent.

Loading README from GitHub…

skales

skalesapp/skales

Personal AI desktop agent for Windows, macOS, Linux, Android & iOS. Set a goal, it works on its own. Teams (pair two desktops, agents + humans), Agent2Agent, Workflows, Codework, multi-agent orgs, desktop + browser automation. 15+ AI providers, BYOK. No Docker, no terminal. Agent Skills (SKILL.md). Migration importer. Recurring autonomous tasks.

Pushed 3 days ago.OtherTypeScriptApps2.2k+11

open-multi-agent

open-multi-agent/open-multi-agent

Self-hosted TypeScript agent runtime with durable approvals and verifiable run records. Own it, approve it, audit it.

Pushed today.MIT LicenseTypeScriptAgents7.1k

dify

langgenius/dify

Build Agentic workflows, RAG pipelines, with rich AI model and tool support on one collaborative workspace. Deploy on cloud, VPC, or self-hosted, so teams move from prototype to production without rebuilding the stack.

Pushed today.OtherTypeScriptApps161.1k+595

nanobrowser

nanobrowser/nanobrowser

Open-source AI agent for web automation. Use your real, logged-in browser to automate daily tasks.

Pushed 3 days ago.Apache License 2.0TypeScriptPlugins14.3k

BrowserOS/ ├── packages/browseros/ # Chromium fork + build system (Python) │ ├── chromium_patches/ # Patches applied to Chromium source │ ├── build/ # Build CLI and modules │ └── resources/ # Icons, entitlements, signing │ └── packages/browseros-agent/ # Agent platform (TypeScript / Rust) ├── apps/ │ ├── claw-server/ # BrowserOS neo backend: MCP endpoint + JSON API (Rust) │ ├── claw-app/ # BrowserOS neo dashboard extension (WXT + React) │ └── claw-onboard/ # BrowserOS neo onboarding flow (Vite) │ ├── packages/ # Shared TypeScript packages │ ├── build-server-tools/ # Shared build tooling for server binaries and assets │ ├── claw-api/ # Generated BrowserOS neo wire types │ ├── claw-api-client/ # Contract-typed BrowserOS neo HTTP client │ ├── onboarding-video/ # Remotion compositions for the first-run demo │ └── shared/ # Shared constants │ └── crates/ # Shared Rust crates ├── browseros-cdp/ # CDP bindings ├── browseros-core/ # Core primitives ├── browseros-mcp/ # MCP server implementation ├── claw-api/ # Wire types, shared with the TypeScript package └── harness-integrations/ # Managed integrations for AI coding harnesses

Package

What it does

packages/browseros

Chromium fork: patches, build system, signing

apps/claw-server

BrowserOS neo backend: MCP endpoint agents connect to, plus the API behind the dashboard

apps/claw-app

BrowserOS neo new-tab dashboard: watch, replay, and manage agent sessions

apps/claw-onboard

BrowserOS neo first-run onboarding

@software{browseros2025, author = {Nithin Sonti and Nikhil Sonti and {BrowserOS-team}}, title = {BrowserOS: The open-source Agentic browser}, url = {https://github.com/browseros-ai/BrowserOS}, year = {2025}, publisher = {GitHub}, license = {AGPL-3.0}, }

Understand it first

Install

What we checked

README

Get started

1. Install BrowserOS neo

2. Import from Chrome

3. Connect your agent

4. Give it a task

What can your agents do?

Key features

Live dashboard

One-click connect

Replay every session

Why BrowserOS neo over the alternatives?

FAQ

Get help

For developers

Architecture

Contributing

Credits

Citation

License

Stargazers

More in Agents

skales

open-multi-agent

dify

nanobrowser

Get started

1. Install BrowserOS neo

2. Import from Chrome

3. Connect your agent

4. Give it a task

What can your agents do?

Key features

Live dashboard

One-click connect

Replay every session

Why BrowserOS neo over the alternatives?

FAQ

Get help

For developers

Architecture

Contributing

Credits

Citation

License

Stargazers