I was actually very interested until I realized that this doesn't run on my computer…

I get the sandboxing, etc, but a Docker container would achieve the same goals.

There are pros and cons to running the browser on your own machine

For example, with remote browsers you get to give your swarm of agents unlimited and always-on browsers that they can use concurrently without being bottlenecked by your device resources

I think we tend to default to thinking in terms of one agent and one browser scenarios because we anthropomorphize them a lot, but really there is no ceiling to how parallel these workflows can become once you unlock autonomous behavior

▲

garciasn 2 hours ago | parent [-]

I appreciate that, but for the audience here on HN, I’m fairly certain we understand the trade offs or potentially have more compute resources available to us than you might expect the general user to have.

Offer up the locally hosted option and it’ll be more widely adopted by those who actually want to use it as opposed to tinker.

I know this may not fit into your “product vision”, however.

	▲	antves an hour ago \| parent [-]
		I agree it would be really cool to run this locally, it's definitely something on our radars