felarof

> “Every month, alert me to any fluctuations in product cost and which items in my Square catalog are affected. Highlight any items where my COGS exceeds 35%. All the invoices are available in my email.” That would be incredibly powerful.

You could try this use case on on agent builder even today. We also have a scheduled tasks for you to schedule it to run monthly

> Have you ever thought about a marketplace for premade workflows?

We want to do this and are moving towards that! But we first need to make the premade (or user published) workflows very reliable.

There are bunch of tedious / routine tasks that AI can automate.

I think the big hurdle is mostly education / shift in mindset. We are so used to doing the task manually that most of us (including me) don't pause to think if I should be doing this or can I give to an agent.

You can't run shell commands though. Bash is the most powerful tool in claude code!

> You guys need some marketing help. There’s a lot of potential here, but you don’t do a good job of selling it.

Thank you for the feedback. Ack, we need to do a better job of marketing.

> How do you plan to monetize it? Our goal is to eventually to sell license for enterprise browsers.

At the moment, our product is designed for headful mode.

But if you want to use our browser in headless and use playwright that would work too! (we are chromium fork)

gpt-oss 20B works well. You'll want at least 12k context length for agent mode.

Thanks!

> whole Browser and not a Chrome Extension argument

Both of us are definitely biased to think our own approach is better :)

But without owning the binary, we couldn't shipped today's feature -- Agent with access to your filesystem and being able to run shell commands like Claude Cowork.

> your interface is still literally a chrome extension side panel

Yep, our interface is a chrome extension to make iterating on the UX faster. But it uses a ton of C++ APIs that we expose under `chrome.browseros.*`

> Your workflow pipeline is really cool! Any blog post/summary on how you set it up?

Thanks! We'll look into publishing a blog soon!

We are still in early versions of the feature! Haven't released on our repo yet.

What use case did you have? Happy to show a demo of current version we have (you can hit me up on discord or slack -- links available on our repo)

Thanks!

> how is it reliably enforced?

At the chromium level, you have access to every single DOM element and coordinate space around it. So, when a click happens either user or agent, we have a neat way of enforcing required action (either allow it or nullify the click).

We are still at early version. And mostly targeting enterprise sites (like SAP) which don't change that often.

What use case did you have in mind?

Ohh, interesting, technically this should already be possible. Because we already package gemini-cli into the sidecar (bun) binary. We just have to create a good UX.

What angle are you looking at this from? Is it for convenience? Or do you not like terminal UI and need a web-friendly UI for these agents?

> if you're interacting with like salesforce or a customer support tracker or an issue tracker or something you're likely using a webapp

Precisely. I think most knowledge work (especially at business) still happens browser. That is the workflow we want to target!

Good question. We think the browser is becoming the new OS. It doesn’t really matter anymore if you’re on Windows, macOS, or Linux—the browser is where most work already happens.

We see a future where it’s the main gateway to everything, and where agents live and work alongside you inside the browser. That’s why we call it BrowserOS. :)