Earlier quoted context omitted.
Why a new browser extension for Chrome instead of an MCP operating Chrome over Chrome DevTools Protocol? https://chromedevtools.github.io/devtools-protocol/ Not vouching for this project, but just an example of the category existing: https://github.com/AgentDeskAI/browser-tools-mcp
CDP is great for testing. But one of the most basic checks for bot detection is checking for CDP(webdriver). Its always going to be a cat and mouse game. You'll see a bunch of solutions captch solvers etc, But they usually are only good for a few weeks.
Show HN: Nxtscape – an open-source agentic browser
201–210 of 228 posts
Re: Show HN: Nxtscape – an open-source agentic browser
#202Earlier quoted context omitted.
Why a new browser extension for Chrome instead of an MCP operating Chrome over Chrome DevTools Protocol? https://chromedevtools.github.io/devtools-protocol/ Not vouching for this project, but just an example of the category existing: https://github.com/AgentDeskAI/browser-tools-mcp
CDP is great for testing. But one of the most basic checks for bot detection is checking for CDP(webdriver). Its always going to be a cat and mouse game. You'll see a bunch of solutions captch solvers etc, But they usually are only good for a few weeks.
Re: Show HN: Nxtscape – an open-source agentic browser
#203In the meantime, the bigger opportunity with relatively little competition at the moment is the Web itself, not which application to browse it with. The Web absolutely sucks, and that's most of the reason we even feel the need for an "elevated browser experience" in the first place (i.e. lifted trucks on the information highway).
The Web sucks, because it was built naively, then optimized for profitable friction. But all of it stood on the assumption that the cost of production on the web involves highly skilled human labor. LLMs have shattered that assumption, but the effects have not manifested. Which is to say that the entire existing Web is probably going to become a marginal, legacy corner of a much bigger base of LLM-driven hypermedia contents that is yet to come.
Re: Show HN: Nxtscape – an open-source agentic browser
#204From a founder hat, I can see why the code base is a moat, hard problem. I hope the effort is worth the cost.
Good luck.
Re: Show HN: Nxtscape – an open-source agentic browser
#205As a consumer I'm asking myself why not just make an extension. I can see myself trying and picking 2 or more browser addons to to turbo charge + chat with any page. From a founder hat, I can see why the code base is a moat, hard problem. I hope the effort is worth the cost. Good luck.
Yes, in the long run, owning the underlying codebase would allow us to have more control and provide better user experience. (Very similar to cursor forking vscode)
Re: Show HN: Nxtscape – an open-source agentic browser
#206Earlier quoted context omitted.
Not to pull a "why should I use Dropbox when I have rsync" but why should we use this over adding a Playwright MCP to Claude Desktop or similar? Does having access to Chromium internals give you any super powers over connecting over the Chrome Devtools Protocol?
Yes, eventually we think there is more value of owning the entire stack than just be a MCP connector. Few ideas we were thinking of: integrating a small LLM, building MCP store into browser, building a more AI friendly DOM, etc. Even today, we use chrome's accessibility tree (a better representation of DOM for LLMs) which is not exposed via chrome extension APIs.
Chrome has a built-in LLM: https://developer.chrome.com/docs/ai/built-in
Re: Show HN: Nxtscape – an open-source agentic browser
#207Re: Show HN: Nxtscape – an open-source agentic browser
#208Earlier quoted context omitted.
Yes, eventually we think there is more value of owning the entire stack than just be a MCP connector. Few ideas we were thinking of: integrating a small LLM, building MCP store into browser, building a more AI friendly DOM, etc. Even today, we use chrome's accessibility tree (a better representation of DOM for LLMs) which is not exposed via chrome extension APIs.
> building a more AI friendly DOM You might consider the Accessibility Tree and its semantics. Plain divs are basically filtered out so you're left with interactive objects and some structural/layout cues.
The issue is mac and windows accessibility APIs are opaque and I have no idea what I'm doing so I'm forced to vibe code it all which is not turning out too well... :-)
I suffer from mild carpal tunnel so I want to build a really low latency computer use agent that can do anything on my computer without me having to learn the talon voice syntax or some other traditional accessibility software like mac dictation.
Re: Show HN: Nxtscape – an open-source agentic browser
#209Re: Show HN: Nxtscape – an open-source agentic browser
#210IMO comments so far seem to be not seeing the forest for the trees -- I can imagine incredible value for myself in a browser that hooks into a local LLM, writes everything it sees to a local timestamped database (oversimplification), parses and summarizes everything you interact with (again, oversimplification -- this would be tunable and scriptable), exposes Puppeteer-like functionality that is both scriptable via c…
How it all started:
“Bookmarks and shit don’t cut it anymore”.
Tsk tsk.
I’ll just leave this here: