The launcher already computed which Command key you pressed — and then threw the answer away. isCmdKey accepted keycode 55 (left) or 54 (right), so ANY two ⌘ presses inside the 500ms window fired it: left-left, left-right, right-left. Ordinary two-handed ⌘ use (or reaching for ⌘C twice) could summon Menu Band. Now the side decides. The NX device bits are the authority when present, since some keyboards report keycode 55 for both sides; we fall back to the keycode when neither bit is set. A left ⌘ additionally BREAKS the chain rather than merely not counting, so it can't serve as the first half of a right-⌘ pair. Also corrected the header, which promised right-⌘ behavior the code didn't implement and pointed at AppDelegate.startRightCommandTapMonitor — a function that no longer exists (the launcher is the only ⌘⌘ handler now). Note this is inherently direct-download only: the launcher is a CGEventTap daemon and a separate target, both forbidden under the App Store sandbox, so there is no ⌘⌘ shortcut in the MAS build to change. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>