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

Status Fixed / completed
Maintainer reply None cached
Activity 5 comments · opened Nov 17, 2025 · 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 ↗

5 Comments

ryanackley · 8 months ago
  1. Ask Claude Code to plan how to use library X.
  2. Starts to work.
  3. Go make a coffee
  4. Come back 15 minutes later. It's been waiting for permission to search "How do I use library X" the entire 15 minutes
  5. Click "Yes" thirty times while letting it do research.
  6. Why can't we just give it permissions to search the web?
vzakharov · 8 months ago

It gets worse because when the agent instructs a secondary agent to execute a task, that secondary agent can’t search web _at all_, because (as far as I understand) its “don’t ask” mode prohibits it from sending any confirmation messages to the user.

<img width="531" height="294" alt="Image" src="https://github.com/user-attachments/assets/ec52bfa7-51cc-4a92-bc8f-327071921b31" />

johnbillion · 8 months ago

Looks like this got implemented. The following config means CC doesn't prompt for web searches or web fetches:

{
  "permissions": {
    "allow": [
      "WebFetch",
      "WebSearch"
    ]
  }
}
vzakharov · 8 months ago

Confirmed, it doth work! Thx for the heads up, @johnbillion!

(Just to be clear, the settings I edited are in .claude/settings.local.json in the project dir.)

<img width="537" height="373" alt="Image" src="https://github.com/user-attachments/assets/53076895-4dda-4ac3-a31b-119c886454a5" />

github-actions[bot] · 8 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.