[BUG] "Accept and auto mode" shows "Permission mode couldn't be changed" warning when accepting a plan (Claude for Mac)

Proposed Solution: Fix Race Condition in "Accept and Auto Mode"

Root Cause

The "Accept and auto mode" action (⌘↵) performs two sequential operations:

1. Accept the proposed plan
2. Switch permission mode to "Auto"

The warning appears because of a race condition: the permission mode change is triggered before the plan acceptance fully completes its state transition. The mode switch API call receives a stale/conflicting state and returns an error, even though the mode eventually switches correctly.

Key evidence:

• Clicking plain "Accept" then manually switching to Auto does NOT trigger the warning
• The warning appears consistently with "Accept and auto mode" (combined action)
• The mode still switches correctly despite the warning (false positive)

Fix: Sequential Await with State Verification (Recommended)

// BEFORE (likely current code — parallel or non-awaited):
async function acceptAndAutoMode() {
  acceptPlan();           // Not awaited or fires-and-forgets
  setPermissionMode('auto');  // Fires before accept completes
}

// AFTER (sequential with state verification):
async function acceptAndAutoMode() {
  await acceptPlan();
  await waitForState(() => planAccepted);
  await setPermissionMode('auto');
}

Alternative: Optimistic UI with Error Suppression

Since the mode does switch correctly, verify before showing the warning:

async function acceptAndAutoMode() {
  await acceptPlan();
  try {
    await setPermissionMode('auto');
  } catch (error) {
    const currentMode = await getPermissionMode();
    if (currentMode === 'auto') {
      // False positive — mode switched successfully
      return;
    }
    throw error;
  }
}

Impact

• Severity: MEDIUM — cosmetic issue (warning is false positive), but user-facing
• Fix complexity: LOW — race condition fix, 5-15 lines
• Risk: LOW — purely sequential ordering change

Full solution: solutions/claude-code-60277-accept-auto-mode-permission-warning-fix.md

Update: The issue is not limited to "Accept and auto mode." Clicking plain "Accept" and then manually switching to Auto also triggers the same warning. Even switching to Bypass and then back to Auto reproduces it. The warning appears on any permission mode switch, not just during plan acceptance.

Was hitting something similar:

• Ran claude --permission-mode auto, acknowledged the risk
• Ensured "permissions" → "defaultMode": "auto" in ~/.claude/settings.json
• Opened Claude Desktop, saw auto:

<img width="528" height="128" alt="Image" src="https://github.com/user-attachments/assets/43194a93-eba1-4704-abf4-5c297e570f11" />

• Submitted a prompt, saw auto immediately jumping to Ask permissions. All attempts to return to auto with a dropwdown produced this:

<img width="466" height="64" alt="Permission mode couldn't be changed. You can try again." src="https://github.com/user-attachments/assets/678debfe-603f-40b3-b961-efec97037caf" />

I tried to re-login everywhere, update, reinstall - no luck. Then I bumped into this:
https://code.claude.com/docs/en/permission-modes#eliminate-prompts-with-auto-mode

Model: Claude Sonnet 4.6, Opus 4.6, or Opus 4.7 on Team, Enterprise, and API plans; Claude Opus 4.7 only on Max plans. Other models, including Haiku and claude-3 models, are not supported.

So in my case I was trying auto on Opus 4.6 on the Max plan which was not expected to work. I wish the UI was more informative here. It's clearly wrong to show auto next to Opus 4.6 if these options are incompatible in my case anyway. The notification is pretty useless too - it reads as if there's downtime or some other glitch in the system.

I won't get an hour of frustration back, but hope this helps someone.

It seems the bug is really: when you change to a model which doesn't support the mode you're in, please give the user an informative message that Model ... doesn't support auto/bypass. rather than giving a message without any hope for the user, but to land here on this page.

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.