Very neat idea! I implemented it into my self hosted remote coding agent: https://stanislas.blog/2026/02/netclode-self-hosted-cloud-co...
Deno Sandbox
181–185 of 185 posts
Re: Deno Sandbox
#182> The real key materializes only when the sandbox makes an outbound request to an approved host. If prompt-injected code tries to exfiltrate that placeholder to evil.com? Useless.
pretty smart. why isn't this the norm?
Re: Deno Sandbox
#183Earlier quoted context omitted.
Saw quite bit on HN. A quick search this popped up: https://news.ycombinator.com/item?id=45486006 If we can spin up microVM so quickly, why bother with Docker or other containers at all?
10 seconds is actually not that impressive. we spin up Sandboxes around 50-200ms at E2B
isnt that number mostly due to firecracker?
Re: Deno Sandbox
#184Not sure if anyone from the deno team is monitoring this forum, but I was trying to stand up a dev-base snapshot and pretty quickly ran into a wall. Is it not currently possible to create a bootable volume from the CLI? https://docs.deno.com/sandbox/volumes/#creating-a-snapshot has an example for the js API, but the CLI equivalent isn't specifying --from and the latest verson of the deno CLI installed fresh from deno…
could you try again? it should be available now (no need to update deno CLI)
It's working now, thanks. While I've got your attention, it was a little bit of effort to wrap my head around the APIs when `sandbox create` uses --root AND/or --volume, `snapshot create` uses positional args , and `volumes create` uses --from
I know that each of these things is subtly different, but they're similar enough that the bootable snapshot creation workflow (which I expect is a common one) has some sharp edges, since you have to interact with all three APIs at the same time.
Also, the CLI doesn't give a useful error when you try to create a snapshot from a currently attached volume.
Finally, updating a snapshot is more steps than I'd ideally like. I would much rather be able to make changes in a sandbox with a snapshot root and have them persist as a new snapshot. I kind of get why this isn't currently the case, but The volume/snapshot dance feels (for my usecase) like it's missing some abstraction.
That said, now that I've got a snapshot set up it's a nice experience. I've got an alias for `deno sandbox create --root dev --ssh` and I can `claude` in yolo mode without much fear.
Congratulations to the team :)
Re: Deno Sandbox
#185Ignoring the fact that most of the blog post is written by an LLM, I like that they provide a python sdk. I dont believe vercel does for their sandbox product.
I can't ignore that fact. The post was suffocating to read. LLMs have an obnoxious style.