Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
npx -y [email protected]Claude Code ไม่มีลิงก์ติดตั้งสำหรับคำสั่งแบบโลคัล ให้คัดลอกคำสั่งด้านล่างแล้วรันในเทอร์มินัล
claude mcp add browseros-cli -- npx -y browseros-cli@0.4.0รันในเทอร์มินัล
{ "mcpServers": { "browseros-cli": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดจากผู้เผยแพร่
Website · Docs · Enterprise
Command-line interface for controlling BrowserOS — launch and automate the browser from the terminal
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.
brew tap browseros-ai/tap
brew install --cask browseros-neo
One click brings over your logins, bookmarks and extensions. Your agents work with your real accounts from the first task.
BrowserOS neo finds Claude Code, Codex, Cursor, VS Code, OpenClaw and Hermes on your machine. Connect any of them with one click.
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.
Anything that needs a logged-in browser:
~/.browserclaw/ and never leave your machine. Privacy127.0.0.1.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.
Both browsers ship from this monorepo. Two main subsystems: the browser (Chromium fork, C++ and Python) and the agent platform (TypeScript and Rust).
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/ # 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
We'd love your help making BrowserOS neo and BrowserOS better. Start with the Contributing Guide, which routes you to the right path.
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},
}
BrowserOS neo and BrowserOS are open source under the AGPL-3.0 license.
Copyright © 2026 Felafax, Inc.
Watch the repo if you want to hear when agents can do something new.
Thank you to all our supporters.
Command-line interface for controlling BrowserOS — launch and automate the browser from the terminal
{ "mcpServers": { "browseros-cli": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
Browseros Cli ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-11-13 Command-line interface for controlling BrowserOS — launch and automate the browser from the terminal