Hey cool stuff since last update!
I still don't buy the we needed it to be a whole Browser and not a Chrome Extension argument:
- your interface is still literally a chrome extension side panel
- none of the agentic browsers from the bigger players like Atlas and Comet really took off either
I do think the server side integration is required:
- with rtrvr.ai a ton of users are integrating our web agent chrome extension via Remote MCP from chatgpt.com as well as triggering as an API endpoint remotely. Your implementation is limited to only local connections as I understand.
- the biggest unlock for users is running at scale, so just being able to launch a hundred cloud browsers, do a task, and return results while you do other things. So we see hybrid cloud/local execution as the key unlock for this year
Your workflow pipeline is really cool! Any blog post/summary on how you set it up?
Last year was a lot of technical builders exploring the capabilities, and I am excited for this year of making these agentic browsers useful!
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!
Thanks for initial feature request! We do read every single request :)
Yes, we expose BrowserOS as an MCP server -- that you can use from claude code, cursor, opencode, etc -- https://docs.browseros.com/features/use-with-claude-code
MCP server works out of box (unlike Chrome DevTools MCP which requires tricky setup).
> we're adding browser-level guardrails (think IAM for agents)
This sounds interesting, but where would I go to see these guardrails and their implementation? I tried searching in the repository and couldn't find them.
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)
IAM for agents sounds interesting but how is it reliably enforced? You also built evals?
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?
What would be great is if it could work in the browser like Claude in chrome and communicate (with my control) back to objects on my desktop like my ide for example or really anything
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?
why are you calling this an OS
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. :)
Is this really true? Mobile device users are all mostly forced to use apps rather than the browser for most stuff, and people on desktop PCs/laptops are probably either using them for gaming (all desktop apps), or work where a lot of stuff is desktop apps.
Sure regular consumer stuff like social media is webapps (if they're not mobile only), and if you're interacting with like salesforce or a customer support tracker or an issue tracker or something you're likely using a webapp, but the move to mobile devices for most consumer stuff means that people still using PCs are largely power users.
> 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!