[FEATURE] Auto-approve WebSearch tool without prompts via permissions configuration

Resolved 💬 5 comments Opened Nov 17, 2025 by vzakharov Closed Dec 23, 2025

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

When using the Claude Code plugin, the WebSearch tool always prompts for user approval before executing, unlike other tools (Bash, Edit, Read, WebFetch) which can be auto-approved via the permissions configuration in settings.json.

This creates workflow friction when I want Claude to autonomously research information during tasks.

Currently, the permissions system supports auto-approval for:

  • Bash commands
  • File operations (Edit, Read, Write)
  • WebFetch (for specific domains)
  • MCP tools

But WebSearch is conspicuously absent from this list, forcing manual approval for every search query even when I've configured other tools to run automatically.

Proposed Solution

Add WebSearch to the permissions configuration system with syntax similar to other tools:

{
  "permissions": {
    "allow": [
      "WebSearch",
      "WebSearch(query:*)",
    ]
  }
}

This would allow users to:
Auto-approve all web searches: "WebSearch"
Auto-approve searches matching patterns: "WebSearch(query:documentation)"
Set query limits: "WebSearch(max_queries_per_session:10)"
The configuration would work exactly like existing tool permissions - users could choose allow, deny, or ask (default) modes.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

Interactive mode (TUI)

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗