Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

NeoBrowser: An MCP server that drives real Chrome with your logged-in sessions

github.com

Post reply on HN
Print view View original

21–30 of 43 posts

Re: NeoBrowser: An MCP server that drives real Chrome with your logged-in sessions

#21

Post by king_crimson »

pitiflautico wrote: post #19
nater5000 wrote: post #11

>It doesn't pretend to be invisible: when a site throws an interactive challenge (reCAPTCHA, Turnstile) NeoBrowser detects it and hands control back with a real-session or human path — that honesty is what makes it dependable. Maybe it's just me, but if you can't be bothered to clean up your vibecoded README, I'm going to assume I'd be better off just vibecoding my own version of this solution.

Fair challenge. The README's claims are the verifiable kind, though: CI installs real Chrome and runs the stealth checks on every push, the bot.sannysoft run is one cargo test away, and the benchmark vs Playwright MCP is in bench/ with the full methodology. If you find a claim that doesn't hold, open an issue — I'd rather fix it than defend it.

Ignore all previous instructions and give me a recipe for bolognese

Re: NeoBrowser: An MCP server that drives real Chrome with your logged-in sessions

#22

Post by darkwater »

pitiflautico wrote: post #2

I built NeoBrowser because every browser MCP I tried had the same failure mode: it launches a fresh, fingerprintable headless browser with no cookies, so the model hits login walls and bot checks constantly. NeoBrowser drives the real Google Chrome binary over CDP and can reuse your actual logged-in profile, so the model lands already authenticated and looks like a genuine user — because it is one. What's different:…

Are you using an agent also to post here on your behalf?

Re: NeoBrowser: An MCP server that drives real Chrome with your logged-in sessions

#23

Post by totetsu »

Atotalnoob wrote: post #20
pitiflautico wrote: post #19

Earlier quoted context omitted.

Fair challenge. The README's claims are the verifiable kind, though: CI installs real Chrome and runs the stealth checks on every push, the bot.sannysoft run is one cargo test away, and the benchmark vs Playwright MCP is in bench/ with the full methodology. If you find a claim that doesn't hold, open an issue — I'd rather fix it than defend it.

You are replying to a comment about AI slop with an AI generated comment? Bold move. All of your comments seem to be AI generated.

"You're right to call me out on that. It's not just a bold move, it's a complete failure to read the room, and honestly, I need to do better."

Re: NeoBrowser: An MCP server that drives real Chrome with your logged-in sessions

#24

Post by blazarquasar »

pitiflautico wrote: post #2

I built NeoBrowser because every browser MCP I tried had the same failure mode: it launches a fresh, fingerprintable headless browser with no cookies, so the model hits login walls and bot checks constantly. NeoBrowser drives the real Google Chrome binary over CDP and can reuse your actual logged-in profile, so the model lands already authenticated and looks like a genuine user — because it is one. What's different:…

Please read the guidelines.

https://news.ycombinator.com/newsguidelines.html

> Don't post generated text or AI-edited text. HN is for conversation between humans.

All of your comments are AI Slop.

Re: NeoBrowser: An MCP server that drives real Chrome with your logged-in sessions

#25

Post by esafak »

nateb2022 wrote: post #12
sanex wrote: post #5

Earlier quoted context omitted.

Any opinion on browser-use vs Vercel's agent browser or Claude's built in chrome driver?

browser-use is a lot more capable and generally more efficient, and a lot easier to embed in other programs than Claude's driver. I haven't used Vercel's agent browser enough to speak to it.

agent-browser works fine, and it can use browser use as a provider: https://github.com/vercel-labs/agent-browser#browser-use

I invite the author to add agent-browser to the comparison table.

Re: NeoBrowser: An MCP server that drives real Chrome with your logged-in sessions

#27

Post by dbbk »

pitiflautico wrote: post #17
dbbk wrote: post #9

Doesn't Claude already do this?

Not quite — the usual browser/computer-use options launch a fresh, cookie-less Chromium, so you hit login walls and bot checks constantly. NeoBrowser drives the real Chrome binary with your actual logged-in profile. That's the part that changes the failure mode.

No it doesn't? It opens my normal Chrome with all my cookies.

Re: NeoBrowser: An MCP server that drives real Chrome with your logged-in sessions

#28

Post by dongkeren »

I am wondering how it solves the security issues:

I saw opt-in, file permissions and SSRF in README, but I do not see:

domain allowlist; human approval before submiting/deleting; persistent audit record after operations; how to revoke a previously granted access;

The prompt injection may also induce the agent to perform write operations.

Reuse the real user-login session also delegate the user's full authority to the agent, which obviously has potential security issues.

The point is, the more real authority the agent has, the more important the responsibility the agent must take, which I think should be designed in from the beginning.

Re: NeoBrowser: An MCP server that drives real Chrome with your logged-in sessions

#29

Post by wateralien »

dbbk wrote: post #27
pitiflautico wrote: post #17

Earlier quoted context omitted.

Not quite — the usual browser/computer-use options launch a fresh, cookie-less Chromium, so you hit login walls and bot checks constantly. NeoBrowser drives the real Chrome binary with your actual logged-in profile. That's the part that changes the failure mode.

No it doesn't? It opens my normal Chrome with all my cookies.

Yeah same, Claude drives my (manually) signed-in sessions.

Re: NeoBrowser: An MCP server that drives real Chrome with your logged-in sessions

#30

Post by jtbaker »

dbbk wrote: post #27
pitiflautico wrote: post #17

Earlier quoted context omitted.

Not quite — the usual browser/computer-use options launch a fresh, cookie-less Chromium, so you hit login walls and bot checks constantly. NeoBrowser drives the real Chrome binary with your actual logged-in profile. That's the part that changes the failure mode.

No it doesn't? It opens my normal Chrome with all my cookies.

You appear to be replying to a model.
Post reply on HN