Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Launch HN: Runtime (YC P26) – Sandboxed coding agents for everyone on a team

runtm.com

Post reply on HN
Print view View original

11–20 of 48 posts

Re: Launch HN: Runtime (YC P26) – Sandboxed coding agents for everyone on a team

#11

Post by cvolante »

nilirl wrote: post #3

Hi, this looks really powerful, in that it seems to have many use cases. One question I had: Does every sandbox change end (when ready for production) in a pull request? If marketing sends me a pull request and I hate the code, what's the flow like for me to fix it?

The sandbox’s lifecycle is independent of the PR so that the same user or someone else in your team, like an engineer can come back to the same session and keep building until the result is ready to merge. So you can choose to iterate on the first drafts on the same sandbox. Curious, what flow you envision in your case?

Re: Launch HN: Runtime (YC P26) – Sandboxed coding agents for everyone on a team

#12

Post by theahura »

Really cool! We're working on something similar over at https://norisessions.com/

A few questions

- you mention proxying keys. One issue that we run into is that there are a bunch of tools that are really useful but require keys to be on disk (e.g. aws cli -- yes yes you can do IAM permissions but still). How do you guys think about those? (Especially since your setup onboarding is 'just install from npm or mise')

- poking around on the github, saw that you guys were at one point on fly.io. Did you guys end up switching off them? What motivated that if so?

- the CLI integration is cool! Is that actually teleporting remote sessions down to a local machine? Or is it more a window into the remote sandboxes?

would love to share notes! If you want to get in touch separately feel free at amol at noriagentic dot com.

Re: Launch HN: Runtime (YC P26) – Sandboxed coding agents for everyone on a team

#16

Post by cvolante »

theahura wrote: post #12

Really cool! We're working on something similar over at https://norisessions.com/ A few questions - you mention proxying keys. One issue that we run into is that there are a bunch of tools that are really useful but require keys to be on disk (e.g. aws cli -- yes yes you can do IAM permissions but still). How do you guys think about those? (Especially since your setup onboarding is 'just install from npm or mise') -…

Nori looks really cool, will set up sometime to exchange notes. But with regards to your questions: - Proxying keys: We allow users to setup keys in the sandbox and use CLIs for some cases but we also support an egress gateway that intercepts and injects keys on the way out, which supports the major api integrations we offer. - We still allow fly.io for deployments (so after a sandbox has a final app, you can deploy it and move out of the ephemeral sandbox). We never used them for sandboxing, but we will integrate into https://sprites.dev/ soon. - For the CLI, we allow you to SSH into the remote sandox since a lot of workload add too much stress to local machines

Curious about what sandbox provider you use to power Nori and how you are handling the secrets/keys issue?

Re: Launch HN: Runtime (YC P26) – Sandboxed coding agents for everyone on a team

#19

Post by gustrigos »

agcat wrote: post #17

This is amazing, what was the inspiration?

thanks! we used to build a lot of internal software / scripts for conferences or one-off data crunching. We saw LLMs getting better and how the world would go from building software for localhost to needing it to deploy. I then wrote an essay about my thoughts as software goes to zero back in January. https://www.gustrigos.com/essays/on-abundant-ephemeral-softw...

Re: Launch HN: Runtime (YC P26) – Sandboxed coding agents for everyone on a team

#20

Post by gustrigos »

zuzululu wrote: post #14

Checked license it said copyrighted which makes this unsuable for me. my question is what advantage does this have over real FOSS agentic sandboxes

We're using a split license: apache-2.0 for the CLI/SDK/sandbox, MIT for templates, AGPLv3 for server components. Not copyrighted.

But beyond that, we are managing a higher level abstraction than sandboxes.

Post reply on HN