claude-code - 💡(How to fix) Fix Permission prompt UI shows Apple ⌘ symbol instead of "Ctrl" on Windows

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…

Root Cause

Root cause hypothesis

Platform detection is either:

  • Hardcoded to macOS glyphs in the permission-prompt component, or
  • Falling through to a macOS default branch when the OS check fails or isn't applied at that render path.
RAW_BUFFERClick to expand / collapse
<img width="2442" height="583" alt="Image" src="https://github.com/user-attachments/assets/a77f103e-55aa-44ca-a070-ef312fab6abc" />

Permission prompt UI shows Apple ⌘ symbol instead of "Ctrl" on Windows

Environment

  • App: Claude desktop (Windows, MSIX install from Microsoft Store)
  • Version: 1.7196.0.0
  • Install path: C:\Program Files\WindowsApps\Claude_1.7196.0.0_x64__pzs8sxrjxfjjc\app\Claude.exe
  • OS: Windows 11 Pro 10.0.26200
  • Status: Persistent across multiple app versions — has not been fixed despite passage of time.

Steps to reproduce

  1. Launch Claude desktop on Windows 11.
  2. Start a conversation in which Claude calls a tool that requires user permission (e.g., a Bash command, file edit, etc.).
  3. Observe the permission prompt that appears, including its keyboard-shortcut hints.

Expected behavior

Keyboard hints in the permission prompt show the correct Windows modifier names — i.e., "Ctrl" (and "Alt", "Shift", "Win") — matching the user's actual platform.

Actual behavior

The permission prompt renders the macOS Command key glyph in place of "Ctrl" (and presumably other macOS-flavored modifier glyphs in place of their Windows equivalents). Pressing the displayed shortcut on a Windows keyboard requires the user to mentally translate ⌘ → Ctrl every time.

Root cause hypothesis

Platform detection is either:

  • Hardcoded to macOS glyphs in the permission-prompt component, or
  • Falling through to a macOS default branch when the OS check fails or isn't applied at that render path.

A cross-platform Electron app should consult process.platform (or equivalent) and pick the modifier label per OS — "Ctrl" on win32, "⌘" on darwin, "Ctrl" on linux.

Impact

Small but persistent friction every time a permission prompt appears (which can be many times per session for power users). Also undermines polish — a Windows user sees a Mac glyph and immediately reads the app as "ported but not finished."

Attachment

A screenshot of the misrendered prompt can be attached on submission; the reporter has seen this repeatedly and can capture one in seconds.

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

Keyboard hints in the permission prompt show the correct Windows modifier names — i.e., "Ctrl" (and "Alt", "Shift", "Win") — matching the user's actual platform.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Permission prompt UI shows Apple ⌘ symbol instead of "Ctrl" on Windows