[FEATURE] Explain commands that need permission in plain language

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

Claude Code regularly asks for permission to run commands. My idea is to have it say in plain language what the command is doing right alongside/underneath it. I think it does currently say its motivation, but explaining what the command is doing would be helpful, particularly for commands a dev isn't familiar with, or for tired devs doing a lot of context switching :)

Proposed Solution

Each permission prompt should include a brief plain-English explanation of what the command does and why Claude Code is running it, displayed directly above or below the raw command.

Example - current:

gh pr create --base main --head feature/refactor --title "Decouple voice pipeline modes"

Example - proposed:

Creating a GitHub pull request from your feature/refactor branch into main
> gh pr create --base main --head feature/refactor --title "Decouple voice pipeline modes"

The explanation should be:

• One line, conversational, no jargon
• Covers both what the command does and why it's being run in the current context
• Generated by Claude Code itself (it already knows the intent since it chose to run the command)
• Shown for all permission prompts, not just destructive ones

This would be especially helpful when running multiple parallel sessions, reviewing long-running tasks after stepping away, or when the command involves tools the developer doesn't use regularly (e.g., xcrun simctl, detox, complex git operations).

Alternative Solutions

It's not a must, just an idea I thought might be useful.

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

See above.

Additional Context

N/A