[Feature Request] Rethink shell expansion permission prompts - resolve or skip, don't prompt on undecidable strings
Bug Description
/bug
/feedback Rethink the "expansion" permission prompts. When a bash command contains a shell expansion — $(...), backticks, a glob — Claude Code can't statically determine what it'll resolve to, so it asks the human to approve it. But that's backwards: if it's complicated for a machine to gauge the result, it's just as impossible for the human staring at the same unresolved string. Asking a person to adjudicate something that's formally undecidable isn't a safety feature — it's passing an impossible question down the chain. Either resolve the expansion and show me the concrete command, or judge it by intent (like auto mode does) — but don't prompt me to rubber-stamp something neither of us can actually evaluate. 🤠
Environment Info
- Platform: darwin
- Terminal: Apple_Terminal
- Version: 2.1.210
- Feedback ID: 4a26406b-0edc-4254-abb3-eeeca0fe5216
Errors
[]