Permission confirmations block productivity - no practical way to allow safe commands

Bug Report: Claude Code Permission Confirmations Block Productivity

Date: 2026-01-20
Component: Claude Code CLI - Permission System

Problem

Read-only bash commands require manual confirmation. Examples:

• lsusb
• lsblk
• df
• ps
• cat

Each command stops execution and waits for user approval.

Impact

• Workflow constantly interrupted by confirmation prompts
• User must manually add each command to allow list
• This has been ongoing for weeks
• No practical way to allow all safe commands at once

Current Workaround

Manually adding entries to ~/.claude/settings.json:

"permissions": {
  "allow": [
    "Bash(lsusb:*)",
    "Bash(df:*)"
  ]
}

This does not scale.

Additional Issue: Claude Hallucination

When asked about alternatives (e.g., using a deny list instead), Claude stated that deny lists do not exist in Claude Code. This is false - deny lists do exist.

User had to correct Claude based on their own experience. Verifying the correct information required spawning an agent that consumed 35,000 tokens just to look up Claude Code's own documentation.

User time wasted correcting the model instead of doing actual work.