Productivity & writingDocumented overviewLast checked Oct 1, 2026

BrowserOS neo (formerly BrowserClaw): Pricing, Features & Best Use Cases

Free, open-source local browser that AI agents (Claude Code, Codex, Cursor) drive via MCP using your logged-in accounts, with session replays.

BrowserOS neo (formerly BrowserClaw) pricing and usage limits

Prices checked Oct 1, 2026 on the official US pricing page. Prices and limits change often.

Vendor pricing page re-checked automatically 11 days ago: no changes detected.

Free access and trial conditions

Completely free; open source under AGPL-3.0

No trial; free to download and use

Paid plans: what changes as you upgrade

Open Source (Free) self-serve

Free source (opens in a new tab)

Free

For: Individuals and small teams using AI agents locally

Limits

  • Unlimited agents
  • Unlimited sessions
1 more
  • Full replay history (local)

Includes

  • One-click Chrome login import
  • MCP integration with any agent
3 more
  • Parallel agent tabs
  • Session replay (video)
  • Open source AGPL-3.0

No API

Usage caps, credits and extra costs

None; bring your own AI provider keys

N/A

What is BrowserOS neo (formerly BrowserClaw), and how does it work?

BrowserOS neo is a secondary desktop browser built for AI agents. You import logins from Chrome, connect agents such as Claude Code, Cowork, Codex or Cursor through MCP with one click, and the agent opens its own tabs to browse, click and read while signed in as you. A new-tab dashboard shows every running agent, several can work in parallel, and each session is saved as a scrubbable replay on disk. The browser is open source under AGPL-3.0, runs entirely on your machine and is free; you bring your own AI provider.

BrowserOS neo (formerly BrowserClaw) homepage — screenshot of the productivity & writing AI tool, Oct 1, 2026
BrowserOS neo (formerly BrowserClaw)'s official site: how the product presents itself. browseros.com, captured Oct 1, 2026

What you provide and what you get back

How BrowserOS neo (formerly BrowserClaw) works: what you provide, where it runs and what you get backYOU PROVIDEYour inputChrome saved logins (imported onc…Browser prompts to agents via MCPAd agent commands: 'check my emai…PRODUCTIVITY & WRITINGBrowserOS neo (formerly Brow…Desktop, MCPfree tier, paid price not publish…free tier availablechecked Oct 1, 2026YOU GET BACKThe resultAgent browser sessions with full…Read-only page snapshots (token-e…Session recordings saved to disk…input → BrowserOS neo (formerly BrowserClaw) → output · from the vendor's own pages, no hands-on test unless stated
What you give BrowserOS neo (formerly BrowserClaw) and what comes back, from its documentation

You provide

  • Chrome saved logins (imported once)
  • Browser prompts to agents via MCP
  • Ad agent commands: 'check my email', 'book a flight', 'unsubscribe from emails'

You get back

  • Agent browser sessions with full visibility and replay
  • Read-only page snapshots (token-efficient)
  • Session recordings saved to disk as video replays

Where you can use it

Platforms
Desktop (macOS, Windows), MCP (integrates with agents)
Account
Not required
Works offline
1

Where BrowserOS neo (formerly BrowserClaw) is most useful

Scenarios are worked out by our editors from the documentation; the actual result depends on your input and plan.

Letting a coding agent complete web tasks that need real logins

Who
Developers using Claude Code, Codex or Cursor
You provide
Agent prompt asking for a web task (e.g. 'check Gmail and summarize important emails')
Expected result
Agent logs in, completes the task, returns results; all actions visible in real-time and replay

Running several agent browser tasks in parallel

Who
Power users automating multiple workflows
You provide
Multiple agent prompts running simultaneously
Expected result
Each agent works in isolated tabs; new-tab dashboard shows all running agents; tasks complete independently

Auditing and replaying what an agent did

Who
Anyone verifying agent behavior for safety or debugging
You provide
Completed agent session
Expected result
Full-screen, scrubbable video replay of every action; rewind to spot where things went wrong

What BrowserOS neo (formerly BrowserClaw) does, and where it stops

One-click Chrome login import

Reads saved logins from Chrome and imports them into BrowserOS neo; no manual re-typing Agent can immediately log in to Gmail, GitHub, banking sites, etc. without credential entry

Access: First-time setup; import dialog on launchLimit: Only works if you have Chrome installed; requires permission to read Chrome data

MCP connection to Claude Code, Codex, Cursor, VS Code, Zed and others

One-click connection via MCP standard; no config files or CLI needed Agents can request browser actions from your IDE terminal or chat interface

Access: MCP install board on new-tab page; click Connect for each agentLimit: Requires the agent to support MCP; older tools not supported

Agent dashboard on the new-tab page

Shows every running agent: which site it's on, current task, step count, elapsed time Watch all agents in real-time; see progress at a glance

Access: New-tab page automatically; live updatingLimit: Dashboard is local only; no cloud sync or sharing

Parallel isolated agent tabs and session replay

Each agent works in its own set of tabs; tabs are grouped and isolated; sessions save as video replays Run Claude, Codex and Cursor on different tasks simultaneously without interference; review what happened later

Access: Automatic; no config neededLimit: Replays are local video files; no cloud backup

Pros, cons and deal-breakers

Where BrowserOS neo (formerly BrowserClaw) is strong

  • Completely free and open source (AGPL-3.0) No licensing cost; can be modified and redistributed under AGPL terms documented
  • All browsing data stays local Privacy and security benefit; nothing goes to BrowserOS servers documented
  • Works with any MCP-capable agent Supports Claude Code, Cursor, Codex, VS Code, Zed and future agents documented
  • 13,000+ GitHub stars and Y Combinator backing Active community and commercial validation documented

Limitations to check before paying

  • Desktop only: macOS and Windows; no Linux support mentioned Unsuitable for Linux-only developers or cloud-based workflows documented
  • Requires your own AI agent and provider keys Must have Claude API key, OpenAI key, etc.; no bundled provider documented
  • Agents run signed in to your real accounts, which needs careful oversight High trust required; a buggy agent prompt could send emails or delete data documented
  • Enterprise offering not priced publicly Large teams must contact sales for custom terms documented

How to use BrowserOS neo (formerly BrowserClaw) for setting up an AI agent to browse the web with your logins

BrowserOS neo (formerly BrowserClaw) documentation — screenshot of the productivity & writing AI tool, Oct 1, 2026
BrowserOS neo (formerly BrowserClaw) documentation: where the steps below come from. docs.browseros.com, captured Oct 1, 2026

Set up BrowserOS neo (formerly BrowserClaw)

  1. Download BrowserOS neo for macOS or Windows from browseros.com
  2. Launch the app; it automatically detects Claude Code, Cursor, and Codex installed locally
  3. Click 'Connect' next to Claude Code (or your agent) on the MCP install board
  4. BrowserOS neo imports your Chrome logins and is ready to go

Example: setting up an AI agent to browse the web with your logins

  1. Open Claude Code (or your terminal) and ask: 'Check my Gmail and summarize the 5 most important emails'
  2. Claude Code connects to BrowserOS neo; the agent opens a new tab and logs in to Gmail
  3. Watch the agent click through emails in real-time on the BrowserOS neo dashboard
  4. When done, Claude Code returns the summary to your terminal
  5. Open the replay on the new-tab page to rewind and see exactly what the agent did

Review and export the result

  1. Verify connection by checking the MCP board shows 'Connected' next to your agent
  2. Test by asking the agent a simple web task: 'Open Wikipedia and search for AI'
Example prompt suggested by our editors (not a recorded output of the product)
Check my Gmail inbox, find emails from my manager, and summarize their action items.

BrowserOS neo (formerly BrowserClaw) integrations and API

BrowserOS neo (formerly BrowserClaw) documentation — screenshot of the productivity & writing AI tool, Oct 1, 2026
BrowserOS neo (formerly BrowserClaw) documentation (continued). docs.browseros.com, captured Oct 1, 2026

Native integrations and export formats

Export: Session video replays (local MP4 files)

API access and separate billing

BrowserOS neo (formerly BrowserClaw) has no public API in its official documentation. MCP is the primary integration method; no REST API

Privacy, data use and commercial rights

Summarized from the vendor's current policies; this is not legal advice and a vendor's badge is not an independent audit.

How your inputs and outputs are handled

Chrome logins imported locally; agent actions stored as session recordings on disk

None; open source; no training on user data

Sessions stored locally indefinitely until user deletes them

Commercial use and plan restrictions

N/A; free and open source

No plan restrictions

Controls for business users

  • Open source (AGPL-3.0) allows inspection of code
  • Everything runs locally; no cloud storage

Policies: browseros.com/

Explore BrowserOS neo (formerly BrowserClaw) further

Tools and guides near BrowserOS neo (formerly BrowserClaw)

BrowserOS neo (formerly BrowserClaw) user reviews

No user reviews yet.

Used BrowserOS neo (formerly BrowserClaw)? Be the first to share your experience.

Write a review

Reviews are checked by a moderator before they appear. Your email is never published. Plain text only.

Your rating (required)

Show what you made or what went wrong. Images are published only if the review is approved; location data is removed.

    BrowserOS neo (formerly BrowserClaw) FAQ

    Is BrowserOS neo free?

    Yes, completely free and open source under AGPL-3.0. You bring your own AI provider keys. source (opens in a new tab)

    Is BrowserOS neo a cloud browser or does it run locally?

    BrowserOS neo runs entirely on your own machine. It is not a cloud browser. Your logins, sessions, screenshots, and replays are local files. source (opens in a new tab)

    Can I run two AIs at the same time?

    Yes. Every agent gets its own set of tabs, tracked separately. Codex and Claude Code can each work on their own tasks at the same time without stepping on each other. source (opens in a new tab)

    Can I replay what my AI did?

    Yes. Every session is saved as a scrubbable video. Rewind, spot the moment things went sideways, and give the agent a better instruction next time. source (opens in a new tab)

    What operating systems are supported?

    macOS and Windows. System requirements match Google Chrome or Safari. source (opens in a new tab)

    What changed at BrowserOS neo (formerly BrowserClaw) recently

    :

    Sources and review methodology

    Official sources and verification dates

    Not verified: Linux support (not mentioned; appears desktop-only); Enterprise pricing and terms; Whether per-agent profile isolation is on the roadmap.

    How we documented and maintain this page

    Every fact about BrowserOS neo (formerly BrowserClaw) above comes from the 2 official pages listed here, last compared on Oct 1, 2026; we have not run BrowserOS neo (formerly BrowserClaw) ourselves, so it has no editorial score. How we check and re-check pages.

    Article updated Oct 10, 2026; prices checked Oct 1, 2026. Outbound links to vendors are plain links; we do not earn commissions. How we review · Report an error