Capture a snapshot from a sandbox
Create a snapshot by capturing the current state of a sandbox or promoting an existing checkpoint.
Authorizations
Path Parameters
Sandbox display name
Body
if omitted, creates a fresh checkpoint from the running VM
Must be true when the included settings hold literal secret values (opaque values rather than workspace secret references, and any env var value), acknowledging that the snapshot stores them and every sandbox created from it can use them.
Description says what this snapshot's image can do, so a caller can hand it to an agent as a capability summary. At most 1024 characters.
1024sandbox-local Docker image to export
required for Docker image export unless the sandbox has a capacity
ImageConfig sets the command and ports the snapshot records, as a Docker image's ENTRYPOINT, CMD and EXPOSE do. By default a capture keeps those of the snapshot the sandbox was created from; each field given here replaces that one, and an empty list clears it. A function serving the snapshot runs this command and listens on its one exposed port.
Sandbox settings to carry into the snapshot. Sandboxes created from it start with each carried setting their create request leaves unset: "mounts" (the mount_config, with its auth), "proxy_config", "env_vars", "resources" (CPU and memory), "lifecycle" (idle_ttl_seconds, delete_after_stop_seconds, preserve_memory_on_stop), and "labels" (merged under this request's labels; reserved com.langchain.* labels are left out). "all" names every one of these. VM memory is captured with include_memory, not here. Warning: mounts, proxy_config and env_vars carry the sandbox's credentials, and every sandbox created from the snapshot can use them.
all, mounts, proxy_config, env_vars, resources, lifecycle, labels IncludeMemory, when true, captures a full VM memory snapshot alongside the filesystem clone. Only honored when the sandbox is running AND Checkpoint is omitted (i.e. a fresh in-VM checkpoint is requested). Defaults to false to keep snapshots small unless memory restore is explicitly desired.
Labels seed the captured snapshot's labels.
RunConfig overrides the runtime configuration the snapshot carries: for a docker_image export, the image's USER, WORKDIR and ENV; for a capture of the running VM, the sandbox's own. user and work_dir replace, env_vars merge.
mutable Docker-style tag; defaults to "latest"
Response
Created
Description says what this snapshot's image can do, so a caller can hand it to an agent as a capability summary.
The settings this snapshot carries, in include terms: sandboxes created from it start with each one their create request leaves unset. Env var values are never returned.
mounts, proxy_config, env_vars, resources, lifecycle, labels MemorySnapshotSizeBytes is non-nil iff the snapshot was captured with VM memory state. A non-nil value is the canonical signal that this snapshot can warm-restore from memory; nil means rootfs only.
The mount_config sandboxes created from this snapshot start with when their create request has none, with secret values redacted. Present only on snapshots captured with include "mounts" or "all" from a sandbox that had mounts.
The proxy_config sandboxes created from this snapshot start with when their create request has none, with secret values redacted. Present only on snapshots captured with include "proxy_config" or "all".
RunConfig is what sandboxes from this snapshot boot with. Absent on snapshots built before it was recorded, which run as root with their own env.
Tags currently resolving to this snapshot, under Name. A snapshot with no tags is dangling — addressable only by id.

