# BrowserOS > BrowserOS is the open-source AI browser that turns your words into actions by running AI agents locally on your computer. BrowserOS is a privacy-first Chromium-based browser built for agentic browsing, AI-assisted research, and multi-step task automation. It runs on macOS, Windows, and Linux, works with Chrome extensions, and supports both cloud and local models. The BrowserOS website llms.txt is generated from structured site metadata and aligned with the BrowserOS docs so product claims, supported providers, and connected-app capabilities stay consistent across both properties. ## Core Links - [BrowserOS Homepage](https://www.browseros.com/): Product overview, positioning, supported operating systems, and the main download entry point. - [BrowserOS Docs](https://docs.browseros.com/): Documentation for features, providers, integrations, comparisons, and setup. - [BrowserOS GitHub Repository](https://github.com/browseros-ai/BrowserOS): Open-source codebase, issues, contribution entry point, and release activity. - [BrowserOS Blog](https://www.browseros.com/blog): Long-form product updates, technical explainers, and launch announcements. ## Key Facts - [Open-source AI Browser](https://www.browseros.com/): BrowserOS positions itself as an open-source browser with built-in AI agents and local-first privacy. - [Supported AI Providers](https://docs.browseros.com/features/bring-your-own-llm#cloud-providers): BrowserOS docs list cloud providers including Kimi K2.5, Gemini, Claude, OpenAI, OpenRouter, Azure OpenAI, AWS Bedrock, and OpenAI-compatible providers such as Together AI, Fireworks, Groq, and Perplexity. - [Local Models](https://docs.browseros.com/features/bring-your-own-llm): BrowserOS also supports local models through Ollama and LM Studio for private, offline, or low-cost chat workflows. - [Integrations and Automation](https://docs.browseros.com/features/connect-mcps): BrowserOS docs describe 40+ supported apps across email, calendar, messaging, project management, docs, storage, design, CRM, payments, analytics, support, search, and social workflows. - [Pricing](https://www.browseros.com/): BrowserOS is described on the website as free and open source, with optional third-party model costs depending on provider usage. ## Comparison Docs - [BrowserOS vs OpenClaw](https://docs.browseros.com/comparisons/openclaw): Comparison page for BrowserOS and OpenClaw. - [BrowserOS vs Claude Cowork](https://docs.browseros.com/comparisons/claude-cowork): Comparison page for BrowserOS and Claude Cowork. - [BrowserOS vs Chrome DevTools MCP](https://docs.browseros.com/comparisons/chrome-devtools-mcp): Comparison page for BrowserOS and Chrome DevTools MCP. ## BrowserOS neo Comparisons - [BrowserOS neo Comparisons Index](https://www.browseros.com/compare): All BrowserOS neo comparison pages, grouped into test frameworks, agent browser infrastructure, and agents that run inside your existing browser. - [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. ## Docs - [Getting Started](https://docs.browseros.com/onboarding): Set up BrowserOS quickly and learn the core product flow. - [Bring Your Own LLM](https://docs.browseros.com/features/bring-your-own-llm): Connect your own cloud or local models to BrowserOS. - [Connect Apps](https://docs.browseros.com/features/connect-mcps): Connect 40+ apps so BrowserOS can work across email, calendar, docs, and project tools. - [MCP Clients](https://docs.browseros.com/features/use-with-claude-code): Control BrowserOS from Claude Code, OpenClaw, Gemini CLI, and other MCP clients. - [Workflows](https://docs.browseros.com/features/workflows): Build repeatable browser automations with the BrowserOS workflow system. ## 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. - [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.