91–100 of 202 posts
We are soon going to release a new technology, built on top of the same stack, to allow full-stack development completely in the browser. It's called BrowserPod and we think it will be a perfect fit for agents as well.
Earlier quoted context omitted.
Any sandbox technology works fine until it isn't. It's not like you could escape Java sandbox, but Java applets were removed from the browsers due to issues being found regularly. In the end, browser sandbox is one of the few that billions of people use and run arbitrary code there every day, without even understanding that. The only comparable technology is qemu. I don't think there are many hosters who will hand of…
> Any sandbox technology works fine until it isn't. Tautology is tautology. > but Java applets were removed from the browsers Java applets provided more scope compared to the browser itself, not less. They're not really comparable to seccomp or namespaces. > hosters who will hand off user account to a shared server There's lots of CI or function runners that expose docker-like environments.
They are comparable because they provided a restricted sandbox to execute untrusted code.
> There's lots of CI or function runners that expose docker-like environments.
These are running inside VMs.
[flagged]
Good opportunities arise for those who stick their neck out. Here's some inspiration for what to blog about: https://simonwillison.net/2022/Nov/6/what-to-blog-about/ It seems he started his blog in 2003: https://simonwillison.net/2003/Jun/12/oneYearOfBlogging/
As for the "browser is the sandbox" running untrusted code in the user's browser increases the risk of an unintended RCE via a sandbox escape which can be done in Chrome [0]. WASM is not going to save you either [1].
[0] https://www.ox.security/blog/the-aftermath-of-cve-2025-4609-...
This is a great example of how useful the File System Access API is. On http://co-do.xyz/ you can select a directory and let AI get to work inside of it without having to worry about side effects. The Fily System Access API is the best thing that happened to the web in years. It makes web apps first class productivity applications.
They won’t be first-class as long as native UI still has the upper hand.
Earlier quoted context omitted.
Ridden? There are issues from time to time, but it's not like you can grab the latest, patched Ubuntu LTS and escalate from an unprivileged seccomp sandbox that doesn't include crazy device files.
Any sandbox technology works fine until it isn't. It's not like you could escape Java sandbox, but Java applets were removed from the browsers due to issues being found regularly. In the end, browser sandbox is one of the few that billions of people use and run arbitrary code there every day, without even understanding that. The only comparable technology is qemu. I don't think there are many hosters who will hand of…
Java applets were killed off my MS's attempt at "embrace, extent, extinguish" by bundling an incompatible version of Java with IE, and Sun's legal response to this.
This is a great example of how useful the File System Access API is. On http://co-do.xyz/ you can select a directory and let AI get to work inside of it without having to worry about side effects. The Fily System Access API is the best thing that happened to the web in years. It makes web apps first class productivity applications.
> It makes web apps first class productivity applications. They won’t be first-class as long as native UI still has the upper hand.
That said. It's a good start.
This is a great example of how useful the File System Access API is. On http://co-do.xyz/ you can select a directory and let AI get to work inside of it without having to worry about side effects. The Fily System Access API is the best thing that happened to the web in years. It makes web apps first class productivity applications.
I know there are lots of good arguments why docker isn't perfect isolation. But it's probably 3 orders of magnitude safer than running directly on my computer, and the alignment with the existing dev ecosystem (dev containers, etc) makes it very streamlined.
Using anything other than a Linux CLI and file system seems like a misstep to me - it’s what LLMs know best and can use best.
That's great if you are a developer and that's also how I work myself. You aren't wrong. But there are a lot of users who are not developers for whom that isn't a viable path. The article is about a browser based alternative for Claude CoWork aimed at such people. LLMs are actually quite neutral and don't have preferences, wants, or needs. That's just us projecting our own emotions on them. It's just that a lot of co…
It would probably help if the sandbox presented a linux-y looking API, and translated that to actual browser commands.