363
(deno.com)
simonw | 10 hours ago | 3 Comment
from deno_sandbox import DenoDeploy
sdk = DenoDeploy()
with sdk.sandbox.create() as sb:
# Run a shell command
process = sb.spawn("echo", args=["Hello from the sandbox!"])
process.wait()
# Write and read files
sb.fs.write_text_file("/tmp/example.txt", "Hello, World!")
content = sb.fs.read_text_file("/tmp/example.txt")
print(content)
Looks like the API protocol itself uses websockets: https://tools.simonwillison.net/zip-wheel-explorer?package=d...Show Reply 3 [+]
emschwartz | 10 hours ago | 14 Comment
> 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.
That seems clever.
Show Reply 14 [+]
johnspurlock | 11 hours ago | 3 Comment
This isn’t the traditional “run untrusted plugins” problem. It’s deeper: LLM-generated code, calling external APIs with real credentials, without human review. Sandboxing the compute isn’t enough. You need to control network egress and protect secrets from exfiltration.
Deno Sandbox provides both. And when the code is ready, you can deploy it directly to Deno Deploy without rebuilding."
Show Reply 3 [+]
chacham15 | 3 hours ago | 1 Comment
Now that I think further, doesnt this also potentially break HTTP semantics? E.g. if the key is part of the payload, then a data.replace(fake_key, real_key) can change the Content Length without actually updating the Content-Length header, right?
Lastly, this still doesnt protect you from other sorts of malicious attacks (e.g. 'DROP TABLE Users;')...Right? This seems like a mitigation, but hardly enough to feel comfortable giving an LLM direct access to prod, no?
_pdp_ | 1 hour ago | 1 Comment
We recently built our own sandbox environment backed by firecracker and go. It works great.
For data residency, i.e. making sure the service is EU bound, there is basically no other way. We can move the service anywhere we can get hardware virtualisation.
As for the situation with credentials, our method is to generate CLIs on the fly and expose them to the LLMs and then they can shell script them whichever way they want. The CLIs only contain scoped credentials to our API which handles oauth and other forms of authentication transparently. The agent does not need to know anything about this. All they know is that they can do
$ some-skillset search-gmail-messages -q "emails from Adrian"
In our own experiments we find that this approach works better and it just makes sense given most of the latest models are trained as coding assistants. They just love bash, so give them the tools.
koolala | 8 hours ago | 1 Comment
yakkomajuri | 6 hours ago | 3 Comment
So many sandbox products these days though. What are people using in production and what should one know about this space? There's Modal, Daytona, Fly, Cloudflare, Deno, etc
Show Reply 3 [+]
zenmac | 9 hours ago | 2 Comment
The real question is can the microVMs run in just plain old linux, self-hosted.
Show Reply 2 [+]
ttoinou | 10 hours ago | 4 Comment
Why limit the lifetime on 30 mins ?
Show Reply 4 [+]
ATechGuy | 9 hours ago | 3 Comment
How to know what domains to allow? The agent behavior is not predefined.
Show Reply 3 [+]
- | 3 hours ago | 1 Comment
nihakue | 10 hours ago | 3 Comment
Will give these a try. These are exciting times, it's never been a better time to build side projects :)
Show Reply 3 [+]
dangoodmanUT | 7 hours ago | 1 Comment
Those limitations from other tools was exactly why I made https://github.com/danthegoodman1/netfence for our agents
e12e | 10 hours ago | 1 Comment
Looks like the main innovation here is linking outbound traffic to a host with dynamic variables - could that be added to deno itself?
Tepix | 10 hours ago | 3 Comment
Just an idea…
Show Reply 3 [+]
WatchDog | 6 hours ago | 1 Comment
- | 3 hours ago | 1 Comment
mrpandas | 9 hours ago | 5 Comment
Show Reply 5 [+]
Bnjoroge | 6 hours ago | 1 Comment
snehesht | 9 hours ago | 1 Comment
MillionOClock | 8 hours ago | 2 Comment
Show Reply 2 [+]
eis | 1 hour ago | 1 Comment
It's about 10x what a normal VM would cost at a more affordable hoster. So you better have it run only 10% of the time or you're just paying more for something more constrained.
A full month of runtime would be about $50 bucks for a 2vCPU 1GB RAM 10GB SSD mini-VM that you can get easily for $5 elsewhere.
latexr | 7 hours ago | 2 Comment
That website does exist. It may hurt your eyes.
Show Reply 2 [+]
LAC-Tech | 8 hours ago | 1 Comment
I really like it. Startup times are now better than node (if not as good as bun). And being able to put your whole "project" in a single file that grabs dependencies from URLs reduces friction a surprising amount compared to having to have a whole directory with package.json, package-lock.json, etc.
It's basically my "need to whip up a small thing" environment of choice now.
eric-burel | 8 hours ago | 1 Comment
EGreg | 7 hours ago | 1 Comment
It uses web workers on a web browser. So is this Deno Sandbox like that, but for server? I think Node has worker threads.
bopbopbop7 | 8 hours ago | 1 Comment
andrewmcwatters | 10 hours ago | 1 Comment