Checked license it said copyrighted which makes this unsuable for me.

my question is what advantage does this have over real FOSS agentic sandboxes

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?

I have a suggestion - an assistant which can help to set up all these agents, perhaps based on templates. You already covered various use cases, but it's not clear if it's something concrete.

I think a lot of people who might be interested in this product might be interested in an easy set-up process. Even if it doesn't really save time for an experienced ops person, a lot of people would rather talk to a bot than fill a form.

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.

I wonder how this would be looked upon by the ever changing rules of claude code.

If someone from Anthropic sees this, would love to know if I can use my max plan here.

[dead]

[dead]