# BrowserOS neo mit Homebrew Cask installieren Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für BrowserOS neo in AI-Agent-Workflows. ## Installation ```sh sudo av install cask:browseros-ai/tap/browseros-neo ``` Weitere Installationsbefehle: ### macOS - Homebrew Cask (100%): ```sh brew install --cask browseros-ai/tap/browseros-neo ``` Evidenz: local Homebrew cask metadata ## Paketfakten - **Paketschlüssel:** cask:browseros-ai/tap/browseros-neo - **Paketmanager:** Homebrew Cask - **Paketmanager-Seite:** - **Version:** 0.51.1.2 - **Quellzusammenfassung:** Browser for agents - **Homepage:** - **Upstream-Dokumentation:** - **Quellarchiv:** - **Generiert:** 2026-10-22T12:10:21+00:00 ## Installationsverhalten - Bottle: nicht verfügbar ## Version und Aktualität - Seite generiert: 2026-10-22 - Manager-Version: 0.51.1.2 - lokale Daten: OK - Upstream-Repository: https://browseros.com/ - Info: No package-manager update timestamp was available. - Info: Release/tag comparison is only available for GitHub repositories. ## Projektgeschichte und Nutzung BrowserOS neo is a free, open-source secondary browser that lets MCP-compatible AI agents operate authenticated web sessions while users watch and replay their actions. ### Projektgeschichte BrowserOS originated in 2025 as an open-source Chromium-based agentic-browser project. The repository now ships two related products: BrowserOS, an AI browser driven by a person, and BrowserOS neo, a secondary browser driven by external AI agents. Neo combines a Chromium fork with a Rust MCP and JSON backend plus a browser dashboard. Its product design centers on imported browser state, parallel agent sessions, live observation, and replayable local audit trails. ### Adoptionsgeschichte BrowserOS neo targets users of MCP-capable agents including Claude Code, Codex, Cursor, VS Code, Zed, OpenClaw, and Hermes. Its one-click connection flow and Chrome import are designed to reduce the setup friction that commonly limits authenticated browser automation. ### Wie es verwendet wird Users install neo, import logins, bookmarks, extensions, and settings from Chrome, then connect an MCP-capable agent. Agent work appears in isolated tabs and in a new-tab dashboard, with each session available for later replay. Official documentation says session history, screenshots, settings, and replay data remain on the local computer under ~/.browserclaw/. The browser is intended for authenticated tasks such as inbox work, filing expenses, updating web applications, and retrieving reports. ### Warum Paket-Nerds sich dafür interessieren BrowserOS neo represents a shift from disposable headless-browser sessions toward a locally installed, inspectable browser environment for agents. Package users get a reproducible desktop installation while retaining real browser state, isolated agent tabs, an MCP endpoint, and on-disk audit artifacts. ### Zeitleiste - 2025: The BrowserOS project identifies its origin year in the repository's official citation metadata. - 2026: BrowserOS neo is documented as a distinct agent-driven browser shipping from the BrowserOS monorepo. ### Related projects - BrowserOS - Chromium - Model Context Protocol - Claude Code - Codex - Cursor ### Quellen - - - - ## Sicherheitshinweise Für BrowserOS neo wurde kein passendes lokales Secret-Handling-Manifest gefunden. Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat. ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: ~/.browserclaw/ ## Verwandte Links - [Web development packages](https://pkg.so/de/web-dev-tools/) - Matched curated package taxonomy and local package facts. - [agent-browser](https://pkg.so/de/brew/agent-browser/) - Choose agent-browser for scriptable headless automation and CI with fresh browser sessions; BrowserOS neo's official comparison positions neo for local, visible automation that retains the user's real signed-in state. Quellen: · · ## Combined YAML source View the package source record on GitHub. [combined/tap-browseros-ai-tap-browseros-neo-294e28e2.yml](https://github.com/mxcl/pkgdb/blob/main/combined/tap-browseros-ai-tap-browseros-neo-294e28e2.yml) ## Quellen - pkg.so package database - curated configuration and credential file locations - curated package history - package version freshness - package relationship graph - cross-ecosystem install command graph