Feature: Human-readable permission prompts for non-technical users

Problem

When Claude Code asks for permission to execute a tool, the prompt shows the raw technical command, e.g.:

Allow ls /Users/pete/project/src?

For developers, this is fine. But when non-technical users work with Claude Code (e.g. in business/ops contexts), these prompts are confusing and don't enable informed decisions. Users see shell commands they don't understand and either blindly approve everything or get stuck.

Proposed Solution

Allow customizing permission prompts to show human-readable descriptions instead of (or in addition to) raw commands. For example:

| Current | Proposed |
|---------|----------|
| ls /Users/pete/project/src | "I want to look at the contents of the src folder" |
| git diff HEAD~1 | "I want to see what changed in the last commit" |
| python3 run_tests.py | "I want to run the test suite" |

This could be implemented as:

• A setting like "permissionPromptStyle": "simple" that uses the description field (already provided by the model on Bash calls) as the primary prompt text instead of the raw command
• Or a hook-based mechanism where a PermissionRequest hook can modify the displayed prompt text before showing it to the user

Use Case

Organizations using Claude Code with mixed-technical teams — e.g. business analysts, ops staff, or managers who interact with Claude Code but aren't developers. Human-readable prompts would let them make genuinely informed approve/deny decisions instead of guessing.