Hi, we would like to contribute our AIO Sandbox project image to OpenShell community.
AIO Sandbox & NVIDIA OpenShell seem to complement each other quite well. AIO Sandbox provides rich built-in agent capabilities such as browser automation, shell access, file operations, VS Code Server, and MCP integration. It provides inner execution environment where the agent actually performs work.
OpenShell, on the other hand, provides the secure outer runtime boundary: sandbox lifecycle management, policy enforcement, controlled networking, and operational governance.
Please see the detail blog we recently published to this regards.
https://medium.com/@dvij_sj12/inside-aio-sandbox-part-3-integrating-aio-sandbox-with-nvidia-openshell-661900449aba?postPublishedType=repub
One question I have regarding the contribution process. Instead of including the detail execution steps in the DOCKERFILE, could we just specify the original image instead (ghcr.io/agent-infra/sandbox:latest).
Look forward to hearing from you. Thanks.
Hi, we would like to contribute our AIO Sandbox project image to OpenShell community.
AIO Sandbox & NVIDIA OpenShell seem to complement each other quite well. AIO Sandbox provides rich built-in agent capabilities such as browser automation, shell access, file operations, VS Code Server, and MCP integration. It provides inner execution environment where the agent actually performs work.
OpenShell, on the other hand, provides the secure outer runtime boundary: sandbox lifecycle management, policy enforcement, controlled networking, and operational governance.
Please see the detail blog we recently published to this regards.
https://medium.com/@dvij_sj12/inside-aio-sandbox-part-3-integrating-aio-sandbox-with-nvidia-openshell-661900449aba?postPublishedType=repub
One question I have regarding the contribution process. Instead of including the detail execution steps in the DOCKERFILE, could we just specify the original image instead (ghcr.io/agent-infra/sandbox:latest).
Look forward to hearing from you. Thanks.