[FEATURE] Allow disabling auto mode in user/project settings.json (not just managed-settings)

Problem

Auto mode was recently added as a permission mode in the Shift+Tab cycle. Users who don't want to use it currently have no way to remove it from the cycle at the user or project level.

The only supported toggle — permissions.disableAutoMode: \"disable\" — is only honored in managed settings (org-level admin policy):

• macOS: /Library/Application Support/ClaudeCode/managed-settings.json
• Linux/WSL: /etc/claude-code/managed-settings.json
• Windows: C:\\Program Files\\ClaudeCode\\managed-settings.json

These paths require root/admin write access and are intended for enterprise fleet management — not individual users who simply don't want auto mode appearing in their Shift+Tab cycle. Individual Pro/Max subscribers on personal machines shouldn't need to write to system policy paths to opt out of a feature.

Proposed solution

Honor permissions.disableAutoMode (or an equivalent key) in regular user and project settings as well:

• ~/.claude/settings.json (user)
• .claude/settings.json / .claude/settings.local.json (project)

{
  "permissions": {
    "disableAutoMode": "disable"
  }
}

When set, auto mode should be hidden from the Shift+Tab permission mode cycle and the \"Enable auto mode?\" confirmation prompt should not appear.

Precedence could follow the existing settings hierarchy (managed > project local > project > user), so an admin policy still wins where one exists.

Alternatives considered

• Just never confirm the prompt — works, but the \"Enable auto mode?\" prompt still appears when cycling modes, which is the exact friction the request is trying to remove.
• Abuse managed-settings.json as a single user — requires sudo, pollutes a system-wide policy path, and isn't the intended use.
• Filing this as an enhancement request — that's this issue.

Priority

Low

Category

Configuration and settings