[FEATURE] Allow wildcard permissions for WebSearch tool (like all other tools)

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Every tool in Claude Code supports wildcard permissions in settings files except
WebSearch. You can set Bash(.), Edit(.), Read(.), Grep(.), WebFetch(domain:*),
Task(.), etc — but WebSearch(.) is rejected on startup with:

WebSearch does not support wildcards. Use exact search terms without * or ?.
Examples: WebSearch(claude ai), WebSearch(typescript tutorial)

This means the entire settings file is skipped, breaking all other permissions too.

Expected behavior

WebSearch(.*) should be supported like every other tool, auto-allowing all searches
without prompting. WebSearch is read-only and low-risk — there's no reason it should
be treated differently from Grep(.) or Read(.).

Current workaround

Remove WebSearch from the allow list entirely and click "allow" on every single
search. This adds friction to every session.

Environment

• Claude Code 2.1.45
• Linux (Ubuntu)

Proposed Solution

WebSearch(.*) should be supported like every other tool, auto-allowing all searches
without prompting. WebSearch is read-only and low-risk — there's no reason it should
be treated differently from Grep(.) or Read(.).

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

WebSearch does not support wildcards. Use exact search terms without * or ?.
Examples: WebSearch(claude ai), WebSearch(typescript tutorial)

Additional Context

_No response_