Raise execute-code materialization limits with skip logs - #968
Draft
Y1fe1Zh0u wants to merge 1 commit into
Draft
Conversation
Raise execute-code workspace materialization limits so ordinary binary documents remain available inside the sandbox, and log files skipped at either budget boundary. Constraint: Per-file materialization is capped at 50 MiB and aggregate materialization at 500 MiB. Rejected: Silently retain the 10 MiB limit | task inputs disappeared without actionable evidence. Confidence: high Scope-risk: narrow Directive: Keep skip logging when changing materialization budgets. Tested: 18 scoped storage-workspace tests; scoped test Ruff; git diff --check. Not-tested: Live deployment performance with a 500 MiB eligible workspace.
Y1fe1Zh0u
force-pushed
the
fix/execute-code-materialize-limits
branch
from
August 14, 2026 12:12
5fdf244 to
c88958a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Why
Binary task inputs larger than 10 MiB were silently omitted from the temporary sandbox. Storage APIs could list the file while
execute_codecould not see it, which made the failure look like an overlay or filesystem inconsistency.Impact
Documents up to 50 MiB can now be materialized for local tool execution, subject to a 500 MiB aggregate budget. Files outside either budget remain skipped, but the backend now records an actionable warning.
Validation
18 passedintests/test_agent_tools_storage_workspace.pygit diff --checkpassedKnown gap
Live deployment performance with a fully eligible 500 MiB workspace has not been measured.