Name derived from Netscape (Firefox's great-grandfather), icon is a red fox, but based on Chrome? Was this originally designed as a Firefox fork or what happened there
Show HN: Nxtscape – an open-source agentic browser
91–100 of 228 posts
Re: Show HN: Nxtscape – an open-source agentic browser
#92I'll get voted down, but I hate that cute AI fox, and hope I never see it again.
Re: Show HN: Nxtscape – an open-source agentic browser
#93[flagged]
Re: Show HN: Nxtscape – an open-source agentic browser
#94[flagged]
Re: Show HN: Nxtscape – an open-source agentic browser
#95That tab grouping capability is leaps and bounds better than the junk Google put into Chrome for "AI suggested" grouping.
Re: Show HN: Nxtscape – an open-source agentic browser
#96so agents can control tabs, forms, clicks—like a real user would.so what about undo. if an agent clicks the wrong thing, how do you roll that back without reloading the world?
There is a big red button to always stop the agent.
Re: Show HN: Nxtscape – an open-source agentic browser
#97Earlier quoted context omitted.
What do you mean? This AI cannot scrape multiple links automatically? Like "make a summary of all the recipes linked in this page" kind of stuff? If it can it definitely meets the definition of scraping.
I think what he means is it is not just generally crawling and scraping, and uses a more targeted approach. Equivalent to a user going to each of those sites, just more efficiently.
Re: Show HN: Nxtscape – an open-source agentic browser
#98Do you respect robots.txt?
No, not today. But wonder if it matter if it the agent is mostly using it for "human" use cases and not scrapping?
If your browser behaves, it's not going to be excluded in robots.txt.
If your browser doesn't behave, you should at least respect robots.txt.
If your browser doesn't behave, and you continue to ignore robots.txt, that's just... shitty.
Re: Show HN: Nxtscape – an open-source agentic browser
#99Good luck, but in your place i would at least start with something that a certain ICP needs more. Many, many manhours have been wasted by ambitious technical founders on taking down Chrome. (many also starting from a chrome fork itself). But none of them succeeded. We only have limited energy