[FEATURE] Include bypassPermissions mode in default Shift+Tab permission mode cycling

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

Currently, Claude Code only exposes 3 permission modes when cycling via Shift+Tab:

Default
Accept Edits
Plan

The 4th mode (bypassPermissions) is only accessible via:

The --dangerously-skip-permissions CLI flag
Manually configuring "defaultMode": "bypassPermissions" in settings.json

This creates an inconsistent experience where users who want bypass mode must either:

Type a long CLI flag every session
Discover and manually edit their settings.json

Proposed Solution

Include bypassPermissions as the 4th option in the Shift+Tab permission mode cycle by default.
Current behavior:
Default → Accept Edits → Plan → Default...
Proposed behavior:
Default → Accept Edits → Plan → Bypass Permissions → Default...

Alternative Solutions

Add to ~/.claude/settings.json:
json{
"permissions": {
"defaultMode": "bypassPermissions"
}
}
This makes bypass mode accessible in the cycle, but requires users to know this config exists.

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

Developers working in isolated environments (Docker containers, sandboxed repos, personal projects) frequently want uninterrupted Claude execution. Currently they must:

Remember and type --dangerously-skip-permissions every launch, OR
Know to configure settings.json with the right key

Both add friction. Having bypass mode in the standard cycle lets users:

Quickly switch to bypass when needed
Easily switch back to safer modes without restarting
Discover the mode exists through normal usage

Additional Context

The mode is already fully implemented—it's just hidden from the default UI cycle
Users who configure defaultMode: "bypassPermissions" get 4 modes in their cycle, proving the UX works
A warning tooltip on first selection (similar to existing dangerous operation warnings) could mitigate safety concerns