[FEATURE]: webfetch allowed/blocked URLs #4495

Open
opened 2026-02-16 17:44:22 -05:00 by yindo · 3 comments
Owner

Originally created by @wolffberg on GitHub (Jan 9, 2026).

Originally assigned to: @thdxr on GitHub.

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Having the ability to allow/block certain URLs from webfetch would greatly improve security when using build mode.

Originally created by @wolffberg on GitHub (Jan 9, 2026). Originally assigned to: @thdxr on GitHub. ### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ### Describe the enhancement you want to request Having the ability to allow/block certain URLs from webfetch would greatly improve security when using build mode.
yindo added the discussion label 2026-02-16 17:44:22 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 9, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #5529: [FEATURE]: Add per-agent filesystem boundaries (allow/deny paths) + optional run-as user for bash - Comprehensive feature request for per-agent access controls that includes URL/fetch restrictions
  • #6318: [FEATURE]: Limit tool (e.g. write, edit) permissions to specific folders - Related feature for tool-level permission restrictions

These issues discuss broader security and access control features that may encompass or relate to URL filtering for webfetch.

Feel free to ignore if your specific use case isn't fully addressed by these existing discussions.

@github-actions[bot] commented on GitHub (Jan 9, 2026): This issue might be a duplicate of existing issues. Please check: - #5529: [FEATURE]: Add per-agent filesystem boundaries (allow/deny paths) + optional run-as user for bash - Comprehensive feature request for per-agent access controls that includes URL/fetch restrictions - #6318: [FEATURE]: Limit tool (e.g. write, edit) permissions to specific folders - Related feature for tool-level permission restrictions These issues discuss broader security and access control features that may encompass or relate to URL filtering for webfetch. Feel free to ignore if your specific use case isn't fully addressed by these existing discussions.
Author
Owner

@robertfall commented on GitHub (Jan 27, 2026):

I've taken a pass at implementing this in https://github.com/anomalyco/opencode/pull/8855

Not sure if there's anything else I need to do to submit it for review.

@robertfall commented on GitHub (Jan 27, 2026): I've taken a pass at implementing this in https://github.com/anomalyco/opencode/pull/8855 Not sure if there's anything else I need to do to submit it for review.
Author
Owner

@robertfall commented on GitHub (Feb 9, 2026):

Hi folks, just want to check if there's something that is outstanding here? Would really like to get this merged as it unblocks opencode use at $WORK as our policies require strict url allow listing.

@robertfall commented on GitHub (Feb 9, 2026): Hi folks, just want to check if there's something that is outstanding here? Would really like to get this merged as it unblocks opencode use at $WORK as our policies require strict url allow listing.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#4495