Conversation
|
Thanks for updating your PR! It now meets our contributing guidelines. 👍 |
kvnloo
force-pushed
the
feat/webfetch-max-size-v3
branch
from
October 3, 2026 21:18
d568537 to
9949e18
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
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.
Summary
Make WebFetch's response-size cap configurable while keeping 5 MiB as the default.
webfetch.max_response_sizeaccepts a positive integer in bytesOPENCODE_WEBFETCH_MAX_SIZEis the fallback when config is unsetCredit / provenance
This carries forward the config design from upstream anomalyco#46812 / anomalyco#46799 by @RaviTharuma and the earlier environment-variable approach from anomalyco#36863 by @ulises-jeremias. This branch refreshes those ideas onto current
devand keeps the combined focused regression coverage.Current refresh
devon 2026-10-03Verification
The earlier focused downstream proof passed the WebFetch test file. Current upstream CI should revalidate this refreshed head.
github_writes_origin=0— ready to promote when upstream write access is available.