[BUG] : Ctrl+Shift+C should fall through to Ctrl+C (copy) when no action is bound to it.
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Problem: In the Claude Code desktop app (Windows), Ctrl+Shift+C does nothing. It should copy selected text to the clipboard, just like Ctrl+C does.
Why this matters: Ctrl+Shift+C is the standard copy shortcut in terminal emulators (Windows Terminal, VS Code integrated terminal, Git Bash, etc.) because Ctrl+C is reserved for SIGINT. Users who frequently switch between Claude Code desktop and a terminal build muscle memory around Ctrl+Shift+C for copy. When it silently does nothing in Claude Code desktop, it's confusing — you think you copied something, switch to another app to paste, and get stale clipboard contents.
What Should Happen?
Expected behavior: When a keybinding like Ctrl+Shift+C has no action mapped to it in the keybindings system, the keypress should fall through to the default OS/Electron handler. Since Electron's default behavior for Ctrl+C is copy, and Ctrl+Shift+C is an unbound superset of that, it should either:
- Fall through to the OS-level clipboard copy, or
- Be explicitly mapped as an alias for copy by default
Current behavior: The keypress appears to be intercepted by the keybinding layer and swallowed, preventing it from reaching the Electron/OS clipboard handler.
Error Messages/Logs
Steps to Reproduce
- Select any text in the Claude Code Desktop app conversation
- Press
Ctrl+Shift+C - Attempt to paste in another application
Expected: Selected text is copied to clipboard
Actual: Nothing is copied; clipboard retains its previous contents. Ctrl+C works correctly for the same selection.
Claude Model
None
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.85
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Windows Terminal
Additional Information
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗