[origin-review] anomalyco/opencode#46812 — CHECK

[kvnloo]

Why this matters

Hard-coded webfetch caps block legitimate large pages and give no config escape hatch.

Evidence

Tip bfb162f389a89b807cd5b538a9c3c7c1169816ef:

• Leaf: packages/opencode/test/tool/webfetch.test.ts (resolveMaxResponseSize)
• Live: tip webfetch.test.ts 8/8 pass
• Evidence class: BEHAVIORAL

Invariant: Webfetch max response size defaults to 5MB and honors config / OPENCODE_WEBFETCH_MAX_SIZE; invalid env values fall back safely.

Ask (design, light) — prospective; non-blocking

1. Should max size be per-tool config only, or also a session override?
2. For never-again: should image attachment paths share the same size resolver?

---

---

Fork mirror of a sealed OSS review draft. Not posted upstream.

• origin: feat: make webfetch max response size configurable anomalyco/opencode#46812
• tip: bfb162f389a89b807cd5b538a9c3c7c1169816ef
• evidence: BEHAVIORAL — tip packages/opencode/test/tool/webfetch.test.ts → 8/8 pass incl. resolveMaxResponseSize (log: cmds/pack25/46812-webfetch.log)
• pack: 05 draft 013
• dedupe_key: anomalyco/opencode#46812
• github_writes_origin: 0

[kvnloo]

RECON — issue says completed, candidate PRs closed

anomalyco#15459 is closed as completed, but the referenced anomalyco#46799 and this anomalyco#46812 are both closed. Before generating any more evidence, establish what actually landed.

1. inspect current upstream dev for a webfetch response-size configuration/env override;
2. identify the commit/PR that owns it, if present;
3. run the current test for default 5 MB + override + invalid-value fallback;
4. if the feature is already on dev, close this mirror as absorbed and link the landed owner;
5. if it is absent despite the issue being closed, report the mismatch and open a fresh current-dev repair only after checking newer PRs.

Do not promote stale anomalyco#46812 evidence until current-code provenance is known.

[kvnloo]

RECON RESULT — MISMATCH: issue closed completed, feature absent on tip

Provenance

• Origin feature issue #15459 closed completed (closer claimed “Addressed in feat: make webfetch max response size configurable anomalyco/opencode#46799”).
• Candidate PRs closed unmerged: #46799, #46812, earlier #36863.
• Tip 696f41bc8e packages/opencode/src/tool/webfetch.ts still hardcodes const MAX_RESPONSE_SIZE = 5 * 1024 * 1024.
• No resolveMaxResponseSize, no OPENCODE_WEBFETCH_MAX_SIZE, no config.webfetch.max_response_size in tip schema (packages/core/src/v1/config/config.ts).
• Tip webfetch.test.ts has image/text/svg cases only — no default/override/invalid-env suite.

Newer PRs checked

Open webfetch PRs (anomalyco#47460 timeout, anomalyco#49326 html media, anomalyco#45906 xhtml, …) do not land max-size config. No owning landed commit/PR.

Conclusion

Mismatch — do not absorb this mirror as done. Stale anomalyco#46812 evidence is not tip-true.

Fresh fork repair (in flight)

Branch: feat/webfetch-max-size-v3 → https://github.com/kvnloo/opencode/tree/feat/webfetch-max-size-v3

Intended delta (from sealed anomalyco#46812, rebased to tip):

• resolveMaxResponseSize (config → env → 5MB; invalid env → default)
• config schema webfetch.max_response_size
• tests: default 5MB + override + invalid fallback

Commit push pending (box disk / App 403); branch at tip ready.

[kvnloo]

Report blob (batch-a/opencode-57.md)

# A7 — kvnloo/opencode#57 webfetch size RECON

- **Status:** mismatch (do not absorb as done)
- **Tip:** 696f41bc8e — MAX_RESPONSE_SIZE still hardcoded 5MB; no resolveMaxResponseSize / OPENCODE_WEBFETCH_MAX_SIZE / config.webfetch
- **Recon comment:** https://github.com/kvnloo/opencode/issues/57#issuecomment-5841719342
- **Fork branch:** https://github.com/kvnloo/opencode/tree/feat/webfetch-max-size-v3
- **Provenance:** #15459 closed completed claiming #46799; #46799/#46812/#36863 closed unmerged; no landed owner
- **Tests:** tip webfetch.test.ts has no default/override/invalid suite (cannot run absent feature)
- **Repair:** port sealed #46812 (resolveMaxResponseSize + schema + tests). Commit pending box disk full.

[kvnloo]

RESULT — done (fork repair; NOT upstream-absorbed)

Mismatch confirmed on tip: 5MB still hardcoded; origin anomalyco#46799/anomalyco#46812 closed unmerged. Fork repair landed only.

• PR: feat(webfetch): configurable max response size #63 (feat/webfetch-max-size-v3 → dev)
• Commit: d568537 on tip 696f41bc8e
• Delta: resolveMaxResponseSize (config webfetch.max_response_size → OPENCODE_WEBFETCH_MAX_SIZE → 5MB default; invalid env → default); schema + tests

Test evidence

cd packages/opencode && bun test test/tool/webfetch.test.ts
(pass) resolveMaxResponseSize > defaults to 5MB
(pass) resolveMaxResponseSize > uses configured max_response_size
(pass) resolveMaxResponseSize > falls back to OPENCODE_WEBFETCH_MAX_SIZE when config unset
(pass) resolveMaxResponseSize > ignores invalid OPENCODE_WEBFETCH_MAX_SIZE values
  8 pass
  0 fail
Ran 8 tests across 1 file.

Do not claim upstream absorbed. Origin writes=0.

[kvnloo]

Current-dev recon: REPAIR_CANDIDATE.

Origin anomalyco#46812 closed unmerged and anomalyco#15459 was marked completed, but current dev still contains:

const MAX_RESPONSE_SIZE = 5 * 1024 * 1024

and current code search finds no OPENCODE_WEBFETCH_MAX_SIZE override.

So the requested configurability does not appear absorbed.

Before writing:

1. search newer PRs/commits one last time;
2. if still unowned, rebuild the smallest current-dev implementation;
3. default remains 5 MiB;
4. positive config/env override works;
5. invalid/non-positive values fail/fallback according to current config conventions;
6. Content-Length and streamed-body enforcement use the same resolved limit;
7. regression must fail on current dev.

Treat the closed issue state as stale bookkeeping, not proof the feature landed.

[kvnloo]

Cleanup classification: REPAIR_REQUIRED — origin closed but current dev still needs the configurable webfetch-size repair. Keep this canonical review thread open until a fresh current-dev repair lands or the bug is proven gone.