--dangerously-skip-permissions does not bypass Bash permission prompts (2.1.80)

Description

--dangerously-skip-permissions flag does not suppress permission prompts for Bash tool calls. Every Bash command still triggers "Do you want to proceed?" with options 1 (Yes), 2 (Yes and don't ask again), 3 (No).

This defeats the purpose of the flag. Users managing multiple machines cannot maintain per-machine settings.json allow-lists as a workaround — the flag should handle this.

Steps to Reproduce

1. Launch: claude --dangerously-skip-permissions
2. Ask Claude to run any Bash command (e.g., curl, ssh, ls)
3. Permission prompt appears despite the flag

Evidence

• Verified via ps aux that process runs with --dangerously-skip-permissions
• settings.json has skipDangerousModePermissionPrompt: true
• settings.json permissions allow list is empty (as it should be — the flag should bypass all)
• Approved permissions accumulate in settings.local.json during the session, confirming prompts are being shown

Expected Behavior

Zero permission prompts. The flag says "Bypass all permission checks."

Actual Behavior

Every Bash command prompts for approval. Pressing "2" (don't ask again) only suppresses that specific command pattern, not all commands.

Environment

• Claude Code 2.1.80
• Linux (Ubuntu 24.04)
• Terminal (not VS Code)

Related Issues

• #32559
• #35718
• #28506

Impact

Users managing multiple machines (DevOps, sysadmin) cannot work efficiently. The workaround of maintaining allow-lists in settings.json across all machines is not scalable and accumulates garbage entries in settings.local.json.