# Installer BrowserOS neo avec Homebrew Cask

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de BrowserOS neo pour les workflows d'agents IA.

## installation

```sh
sudo av install cask:browseros-ai/tap/browseros-neo
```

Commandes d'installation supplémentaires:

### macOS

- Homebrew Cask (100%):

```sh
brew install --cask browseros-ai/tap/browseros-neo
```

  Preuve: local Homebrew cask metadata

## Faits du paquet

- **Clé du paquet:** cask:browseros-ai/tap/browseros-neo
- **Gestionnaire de paquets:** Homebrew Cask
- **Page du gestionnaire de paquets:** <https://github.com/browseros-ai/homebrew-tap/blob/53539f3d68fbd92eeedcfcb53da062194d7ec8eb/Casks/browseros-neo.rb>
- **Version:** 0.51.1.2
- **Résumé source:** Browser for agents
- **Page d'accueil:** <https://browseros.com/>
- **Docs amont:** <https://browseros.com/>
- **Archive source:** <https://cdn.browseros.com/releases/browserclaw/0.51.1.2/macos/BrowserOS_neo_v0.51.1.2_universal.dmg>
- **Généré:** 2026-10-22T12:10:21+00:00

## Comportement d'installation

- Bouteille: non disponible

## Version et fraîcheur

- page générée: 2026-10-22
- version du gestionnaire: 0.51.1.2
- données locales: OK
- dépôt amont: https://browseros.com/
- info: No package-manager update timestamp was available.
- info: Release/tag comparison is only available for GitHub repositories.
## Historique du projet et usages

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.

### Historique du projet

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.

### Historique d'adoption

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.

### Modes d'utilisation

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.

### Pourquoi les passionnés de paquets s'y intéressent

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.

### Chronologie

- 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

### Sources

- <https://browseros.com/>
- <https://docs.browseros.com/>
- <https://docs.browseros.com/llms.txt>
- <https://github.com/browseros-ai/BrowserOS>


## Notes de sécurité

Aucun manifest local de gestion des secrets correspondant n'a été trouvé pour BrowserOS neo. Les métadonnées de paquet restent publiées ici afin que la couverture future dispose d'une URL stable.



## 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/

## Liens liés

- [Web development packages](https://pkg.so/fr/web-dev-tools/) - Matched curated package taxonomy and local package facts.
- [agent-browser](https://pkg.so/fr/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.

  Sources: <https://browseros.com/> · <https://github.com/browseros-ai/BrowserOS> · <https://agent-browser.dev/>

## 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)


## Sources

- pkg.so package database
- curated configuration and credential file locations
- curated package history
- package version freshness
- package relationship graph
- cross-ecosystem install command graph
