Skip to main content

​
Creating a Sandbox

oc create (shortcut for oc sandbox create) provisions a new sandbox VM: 
oc create
oc create --timeout 600 --cpu 2 --memory 2048 --env NODE_ENV=production
The sandbox ID is printed on success. Use --json to capture it programmatically: 
ID=$(oc create --json | jq -r '.sandboxID')

​
Listing & Inspecting

# List all sandboxes
oc ls

# Detailed info for a specific sandbox
oc sandbox get sb-abc123
oc ls shows a table with ID, template, status, CPU, memory, and age. Add --json for machine-readable output.

​
Hibernation & Wake

Save state and stop paying for compute. Wake resumes the same sandbox — the platform attempts fast snapshot restore with a cold-boot fallback if needed. 
oc sandbox hibernate sb-abc123

# ... hours later ...
oc sandbox wake sb-abc123
oc shell sb-abc123
The sandbox keeps the same ID across hibernate/wake cycles. Preview URLs remain active.

​
Adjusting Timeout

The idle timeout resets on every operation (exec, file access, agent activity). Default: 0 — persistent, never auto-hibernates. Set a positive value (or 0 to disable) with oc sandbox set-timeout. 
oc sandbox set-timeout sb-abc123 3600  # 1 hour

​
Killing a Sandbox

oc sandbox kill sb-abc123
All data is lost unless you’ve created a checkpoint first.

​
Common Patterns

​
Create and Shell In

oc shell $(oc create --json | jq -r '.sandboxID')

​
Filter Running Sandboxes

oc ls --json | jq '.[] | select(.status == "running") | .sandboxID'

​
Batch Cleanup

oc ls --json | jq -r '.[].sandboxID' | xargs -I{} oc sandbox kill {}
SDK usage: Sandboxes. Full flags: CLI Reference.