claude-code - 💡(How to fix) Fix [BUG] macOS Desktop: Permission prompt has no Enter keybinding — requires ⌘⇧↵ / ⌘↵ only [2 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#52040Fetched 2026-04-23 07:38:10
View on GitHub
Comments
2
Participants
2
Timeline
6
Reactions
0
Author
Timeline (top)
labeled ×4commented ×2

On macOS Claude Code Desktop, the permission prompt does not respond to the Enter key at all. The only available keybindings are:

  • Allow once: ⌘⇧↵ (Cmd+Shift+Enter)
  • Always allow: ⌘↵ (Cmd+Enter)
  • Deny: Esc

There is no way to approve a permission with just Enter, which is the default behavior in the CLI version.

Root Cause

On macOS Claude Code Desktop, the permission prompt does not respond to the Enter key at all. The only available keybindings are:

  • Allow once: ⌘⇧↵ (Cmd+Shift+Enter)
  • Always allow: ⌘↵ (Cmd+Enter)
  • Deny: Esc

There is no way to approve a permission with just Enter, which is the default behavior in the CLI version.

RAW_BUFFERClick to expand / collapse

Description

On macOS Claude Code Desktop, the permission prompt does not respond to the Enter key at all. The only available keybindings are:

  • Allow once: ⌘⇧↵ (Cmd+Shift+Enter)
  • Always allow: ⌘↵ (Cmd+Enter)
  • Deny: Esc

There is no way to approve a permission with just Enter, which is the default behavior in the CLI version.

Comparison with Windows

Per #48550, Windows Desktop users can press Enter on the permission prompt (it triggers "Always allow" there). On macOS, Enter does nothing — it is not mapped to any action.

Additional context

  • ~/.claude/keybindings.json with "enter": "confirm:yes" in the Confirmation context has no effect on Desktop — the file appears to be ignored entirely.
  • Removing keybindings.json does not change the behavior — macOS Desktop simply has no Enter mapping for the permission prompt.
  • The CLI version defaults to Enter = Allow once, which is the expected behavior.

Expected behavior

Enter should map to "Allow once" on the permission prompt, consistent with CLI behavior and the principle of least privilege.

Environment

  • Platform: macOS (Apple Silicon)
  • App: Claude Code Desktop

extent analysis

TL;DR

The permission prompt in Claude Code Desktop on macOS should be updated to map the Enter key to "Allow once" by default, consistent with the CLI version.

Guidance

  • Investigate the keybinding configuration for the Desktop version to determine why the ~/.claude/keybindings.json file is being ignored.
  • Compare the keybinding implementations between the macOS Desktop and Windows Desktop versions to identify the difference in Enter key behavior.
  • Consider adding a default keybinding for the Enter key to trigger "Allow once" in the permission prompt on macOS Desktop.
  • Review the principle of least privilege to ensure the updated behavior aligns with security best practices.

Example

No code snippet is provided as the issue does not contain sufficient information about the codebase.

Notes

The issue appears to be specific to the macOS Desktop version of Claude Code, and the solution may involve updating the keybinding configuration or the application's behavior on this platform.

Recommendation

Apply a workaround by manually mapping the Enter key to "Allow once" in the keybindings configuration, if possible, until a permanent fix is implemented. This is because the current behavior is inconsistent with the expected behavior and may cause user confusion.

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…

FAQ

Expected behavior

Enter should map to "Allow once" on the permission prompt, consistent with CLI behavior and the principle of least privilege.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING