You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
webfetch permission with object syntax crashes server on startup #29041
Using the object/pattern syntax for the webfetch permission in opencode.jsonc causes the server to crash on startup with "Unexpected server error" for config.providers, provider.list, app.agents, and config.get. I had been looking to see if I could provide a curated list of URLs (domains) that would be allowed while requiring a prompt for everything else.
For most permissions, you can use an object to apply different actions based
on the tool input.
and show object syntax examples for bash and edit. It is unclear whether webfetch is expected to support object syntax or not. If it is, this is a bug;
if not, the docs should clarify which permissions support pattern matching.
Plugins
none
OpenCode version
1.15.10
Steps to reproduce
Add "webfetch": { "*": "ask" } to the permission section of opencode.jsonc
Run opencode
Observe:
Error: 4 of 5 requests failed: Unexpected server error. Check server logs for details.
Affected startup requests: config.providers, provider.list, app.agents, config.get
at vO (B:/~BUN/root/chunk-dk74dn3y.js:470:117)
at <anonymous> (B:/~BUN/root/chunk-dk74dn3y.js:470:5550)
at processTicksAndRejections (native:7:39)
Expected: Server starts normally and prompts on webfetch calls for URLs matching the patterns, OR docs explicitly state object syntax is not supported for this permission.
Your report is distinct in that you're observing a server crash rather than a config validation error, which may indicate a regression or a separate code path worth investigating.
Activity
github-actions commentedon May 23, 2026
This issue might be related to existing issues. Please check:
webfetchnot supporting the object/granular permission syntax (closed, but the underlying bug of a server crash may still be present)Your report is distinct in that you're observing a server crash rather than a config validation error, which may indicate a regression or a separate code path worth investigating.
github-actions commentedon Jul 23, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.