Plan mode causes unnecessary permission stalling on read-only actions

Description

When in plan mode, Claude frequently prompts for permission to perform read-only actions (glob, grep, read files, run ls) that have zero risk. This creates a frustrating stop-and-go experience where the user has to repeatedly approve harmless operations just to let Claude gather context for planning.

The user perception is that Claude is artificially stalling or padding the interaction rather than making progress. As one user put it: "it feels like you purposely make up things to ask permissions for just to take a break."

Expected behavior

Read-only operations within the project directory and its dependencies should not require permission prompts, especially in plan mode where the entire point is research and analysis. Claude should bias toward action on safe operations and only pause for genuinely risky or irreversible actions.

Actual behavior

Claude asks for permission on:

• Reading files in the working directory
• Running ls, cat, head via Bash
• Glob/Grep searches
• Running --help on CLI tools

This happens even when the user has configured broad read permissions.

Reproduction

1. Open Claude Code in plan mode
2. Ask it to plan a feature that requires exploring the codebase
3. Observe repeated permission prompts for read-only file operations

Environment

• Claude Code CLI
• macOS
• Plan mode enabled via settings

---
Reported via Claude Code