Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] (macos) keyboard shortcut for allow-once vs always-allow [1 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#49614•Fetched 2026-04-17 08:36:11
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
r2evansr2evans
Participants
r2evansr2evans
Timeline (top)
labeled ×4

Error Message

Error Messages/Logs

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?

Using macos, the desktop app will ask me to verify permission to access a file or run a program. With some actions, the keyboard shortcut Cmd-Enter will trigger "Allow once" logic; with other actions the same shortcut will trigger "Always allow" logic, and the button for "Allow once" is set to Cmd-Shift-Enter.

Related issues:

They tend to deal with "changing the default behavior", my argument here is that regardless of which is the default, the user should be able to rely on a specific keyboard shortcut to do the same thing.

I don't know if it's default macos behavior or if the desktop app is enabling/controlling it.

What Should Happen?

The keyboard shortcuts (e.g., Cmd-Enter and Cmd-Shift-Enter) should always to the same thing; if it is not relevant to do one of the actions, then that keyboard shortcut should not be assigned arbitrarily to the other (or any other) action.

Error Messages/Logs

Steps to Reproduce

  1. Create a json file with an object
  2. Instruct the Claude desktop app to provide the top-level names within the file's json structure

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

1.2773.0 (884b37)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Other

Additional Information

As an example, I asked claude to provide the top-level names in a json file, this required both reading the file and then running a python script on it. In the first, the Cmd-Enter action is "Allow once" ...

<img width="1051" height="145" alt="Image" src="https://github.com/user-attachments/assets/2c013b98-145e-4bf5-9c3c-c63cabd779b0" />

and then ten seconds later the Cmd-Enter action is "Always allow"

<img width="1033" height="77" alt="Image" src="https://github.com/user-attachments/assets/ca420316-81cd-429b-b7fd-d64b5c18ea41" />

extent analysis

TL;DR

The inconsistent behavior of keyboard shortcuts in the Claude desktop app on macOS can be addressed by reviewing and standardizing the shortcut assignments for "Allow once" and "Always allow" actions.

Guidance

  • Review the code handling keyboard shortcuts in the Claude desktop app to ensure consistent behavior across different actions.
  • Verify that the Cmd-Enter and Cmd-Shift-Enter shortcuts are not arbitrarily reassigned to different actions based on the context.
  • Check if the issue is related to the macOS default behavior or if it's specific to the desktop app's implementation.
  • Consider adding a setting to allow users to customize the keyboard shortcuts for "Allow once" and "Always allow" actions.

Example

No code snippet is provided as the issue does not include specific code references.

Notes

The issue may be related to the desktop app's implementation or a macOS-specific behavior. Further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Review and standardize the shortcut assignments to ensure consistent behavior, and consider adding a setting for customizable keyboard shortcuts. This approach allows for a more predictable user experience while the root cause is being investigated.

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…
#api#configuration error#environment variable#network issue#logging issue

Still need to ship something?

×6

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

Back to top recommendations

TRENDING