claude-code - 💡(How to fix) Fix [BUG] "Yes, don't ask again" for Bash commands does not persist in desktop app [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#47146Fetched 2026-04-13 05:40:14
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Timeline (top)
labeled ×4commented ×1

When I click "Yes, don't ask again" on a Bash command permission prompt, the approval is not persisted. The confirmation prompt appears again on the next execution of the same command.

Error Message

Error Messages/Logs

Root Cause

When I click "Yes, don't ask again" on a Bash command permission prompt, the approval is not persisted. The confirmation prompt appears again on the next execution of the same command.

RAW_BUFFERClick to expand / collapse

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?

Description

When I click "Yes, don't ask again" on a Bash command permission prompt, the approval is not persisted. The confirmation prompt appears again on the next execution of the same command.

Steps to Reproduce

  1. Open Claude Code desktop app
  2. Ask Claude to run a Bash command that writes to a file (e.g., echo "test" >> memo.txt)
  3. When the permission prompt appears, click "Yes, don't ask again"
  4. Ask Claude to run the same command again
  5. The permission prompt appears again

Expected Behavior

According to the documentation, Bash command approvals should be persisted permanently per project directory and command.

Actual Behavior

The permission prompt appears every time, even after selecting "don't ask again".

Environment

  • Client: Claude Code Desktop App
  • OS: macOS (Darwin 25.3.0)
  • Permission mode: Default

What Should Happen?

After selecting "Yes, don't ask again" for a Bash command, the same command should be automatically approved in future executions without showing the permission prompt again.

Error Messages/Logs

Steps to Reproduce

  1. Open Claude Code desktop app
  2. Ask Claude to run a Bash command that writes to a file (e.g., echo "test" >> memo.txt)
  3. When the permission prompt appears, click "Yes, don't ask again"
  4. Ask Claude to run the same command again
  5. The permission prompt appears again

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.104

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

extent analysis

TL;DR

The issue can likely be resolved by investigating the permission storage mechanism in the Claude Code desktop app to ensure that approvals are correctly persisted per project directory and command.

Guidance

  • Review the documentation for the Claude Code desktop app to understand how Bash command approvals are supposed to be stored and retrieved.
  • Check the app's configuration and storage files to see if there are any issues with writing or reading the approval settings.
  • Investigate if there are any specific settings or flags in the app that might be causing the approval to not be persisted.
  • Consider testing the app with a different project directory or command to see if the issue is specific to a particular setup.

Example

No specific code snippet can be provided without more information about the internal workings of the Claude Code desktop app.

Notes

The issue seems to be a regression, as it worked in a previous version, which suggests that a change in the app's code or configuration might be the cause. Without more information about the app's internals or the specific changes made in recent versions, it's difficult to provide a more specific solution.

Recommendation

Apply workaround: The user may need to manually approve the command each time it is run until the issue is resolved, or consider downgrading to a previous version of the app where the issue was not present, if possible.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING