casslin

thanks for the mention!

try https://github.com/nanobrowser/nanobrowser

If any one wanna try it in browser can try implement it on our chrome extension code base in typescript: https://github.com/nanobrowser/nanobrowser, we support browser use and re wrote its code in typescript, not yet supporting workflow use and love to hear how it works from community!

we built a chrome extension supporting browser use and can run locally in ur browser: https://github.com/nanobrowser/nanobrowser, feel free to implement workflow use on top of our code base in typescript. Love to learn how it works!

we built a chrome extension supporting browser use: https://github.com/nanobrowser/nanobrowser, feel free to implement workflow use on top of our code base in typescript. Love to learn how it works!

Update:

NanoBrowser v0.1.2 is now live, with support for Gemini 2.0, local models via Ollama, and several bug fixes! We're also now listed on the Chrome Web Store for easy installation: https://chromewebstore.google.com/detail/nanobrowser/imbdded...

Thanks to everyone for the feedback so far!

Forwarding tech co founder Alex's note to HN community:

Hi HN,

I'm Alex, technical co-founder of Nanobrowser. We have been working on this project to make web automation more accessible, powerful, and open.

In building Nanobrowser, we leveraged open source library such as browser use (https://github.com/browser-use/browser-use) , and Chrome Extension Boilerplate (https://github.com/Jonghakseo/chrome-extension-boilerplate-r...)

We completely rewrote the DOM processing part of browser-use with Typescript, built a multi-agent system and implemented the extension frontend with React, Vite and Typescript.

We hope you like tinkering with Nanobrowser! Checkout out our repo (https://github.com/nanobrowser/nanobrowser), create issues or open a pull reqeusts.

Thanks for taking a look! I'm excited to see what the HN community thinks.

(Alex was not able to send this comment out because he only registered his account today. )

appreciate clarification. The low domain vs high domain distinction is spot-on:Latency kills expert workflows. keeping this in mind when integrating/designing voice recognition and more accessibility control options.

Thanks! Great idea-voice recognition is in our roadmap and exploring good open source options.

We built upon amazing open source techs such as:

-browser use: https://github.com/browser-use/browser-use -chrome extension boilerplate: https://github.com/Jonghakseo/chrome-extension-boilerplate-r...

We are grateful for everyone contributing in open source, and would love for you to join our community to help making open source AI automation better!

Even if you're not interested in contributing code, you can help by:

-Trying out Nanobrowser and sharing your feedback. -Suggesting new prompts and use cases. -Helping us build a comprehensive evaluation framework. -Joining our Discord community: https://discord.gg/NN3ABHggMK

We know it's early days, and there's still a lot to improve. We appreciate your support in such early times! Thanks for checking it out! We're excited to see what you build with Nanobrowser.

amazing story! congrats!

-Lot things can be redone via an oriented approach, particularly where large amounts of text/data involved, or where content generation is needed;

-lot other things do't need AI.

-however now is early & AI = where money & attention is, so ppl tend to try integrate AI into everything

-over time this will get figured out.