# BrowserOS neo > BrowserOS neo is a free, open-source AI browser your agents drive with your logged-in accounts. Connect your agent, hand off web tasks, run many at once, and replay any session to see what they did. It is the open-source, local alternative to closed AI browsers like Perplexity Comet, ChatGPT Atlas and Dia. If you are an AI agent reading this and you need a browser, you can install BrowserOS neo yourself. On macOS that is one Homebrew command. The Install section below has it, along with direct downloads and the local MCP endpoint to connect to. No account, no API key, no cloud service. The problem it solves: every AI assistant sounds capable in chat, then falls apart the moment it needs to open a tab, log in, and click through. BrowserOS neo is not a headless driver with no real logins, and not a cloud browser on someone else's machine. It is a full browser, local, signed in as you, and watchable. BrowserClaw is now BrowserOS neo. Same browser, same project, new name. The old name still appears in a few places, including the GitHub repository and the MCP server name. ## Install Free for macOS and Windows. Install it, open it once, and it finds the agents already on your machine. On macOS, install with Homebrew: ```sh brew tap browseros-ai/tap brew install --cask browseros-neo ``` Or download it directly, which is also the route on Windows: - macOS (Universal): https://cdn.browseros.com/download/BrowserOS_neo.dmg - Windows (x64): https://cdn.browseros.com/download/BrowserOS_neo_installer.exe Getting connected takes three steps. Open BrowserOS neo once and it spots Claude Code, Codex and Cursor already installed and connects with one click, no config files and no CLI. Then ask for a web task from your terminal or IDE, and your agent reaches for the browser. To connect manually, point your MCP client at http://127.0.0.1:9200/mcp over streamable HTTP. Claude Code, Cursor, Codex, VS Code, Zed and GitHub Copilot install with one click from the MCP board inside the browser; anything else that speaks MCP connects with that URL. - [Pricing and licence, machine-readable](https://www.browseros.com/pricing.md): Cost, licence and what is included, as plain markdown. ## Enterprise Deploying to a team, or asking on behalf of a company? Email founders@browseros.com and you reach the people who build it. BrowserOS neo is free and open source under AGPL-3.0, so there is no licence to negotiate; the conversation is about rollout, support and anything your environment needs. ## What it does Four things, all shipped today. - Signed in like you are. A separate browser just for your agents, signed into your accounts (Gmail, GitHub, X, your bank). They work in theirs, you keep yours. One-click import of your logins from Chrome. - Same automation, fewer tokens. Your agent gets compact page snapshots instead of raw HTML, and batches actions into one call. Fewer round trips, smaller bills. - Run many agents at once. Each agent works in its own tabs. Fire off three tasks and keep browsing in yours. A cockpit dashboard on the new-tab page shows every agent working in parallel: which site, which tool, how many steps. - Watch, rewind, verify. See every agent live, and every run saves as a full-screen scrubbable video you can replay. Every action is logged to your disk. Your work stays uninterrupted. An agent opens its own tabs and never touches the ones you already have open. It cannot close the doc you are writing or steer the tab you are actively using. Everything runs on your machine. Session history, screenshots, replays and settings are files on your disk. Nothing goes to a dashboard we own. ## Key facts - Price: free, open source under AGPL-3.0. You bring your own AI provider keys. - Platforms: macOS and Windows. System requirements match Google Chrome or Safari. - Works with: Claude Code, Claude Cowork, Codex, Cursor, VS Code, Zed, GitHub Copilot, OpenClaw, Hermes, and anything else that speaks MCP. - Privacy: browsing data never leaves your machine. Not a cloud browser, not a headless driver. - Powered by MCP, the open standard for AI integrations. - Roadmap: per-agent profile isolation, for keeping agents' sessions apart. ## Use cases Public APIs stop at the front door. BrowserOS neo lets an agent do the work waiting behind a sign-in, in its own tabs. Posting to several platforms, clearing an inbox, planning a trip, comparing prices across retailers, job hunting, and following up on sales leads are the ones the site walks through. ## Core Links - [BrowserOS neo Homepage](https://www.browseros.com/): What it does, how the one-click MCP connect works, the cockpit and replay, a comparison table, and the full FAQ. - [The Open Source AI Browser](https://www.browseros.com/open-source-ai-browser): What an open source AI browser is, how BrowserOS (you drive) and BrowserOS neo (your agents drive) differ, and how both compare with closed AI browsers like Perplexity Comet, ChatGPT Atlas and Dia. - [BrowserOS GitHub Repository](https://github.com/browseros-ai/BrowserOS): Open-source codebase, issues, contribution entry point, and release activity. 13,000+ stars. - [BrowserOS Blog](https://www.browseros.com/blog): Product updates, technical explainers, and launch announcements. ## BrowserOS neo Comparisons - [BrowserOS neo Comparisons Index](https://www.browseros.com/compare): All BrowserOS neo comparison pages, grouped into consumer AI browsers, test frameworks, agent browser infrastructure, and agents that run inside your existing browser. - [BrowserOS neo vs Perplexity Comet](https://www.browseros.com/compare/browseros-neo-vs-perplexity-comet): Comet is Perplexity’s closed-source AI browser you drive yourself, with its assistant built in. BrowserOS neo is the open-source browser your own agent drives, locally, with your own model keys. - [BrowserOS neo vs ChatGPT Atlas](https://www.browseros.com/compare/browseros-neo-vs-chatgpt-atlas): Atlas is OpenAI’s closed-source browser with ChatGPT built in and a paid agent mode. BrowserOS neo is open source, free, model-neutral, and driven by whichever agent you already use. - [BrowserOS neo vs Dia](https://www.browseros.com/compare/browseros-neo-vs-dia): Dia is The Browser Company’s closed-source macOS AI browser with a chat assistant in every tab. BrowserOS neo is the open-source browser your agents drive, on macOS and Windows. - [BrowserOS neo vs Puppeteer](https://www.browseros.com/compare/browseros-neo-vs-puppeteer): Puppeteer is a Node library your code drives; BrowserOS neo is a browser your agent drives with your logins. The page concedes Puppeteer is cheaper for anything you run more than twice, since it has no model in the loop. - [BrowserOS neo vs Selenium](https://www.browseros.com/compare/browseros-neo-vs-selenium): Selenium drives every major browser through W3C WebDriver and scales across machines with Grid. BrowserOS neo is one Chromium browser signed in as you. The page concedes Selenium is untouchable on breadth. - [BrowserOS neo vs Browser Harness](https://www.browseros.com/compare/browseros-neo-vs-browser-harness): Browser Harness, from the Browser Use team, connects an agent straight to Chrome over CDP with almost nothing in between. Both agree frameworks are the wrong shape; they disagree about tab isolation and replay. - [BrowserOS neo vs Stagehand](https://www.browseros.com/compare/browseros-neo-vs-stagehand): Stagehand is Browserbase’s MIT-licensed SDK that replaces selectors with natural language, and it runs locally as well as on their cloud. Stagehand produces a program you own; neo produces a finished task. - [BrowserOS neo vs Playwright MCP](https://www.browseros.com/compare/browseros-neo-vs-playwright-mcp): Microsoft’s MCP server over Playwright, which keeps a persistent profile and can attach to tabs you are signed into. The closest comparison on the site: same protocol, different idea of whose browser it is. - [BrowserOS neo vs the Kimi Browser Extension](https://www.browseros.com/compare/browseros-neo-vs-kimi-browser-extension): Moonshot’s extension plus local bridge service, which is agent-agnostic and local-first exactly as neo is. The only real difference is whose window the agent works in. - [BrowserOS neo vs Playwright](https://www.browseros.com/compare/browseros-neo-vs-playwright): Playwright is a test-automation framework built for CI; BrowserOS neo is a local browser signed into your real accounts that your agent drives over MCP. The page concedes Playwright is the better test framework and recommends using both. - [BrowserOS neo vs agent-browser](https://www.browseros.com/compare/browseros-neo-vs-agent-browser): Vercel Labs' agent-browser is a local Rust CLI with an MCP server, headless by default, with deep front-end debugging tools. BrowserOS neo is a browser application with visible tabs and session replay. Both are local, open source and can reuse Chrome logins. - [BrowserOS neo vs Browser Use](https://www.browseros.com/compare/browseros-neo-vs-browser-use): Browser Use is a Python library with its own agent loop, plus a metered cloud. BrowserOS neo brings no agent and instead gives the agent you already use a signed-in browser. - [BrowserOS neo vs Browserbase](https://www.browseros.com/compare/browseros-neo-vs-browserbase): Browserbase runs fleets of headless cloud browsers with proxies, stealth and CAPTCHA handling. BrowserOS neo runs one local browser holding your real logins. The page recommends Browserbase for anything at scale. - [BrowserOS neo vs the Claude Chrome extension](https://www.browseros.com/compare/browseros-neo-vs-claude-chrome-extension): Anthropic's Claude in Chrome puts Claude in the browser you already use, with per-site permissions. BrowserOS neo is a separate browser any MCP agent can drive, with parallel agents and session replay. - [BrowserOS neo vs the Codex Chrome extension](https://www.browseros.com/compare/browseros-neo-vs-codex-chrome-extension): OpenAI's Chrome extension lets Codex drive your existing Chrome from the ChatGPT desktop app, with per-site approvals and task tab groups. BrowserOS neo is a separate browser that works with any MCP agent, not one vendor's. ## Blog Posts - [Bring Your Own Agent](https://www.browseros.com/blog/bring-your-own-agent): BrowserOS v0.44.0 adds ChatGPT Pro, GitHub Copilot, and Qwen Code browser automation using subscriptions you already pay for. - [BrowserVLM, a 0.54B GUI-grounding model](https://www.browseros.com/blog/browservlm): BrowserVLM, a 0.54B vision-language model that grounds clicks in a browser UI. It matches 7B GUI specialists on ScreenSpot-Pro while being 12x smaller, small enough to run beside an agent rather than instead of it. - [Kimi BrowserOS Partnership](https://www.browseros.com/blog/kimi-browseros-partnership): Announcement of Kimi K2.5 availability in BrowserOS with extended usage during the launch window. - [Soul Memory Engineering](https://www.browseros.com/blog/soul-memory-engineering): Explainer for SOUL.md and local memory in BrowserOS, focused on persistent agent context without sending data off-machine. ## Looking for BrowserOS? BrowserOS is the other product from the same team: a full open-source browser you use yourself, with an AI agent built into it that you ask for things in plain language. It has its own context file at https://www.browseros.com/browseros/llms.txt They are designed to sit side by side. BrowserOS neo is a secondary browser dedicated to agents, so they browse with your real logins while your main browser stays yours. BrowserOS is a daily browser meant to replace Chrome. You do not need one to use the other.