From 2f7364a8aaf2c7c81aa3da06e5251bbce4d6d0c9 Mon Sep 17 00:00:00 2001 From: c <37263590+Aphroq@users.noreply.github.com> Date: Sat, 9 May 2026 15:27:50 +0000 Subject: [PATCH 1/2] Document sandbox archive limits --- docs/sandbox/guide.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/sandbox/guide.md b/docs/sandbox/guide.md index 2f13bdf469..7e1e5f0c0c 100644 --- a/docs/sandbox/guide.md +++ b/docs/sandbox/guide.md @@ -481,6 +481,8 @@ These options only matter when the runner is creating a fresh sandbox session: `concurrency_limits` controls how much sandbox materialization work can run in parallel. Use `SandboxConcurrencyLimits(manifest_entries=..., local_dir_files=...)` when large manifests or local directory copies need tighter resource control. Set either value to `None` to disable that specific limit. +`archive_limits` controls SDK-side resource checks for archive extraction. Use `SandboxArchiveLimits(max_input_bytes=..., max_extracted_bytes=..., max_members=...)` when archives need tighter resource control. Set `archive_limits=None` to keep the default behavior with no SDK archive resource limits, or set an individual value to `None` to disable that specific limit. + A few implications are worth keeping in mind: - Fresh sessions: `manifest=` and `snapshot=` only apply when the runner is creating a fresh sandbox session. From 83be1660177ab5d0e93eed5bcdaadc0eb0f99050 Mon Sep 17 00:00:00 2001 From: c <37263590+Aphroq@users.noreply.github.com> Date: Sat, 9 May 2026 15:43:39 +0000 Subject: [PATCH 2/2] Clarify sandbox archive limits docs --- docs/sandbox/guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sandbox/guide.md b/docs/sandbox/guide.md index 7e1e5f0c0c..a5a2979daf 100644 --- a/docs/sandbox/guide.md +++ b/docs/sandbox/guide.md @@ -481,7 +481,7 @@ These options only matter when the runner is creating a fresh sandbox session: `concurrency_limits` controls how much sandbox materialization work can run in parallel. Use `SandboxConcurrencyLimits(manifest_entries=..., local_dir_files=...)` when large manifests or local directory copies need tighter resource control. Set either value to `None` to disable that specific limit. -`archive_limits` controls SDK-side resource checks for archive extraction. Use `SandboxArchiveLimits(max_input_bytes=..., max_extracted_bytes=..., max_members=...)` when archives need tighter resource control. Set `archive_limits=None` to keep the default behavior with no SDK archive resource limits, or set an individual value to `None` to disable that specific limit. +`archive_limits` controls SDK-side resource checks for archive extraction. Set `archive_limits=SandboxArchiveLimits()` to enable the SDK default thresholds, or pass explicit values such as `SandboxArchiveLimits(max_input_bytes=..., max_extracted_bytes=..., max_members=...)` when archives need tighter resource control. Leave `archive_limits=None` to keep the default behavior with no SDK archive resource limits, or set an individual field to `None` to disable only that limit. A few implications are worth keeping in mind: