> 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?
> 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!