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.

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?