[Feature Request] Improve shell command approval UX with better analysis and safety mechanisms

Bug Description
Claude prompts for approval of shell commands. I understand that the shell is powerful and dangerous--even destructive. Still, the current solutions does not work. Even an experienced developer like me can't parse complex shell commands well. Worse, nearly all of them are fine which creates muscle memory to approve everything. This needs to be much better and still safe.

At least add some context on what Claude intends the command to do to facilitate human review.

Example shell command:

cd /Volumes/Userdata/Users/clarke/dev/+2026/cto-sales/docs/tracker/app; (bun dev >/tmp/tracker-dev.log 2>&1 &); sleep 7; for i in 1 2 3 4 5; do code=$(curl -s -o /dev/null -w
"%{http_code}" http://localhost:3000/ 2>/dev/null); [ "$code" = "200" ] && break; sleep 3; done; echo "page: HTTP $code"
Start dev server

Contains shell syntax (&) that cannot be statically analyzed

Environment Info

• Platform: darwin
• Terminal: vscode
• Version: 2.1.156
• Feedback ID: b975dc2b-5f29-4a30-8204-d79fa9875673

Errors

[]