Permissions

Manage Claude Code tool permissions in project and global settings.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/AlexZan/task-fusion --skill permissions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Permissions
Source: https://github.com/AlexZan/task-fusion/tree/main/.claude/skills/Permissions
Command: npx skills add https://github.com/AlexZan/task-fusion --skill permissions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the complexity and potential for syntax errors when managing Claude Code tool permissions and settings. It automates the process of adding, modifying, or removing permissions and provides a robust debugging workflow for when permission prompts unexpectedly appear, saving you time and frustration.

Core Features & Use Cases

  • Automated Permission Configuration: Easily add, modify, or remove permissions for various tools like Bash commands (e.g., git, npm, gh, docker), WebFetch, WebSearch, and MCP servers.
  • Syntax Validation & Correction: Ensures all permissions are added with the correct syntax (e.g., Bash(tool:*) instead of Bash(tool *)), preventing common errors.
  • Intelligent Debugging: When a permission prompt appears, the Skill can analyze the command, check both global and project settings, identify missing or incorrect permissions, and even detect caching issues (e.g., .claude/settings.local.json).
  • Use Case: If Claude repeatedly asks for permission to run npm install, you can simply tell this Skill to "Stop asking me for npm permission," and it will correctly configure your settings.

Quick Start

Add a global permission to allow all git commands.

Frequently Asked Questions about Permissions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stop Claude Code from repeatedly asking for permission to run commands?

Configure permissions in .claude/settings.json by adding the tool with wildcard syntax (e.g., `Bash(git:*)` for all git commands). Claude Code will then execute those commands without prompting. If prompts persist, clear the settings cache in .claude/settings.local.json and restart VS Code.

What's the correct syntax for adding tool permissions in Claude Code settings?

Use wildcard notation with a colon: `Bash(tool:*)` for all commands of a tool, or `WebFetch:*` and `WebSearch:*` for web tools. Incorrect syntax like `Bash(tool *)` causes errors. The Skill validates and corrects these automatically during configuration.

Can I set different permissions globally and per-project in Claude Code?

Yes. Global permissions go in ~/.claude/settings.json and apply everywhere; project-level permissions in .claude/settings.json override them locally. The Skill manages both files and can debug conflicts between them, including caching issues via .claude/settings.local.json.

Why does Claude Code keep asking for permission even after I configured it?

Permission prompts can persist due to syntax errors, caching in .claude/settings.local.json, or settings not reloaded after restart. The Skill analyzes both global and project configurations, identifies missing or incorrect permissions, detects caching issues, and provides correction steps.

How do I add permissions for WebFetch, WebSearch, and MCP servers in Claude Code?

Add entries to .claude/settings.json or ~/.claude/settings.json using the format `WebFetch:*`, `WebSearch:*`, or `MCPServer(server_name:*)`. The Skill handles JSON structure validation and ensures proper syntax so permissions take effect without restart delays.

What permissions do I need to configure for common tools like git, npm, and docker?

Add permissions for each tool using `Bash(git:*)`, `Bash(npm:*)`, `Bash(docker:*)` in your settings file. The Skill automates this configuration and validates the JSON structure, allowing all commands for those tools without repeated permission prompts.