This is awesome. I would love to prove it, but your page (vscan.dev) is broken. One qq, why is this tool closed-source? I think that to achieve the community trust in tools like this one, it would be great if this could be open-source. Maybe you can monetize it as an open-core model.

It would be great to have a section in the README about how the code looks without using the library, contrasting it with the example you already have. I would need a significant time-saving reason to use a new external library. This is because, for new libraries like yours, we don't know how long you plan to support it. For that reason, using an external library for a core part of my business is a huge risk for me.

My use case: cursor for open-source terminal-based coding agents.

That's a great point. Newrev actually gives you the best of both worlds:

The AI agents still run terminal-based environments on a backend server (local or cloud), so they have full access to resources and native tools. The browser UI simply provides a much more intuitive, visual interface for interaction, file exploration, and live previews, making these powerful agents accessible and easy to use without deep terminal expertise.

So running this on the browser implies you need to know how to clone a git repo, run a chmod command, etc. How do you plan to productize this so that it actually gets to the hands of non technical people?

For the short term, newrev is designed for developers who want to try out these powerful AI CLI agents but prefer not to live in the terminal. This means they can start using them right away.

Our mid-term goal is to offer a fully managed cloud service, primarily still for developers. However, we're seeing more agents run highly autonomously, which means newrev could eventually empower non-developers too. Think of how many 'no-coders' are already using tools like Cursor or Winsurf for their projects today.