Launch HN: Freestyle – Sandboxes for Coding Agents
161–170 of 182 posts
Re: Launch HN: Freestyle – Sandboxes for Coding Agents
#162Re: Launch HN: Freestyle – Sandboxes for Coding Agents
#163Re: Launch HN: Freestyle – Sandboxes for Coding Agents
#164We run upwards of a thousand sandboxes for coding agents - but these are all standard VM's that we buy off the shelf from Azure, GCP, Akamai and AWS. I am not sure why we should use this instead of the standard VM's? Pricing could be one part, but not sure if the other features resonate.
Forking is interesting, but I would need to know how it works and if it is in the blast radius of the agent execution. If we need to modify the agent to be cognizant of forking, then that is a complexity which could be very expensive to handle in terms of context. If not, then I am not sure what is the use for it.
Sandbox start time at 500ms is definitely interesting. But its something we already are on track to reproduce with a pooled batch of VM's. So not sure if that in itself is worth paying for the premium.
My two cents on the space is that agents are rapidly becoming more capable to just use the tooling developed for humans. All clouds provide a CLI which agents can already use to orchestrate - they should just use the VM's designed for humans through the CLI. Our agent can already 'login' to any VM on the cloud and use the shell exactly like a human would. No software harness is required for this capability. The agent working on a VM is indistinguishable from humans.
Re: Launch HN: Freestyle – Sandboxes for Coding Agents
#165I was intrigued to try but your web app is so extremely slow, it takes up to 30+ seconds to move from one tab to the next. Not exactly selling your point of being a super fast provisioning service. Another thing I am wondering. You seem to be selling this as VMs configurable from node/bun. Wouldn't a CLI make more sense here? Another question: How hard do you think it'll be to integrate this with something like Claud…
I'm not sure what you saw as slow, I'd love to improve it. Do you mean the dashboard? We're built as an API for platforms to build on rather than tool for individual developers. Oriented at platform orchestrating tens of thousands at VMs rather than individuals using CLI. We also have a CLI but its primarily a debugging and testing tool. Resuming a freestyle VM with claude code in it will just work. You can do that v…
Switching tabs in the Dashboard (Domains/Routes/etc.) was basically unusable about 4 hours ago. It's noticeably better now, though there's still some latency (just retested).
Re: Launch HN: Freestyle – Sandboxes for Coding Agents
#166Re: Launch HN: Freestyle – Sandboxes for Coding Agents
#167Re: Launch HN: Freestyle – Sandboxes for Coding Agents
#168Re: Launch HN: Freestyle – Sandboxes for Coding Agents
#169Earlier quoted context omitted.
I disagree (as a sandboxing company). With respect to the market, every single sandbox sucks. I'm not gonna shit talk competitors but there is not a good sandboxing platform out there yet — including me — compared to where we'll be in 6 months. We've heard all the platforms have consistent uptime, feature completeness, networking and debugging issues. And in our own platform we're not 1/10ths of the way through solvi…
I don't think you're wrong, but if you really want to really re-think the approach, building an orchestration layer for Firecracker like every other company in the space is doing is probably not it.