Early access for Agentbox v2 is here. Agents can keep the same project files across multiple runs and pause compute while they wait. Storage for paused sandboxes is free during early access.
An agent's work doesn't always end with its response. A user returns with feedback, a report needs another revision, or a coding task continues the next morning. The next run needs the files from the last one, but keeping the environment running through those gaps costs compute.
Agents can still create a sandbox for a single task, collect the result, and delete it. V2 adds the option to keep a project workspace between runs.
When an agent is done for now, it can save its progress and pause the sandbox. Compute stops, and saved files stay available.
When the next request arrives, your application resumes the sandbox so the agent can continue working from those files. The sandbox keeps the same ID, files, and configuration.
Resume restarts the environment and reruns its startup command. It does not restore memory or continue running processes. Progress needed by the next run must be saved to files before pausing.
Create, execute, upload, download, pause, resume, and delete are available through the SDK. Agents can use these operations as tools while they work.
sandbox.execute("pytest") # agent runs its task
sandbox.pause() # done for now — compute stops, files stay
# ...hours later, same sandbox, same files
sandbox.resume()
sandbox.execute("pytest") # picks up where it left offIf the agent runs inside the sandbox it pauses, an external application must initiate the resume. V2 also provides a maximum runtime set at launch, optional idle auto-pause, and deletion from any sandbox state.
Use a fresh sandbox for a one-off task, or keep the project files for the next run. Agentbox v2 supports both.
Compute is usage-based. Paused sandboxes consume no compute, and paused-sandbox storage is free during early access.
GMI Cloud helps you architect, deploy, optimize, and scale your AI strategies
