3 ms·

Show HN: Cloud Playgrounds for AI Agents and Copilots

13 points by mlejva 3y ago

mlejva 3y ago
Hey HN, We've been building cloud for AI agents/copilots/AI apps. One of the first products that we're launching are AI Playgrounds. It's essentially a sandboxed VM (Firecracker [0]) where your agent can freely run code, use filesystem, use headless browser, and more. Every playground has also it's own URL. So for example you can have your agent start a webapp, let the agent work on it inside the playground, and because the playground has URL, the user can see all of the changes. We've seen that it's especially useful for coding copilots and agents. They can easily run linters, formatters, or debug code and feed all this information back to LLM to make the next iteration better. Our short-term goal is to offer coding agents/copilots all of the tooling that human developers get in their coding editors. And have all of this happen in a secure sandboxed environment that people will eventually be able to self-host it. You don't need to manage any infrastructure. You just call a single line of code with our SDK and we spin up a cloud playground in a few hundred ms for your AI app. We have parts of our product open source here https://github.com/e2b-dev https://github.com/e2b-dev and are thinking of actually open-sourcing the whole infrastructure and make it really easy to 1-click deploy for anyone. One of the reasons we haven't done that is how much tooling we had to build on top Firecrackers and how much specialized environment they need. Which makes it a bit of challenge to offer great DX. Happy to answer more questions! [0] https://github.com/firecracker-microvm/firecracker https://github.com/firecracker-microvm/firecracker
DonQYYDS 3y ago
This looks great!
- mlejva 3y ago
  Thanks!
terezatizkova 3y ago
Amazing! What is the logic behind doing this with firecrackers vs other solutions? From what I understood, it is especially helpful for the use-case of coding agents, as firecrackers are good fit for running untrusted code. But how exactly that works and are there any alternatives that you considered?

13 points by mlejva 3y ago

Hey HN, We've been building cloud for AI agents/copilots/AI apps. One of the first products that we're launching are AI Playgrounds. It's essentially a sandboxed VM (Firecracker [0]) where your agent can freely run code, use filesystem, use headless browser, and more. Every playground has also it's own URL. So for example you can have your agent start a webapp, let the agent work on it inside the playground, and because the playground has URL, the user can see all of the changes. We've seen that it's especially useful for coding copilots and agents. They can easily run linters, formatters, or debug code and feed all this information back to LLM to make the next iteration better. Our short-term goal is to offer coding agents/copilots all of the tooling that human developers get in their coding editors. And have all of this happen in a secure sandboxed environment that people will eventually be able to self-host it. You don't need to manage any infrastructure. You just call a single line of code with our SDK and we spin up a cloud playground in a few hundred ms for your AI app. We have parts of our product open source here https://github.com/e2b-dev https://github.com/e2b-dev and are thinking of actually open-sourcing the whole infrastructure and make it really easy to 1-click deploy for anyone. One of the reasons we haven't done that is how much tooling we had to build on top Firecrackers and how much specialized environment they need. Which makes it a bit of challenge to offer great DX. Happy to answer more questions! [0] https://github.com/firecracker-microvm/firecracker https://github.com/firecracker-microvm/firecracker

DonQYYDS 3y ago

This looks great!

mlejva 3y ago
Thanks!

terezatizkova 3y ago

Amazing! What is the logic behind doing this with firecrackers vs other solutions? From what I understood, it is especially helpful for the use-case of coding agents, as firecrackers are good fit for running untrusted code. But how exactly that works and are there any alternatives that you considered?