zlacker

>>simonw+(OP)
Here's the announcement on the Fly blog: https://fly.io/blog/code-and-let-live/ - and the Hacker News thread for that post: >>46557825

I wrote about this because it hits two of my current obsessions at once - developer environment sandboxes (for safely running Claude Code etc in YOLO mode) and APIs for executing untrusted code.

>>simonw+9
Stupid question but why not use a local sandbox for yolo mode instead of a remote machine.

Is there a similar service that runs locally?

>>aszen+fP2
That seems fine if you have a box that's running all the time and something like tailscale set up. I haven't bothered because I'm lazy, but I do want any coding agents I have off my laptop and off the local network, because I'm a little wary about them getting subverted. They need Internet access anyway, so might as well.

Since I anticipate using coding agents a lot, that means my dev environment is going to live in a VM in the cloud from now on.

>>skybri+3Y2
The big issue with this is though that GPUs are not available. I believe many people have local workstation boxes where they do dev on and need proper sandboxes and stuff like firecracker is also not super useful as afaik GPU passthrough is not ideal/working. Or any kinds of larger HW requirements.

>>ichiic+3i3
A workaround might be to copy a directory out with something like Syncthing so you can test locally. But then the coding agent can't help you. So yeah, I can see setting up a box for that. I'm doing web development so it's not an issue for me.

>>skybri+eX3
then all benefit from the sandbox is lost