[BUG] Windows desktop: Quick Entry keyboard shortcut stops working after every restart or update (startup skips it when legacyQuickEntryEnabled is false)

Status Open
Maintainer reply None cached
Activity 1 comment · opened Oct 4, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report
  • [x] I am using the latest version (Claude desktop 2.19675.0)

What's Wrong?

On Windows, a custom Quick Entry keyboard shortcut (Settings > System > Quick Entry keyboard shortcut) only works until the app restarts. After every launch or auto-update it has to be set again. This has happened on every version for about a year.

The shortcut itself is saved. %APPDATA%\Claude\claude_desktop_config.json keeps it across restarts:

"globalShortcut": "Alt+Cmd+C",
"preferences": {
  "legacyQuickEntryEnabled": false
}

The cause, from reading the shipped 2.19675.0 main-process bundle (app.asar):

  1. On Windows, the nativeQuickEntry capability reports unavailable, so startup takes the legacy Quick Entry branch.
  2. That branch registers the saved globalShortcut with globalShortcut.register only when the legacyQuickEntryEnabled preference is true.
  3. setGlobalShortcut, which the settings field calls, registers and saves the shortcut immediately but never checks or sets legacyQuickEntryEnabled.

So with legacyQuickEntryEnabled: false, setting the shortcut works for the current session and the next launch never registers it. Nothing is logged, because the register call is skipped rather than failing.

The preference defaults to true. This config has it set to false, and the Windows settings page shows no toggle for it next to the shortcut field, so a user cannot see or fix the state that breaks the shortcut.

What Should Happen?

A shortcut set in Settings should still work after a restart or an update. Any of these would fix it:

  • setGlobalShortcut turns legacyQuickEntryEnabled on when a shortcut is saved.
  • Startup registers an explicitly saved globalShortcut regardless of that flag.
  • The flag gets a visible toggle on Windows, next to the shortcut field.

Error Messages/Logs

None. main.log has no "Global shortcut registration refused" or "Skipping invalid accelerator" lines, which fits a register call that never runs.

Steps to Reproduce

  1. Windows 11, Claude desktop installed as the MSIX package, with "legacyQuickEntryEnabled": false under preferences in claude_desktop_config.json.
  2. Settings > System > Quick Entry keyboard shortcut. Set Alt+Win+C. Press it, and Quick Entry opens.
  3. Quit Claude fully from the tray and relaunch, or let it auto-update.
  4. Press Alt+Win+C. Quick Entry no longer opens until the shortcut is set again in Settings.

Claude Model

Not applicable (desktop app setting)

Is this a regression?

No, this never worked

Claude Code Version

Not applicable. Claude desktop 2.19675.0 (Windows, MSIX package)

Platform

Other (Claude desktop app)

Operating System

Windows 11 Pro, build 26200

Terminal/Shell

Other (desktop app, not a terminal)

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗