Skip to content

Desktop app always starts sessions in "Accept Edits" mode instead of "Bypass Permissions", even though defaultMode: "bypassPermissions" is set in ~/.claude/settings.json #61436

Closed as not planned
Closed as not planned
Desktop app always starts sessions in "Accept Edits" mode instead of "Bypass Permissions", even though defaultMode: "bypassPermissions" is set in ~/.claude/settings.json#61436
Labels
area:desktoparea:permissionsbugSomething isn't workingduplicateThis issue or pull request already existsplatform:windowsIssue specifically occurs on WindowsstaleIssue is inactive

Description

@Lebedb233
Lebedb233
opened on May 22, 2026

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Desktop app always starts sessions in "Accept Edits" mode instead of "Bypass Permissions", even though defaultMode: "bypassPermissions" is configured in ~/.claude/settings.json

What Should Happen?

Sessions should start in Bypass Permissions mode as configured in settings.json

Error Messages/Logs

Warning: "Bypass Permissions mode isn't enabled. The session started in Accept Edits"
"Permission mode couldn't be changed. You can try again."

Steps to Reproduce

  1. Set ~/.claude/settings.json with "permissions": { "defaultMode": "bypassPermissions" }
  2. Enable "Allow bypass permissions mode" in Desktop Settings
  3. Run CLI with --dangerously-skip-permissions and accept
  4. Open desktop app → start new session
  5. Send any message

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.146

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

CLI works correctly — shows "bypass permissions on".
Desktop GUI ignores the same settings.json.
Mode reverts to "Accept Edits" after sending first message even if manually switched.
skipDangerousModePermissionPrompt: true is also set.

Activity

  1. Lebedb233
    added
    bugSomething isn't working
    on May 22, 2026
  2. github-actions
    added
    duplicateThis issue or pull request already exists
    platform:windowsIssue specifically occurs on Windows
    area:permissions
    area:desktop
    on May 22, 2026

  3. github-actions commented on May 22, 2026

    @github-actions
    github-actionsbot
    on May 22, 2026 – with GitHub Actions

    Found 3 possible duplicate issues:

    1. [BUG] Desktop: Bypass Permissions mode can't be enabled on macOS — reverts to Accept Edits, "Permission mode couldn't be changed" (2.1.148) #61415
    2. [BUG] Permission mode toggle broken on desktop app - "Permission mode couldn't be changed" – AUTO MODE not staying on #60724
    3. Desktop app launches claude with --permission-mode default hardcoded; auto mode toggle fails #61304

    This issue will be automatically closed as a duplicate in 3 days.

    • If your issue is a duplicate, please close it and 👍 the existing issue instead
    • To prevent auto-closure, add a comment or 👎 this comment

    🤖 Generated with Claude Code

  4. Lebedb233 commented on May 22, 2026

    @Lebedb233
    Lebedb233
    on May 22, 2026
    Author

    👍

  5. fifatest-cmd commented on May 25, 2026

    @fifatest-cmd
    fifatest-cmd
    on May 25, 2026

    Confirming this is still broken on the latest desktop build.

    Environment

    • Claude Code Desktop: 1.8555.2
    • Claude Code CLI: 2.1.150
    • macOS: 26.4.1 (Darwin 25.4.0, Apple Silicon)

    Repro

    1. Settings → Claude Code → "Allow bypass permissions mode" toggled ON.
    2. ~/.claude/settings.json has "permissions": { "defaultMode": "bypassPermissions" }.
    3. Project .claude/settings.json and .claude/settings.local.json also have "permissions": { "defaultMode": "bypassPermissions" }.
    4. No managed settings under /Library/Application Support/ClaudeCode/managed-settings.json.
    5. No disableBypassPermissionsMode anywhere.
    6. skipDangerousModePermissionPrompt: true is set in user settings.

    Expected
    Session starts in bypass mode (or at least bypass is selectable from the mode picker).

    Actual

    • Bypass mode does not appear in the in-session permission mode selector.
    • Shift+Tab cycles through the other modes only.
    • defaultMode: "bypassPermissions" from settings.json appears to be ignored by the desktop app.

    Works fine via CLI
    Same machine, same settings files — claude --dangerously-skip-permissions and Shift+Tab both work as expected in the terminal. The bug is desktop-only.

    Happy to provide logs / a sysdiagnose if helpful.

  6. github-actions
    added
    staleIssue is inactive
    on Jun 11, 2026

  7. github-actions commented on Jun 26, 2026

    @github-actions
    github-actionsbot
    on Jun 26, 2026 – with GitHub Actions

    Closing for now — inactive for too long. Please open a new issue if this is still relevant.

  8. github-actions
    closed this as not plannedon Jun 26, 2026

  9. github-actions commented on Aug 29, 2026

    @github-actions
    github-actionsbot
    on Aug 29, 2026 – with GitHub Actions

    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.

  10. github-actions
    locked as resolved and limited conversation to collaborators on Aug 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:desktoparea:permissionsbugSomething isn't workingduplicateThis issue or pull request already existsplatform:windowsIssue specifically occurs on WindowsstaleIssue is inactive

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions