BrowserOS让智能体操作已登录网页

🌐 The open-source Agentic browser; alternative to ChatGPT Atlas, Perplexity Comet, Dia.

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. Also in this repo: BrowserOS BrowserOS, the AI browser for humans A Chromium fork with an AI agent built into every new tab, for when you are the one browsing. Bring your own AI keys or run everything locally with Ollama. Read about BrowserOS · Website · Docs FAQ What's the difference between BrowserOS neo and BrowserOS? BrowserOS neo is a browser your AI drives. BrowserOS is a browser you drive, with an AI agent built in. Both ship from this repo and run side by side. Keep your daily browser, and let agents work in neo. 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. Both browsers are Chromium forks, so Chrome extensions work and your bookmarks, passwords, and settings import in one click. What platforms are supported? BrowserOS neo and BrowserOS run on macOS, Windows, and Linux. Neo's Linux builds are x64. System requirements match Google Chrome. Get help Discord · Slack Report a bug BrowserOS neo docs · BrowserOS docs Enterprise deployment: [email protected] For developers Both browsers ship 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) │ ├── server/ # BrowserOS MCP server + AI agent loop (Bun) │ ├── app/ # BrowserOS extension UI (WXT + React) │ └── app-onboard/ # BrowserOS onboarding flow (Vite) │ ├── packages/ # Shared TypeScript packages │ ├── acpx-ai-provider/ # AI SDK provider over the acpx ACP runtime │ ├── agent-mcp-manager/ # Add, link and unlink MCP servers across coding agents │ ├── browser-core/ # Core browser control primitives │ ├── browser-mcp/ # Browser MCP tool surface │ ├── build-server-tools/ # Shared build tooling for server binaries and assets │ ├── cdp-protocol/ # CDP type bindings │ ├── 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/ #