A hotkey's key is sent once, not twice
Explore this workspace.
Technical background
A key bound to a hotkey that the terminal could also type reached the session twice: once from the hotkey, once from the terminal. It happened from launch until the first ordinary keystroke, and after every multi-chord hotkey, so the first Ctrl+C in a freshly opened Claude Code session sent two interrupts, the second of which can exit it, and Ctrl+C with text selected copied it and interrupted as well. Every hotkey now keeps its key, whatever was typed before. A handler that chooses not to act gives the key back, so copy bound to Ctrl+C with nothing selected still sends one Ctrl+C.
The problem
A terminal key bound to a hotkey could reach the session twice: once from the hotkey and once from ordinary terminal input.
How it works
When a hotkey handles a key, the terminal consumes that key. A handler that does not act returns it to the terminal, so an unselected Ctrl+C still sends one interrupt.
What this does not claim
- This covers keys handled by Torbie hotkeys; it does not make external applications' shortcuts available to Torbie.