BrowserOS neo

What is BrowserOS neo?

BrowserOS neo is a free, open-source browser that AI agents drive with your logged-in accounts. You import Chrome logins in one click, connect Claude Code, Codex, Cursor, or Cowork over MCP, and hand off web tasks. Several agents can work in parallel tabs, and every session is saved for replay.

Top Features:

• Real logins: agents browse Gmail, GitHub, and other sites signed in as you.
• Parallel agents: each agent works in its own tabs while you keep browsing.
• Session replay: every run saves as a scrubbable video you can rewind.

Use Cases:

• Inbox cleanup: ask your agent to unsubscribe from newsletters inside your signed-in Gmail.
• Social posting: have an agent post one update across several logged-in social accounts.
• Form filling: let agents complete checkout forms and bookings behind a sign-in.

Who Can Use BrowserOS neo?

• Developers: give Claude Code, Codex, or Cursor a browser without writing automation scripts.
• Ops teams: hand repetitive logged-in web chores to agents and audit them.
• Privacy-minded users: keep sessions, screenshots, and replays stored on their own machine.

Pricing

• Open source (free): the full browser under the AGPL-3.0 license for macOS and Windows.
• AI usage (pay as you go): model costs are billed by whichever AI provider your agent uses.
• Enterprise (contact sales): team rollouts arranged directly with the people who build it.

Pros and Cons

Pros:

• Local first: browsing data, logins, and replays never leave your own computer.
• Fewer tokens: compact page snapshots replace raw HTML, which lowers model costs.
• Easy setup: it detects installed agents and connects them in one click.

Cons:

• Limited platforms: it runs on macOS and Windows, with no Linux build mentioned.
• Shared logins: agents share your accounts until planned per-agent profile isolation ships.
• Needs an agent: automation requires an MCP-capable agent and your own AI provider keys.

FAQs:

1) Is it free?

Yes, it is free and open source, and you bring your own keys.

2) Which agents are supported?

Any MCP agent works, including Claude Code, Codex, Cursor, Zed, and GitHub Copilot.

3) Is it a cloud browser?

No, it runs entirely on your machine and sends nothing to company servers.

4) Is this the same as BrowserClaw?

Yes, BrowserClaw was renamed, and existing installs keep working as before.

5) Is the original BrowserOS required?

No, it is standalone, though both browsers can run side by side.