Context & Problem Statement
Volume allows the agent to save its progress, code, and outputs safely after the sandbox is shut down or destroyed, which helps "Persistence". A single volume can be mounted to multiple sandboxes over time, allowing different environments to share state or access the same base dataset across different sandbox.
Currently, the Agent Sandbox only supports volume management at the infrastructure level (via YAML configurations like the volumeClaimTemplates field in the Kubernetes Sandbox object). To provide a developer-friendly experience, we fundamentally need native SDK support for managing filesystem volumes (persistent volumes).
Desired Behavior
We want to introduce SDK-level volume management so developers can create and mount volumes directly from their code without having to touch the underlying Kubernetes infrastructure YAML.
Context & Problem Statement
Volume allows the agent to save its progress, code, and outputs safely after the sandbox is shut down or destroyed, which helps "Persistence". A single volume can be mounted to multiple sandboxes over time, allowing different environments to share state or access the same base dataset across different sandbox.
Currently, the Agent Sandbox only supports volume management at the infrastructure level (via YAML configurations like the volumeClaimTemplates field in the Kubernetes Sandbox object). To provide a developer-friendly experience, we fundamentally need native SDK support for managing filesystem volumes (persistent volumes).
Desired Behavior
We want to introduce SDK-level volume management so developers can create and mount volumes directly from their code without having to touch the underlying Kubernetes infrastructure YAML.