`Shift+Y` and `Shift+T` produce no character while SuperCmd is running

[Hantok]

Bug Report

When SuperCmd is running in the background, pressing Shift+Y produces no character output at all. The keystroke appears to be silently consumed or blocked by SuperCmd rather than passed through to the active application.

Steps to reproduce:

1. Launch SuperCmd
2. Switch to any text input field (e.g. a text editor or browser address bar)
3. Press Shift+Y

Expected behavior: uppercase Y is typed into the active field.
Actual behavior: nothing is typed, the character is swallowed entirely.

Additional context:

• Shift+T works correctly and produces uppercase T
• Only certain Shift+<key> combos seem affected; Shift+Y is a confirmed case
• The issue is reproducible with SuperCmd running but does not occur once the app is quit
• Reproduced on v1.0.8 and confirmed present on older versions as well
• Likely related to global hotkey registration or keyboard event interception in the Swift native helpers or Electron's globalShortcut module capturing Shift+Y for an internal binding

Possible root cause:

SuperCmd likely registers Shift+Y (or a conflicting key combo) as a global shortcut via Electron's globalShortcut.register() or via the Swift hotkey helper, preventing the OS from forwarding the event to the focused app.

Version: 1.0.8
OS: macOS 15

[shobhit99]

Hi @Hantok
Is this on the dmg release or are you testing this on main branch
I tried reproducing this but it was working properly for me. can you check if there are any shortcuts registered with shift, i will try to reproduce with same hotkeys

[Hantok]

Hi @shobhit99

this is the release version from dmg file (arm). the issue is repoduced even when I switch to other languages. those buttons do not work with Shift and do not produce uppercase letter. Weird situation. I removed all shortcuts related to 't' and 'y'.

[shobhit99]

@Hantok i tried on different mac as well. can you try existing the SuperCmd and see if it's still happening. dumb test but just want to double confirm if it's actually supercmd causing the issue

[Hantok]

Got it, @shobhit99
Please do not close the issue. I am investigating on my mac. Once I find the root cause - I share here or create PR.

[Hantok]

Hi @shobhit99
PR is set: #154
Finally I can type normally ☺️

[Hantok]

Hi @shobhit99,

I'm not convinced this fix improves the app design. I've started testing from version 1.0.8 to 1.0.11 and can no longer reproduce the bug. It's possible "an outdated hotkey cache" was the cause, but I'm uncertain.

I've found other bugs and will report them in a separate thread.

[Hantok]

UPD: It is so weird. It started to reproduce again in v1.0.11

[shobhit99]

@Hantok It's merged in main but it's not yet released, it will be live in 1.0.12 release

[shobhit99]

@Hantok can you confirm if this is working for you, excluding the breaking change, the new release is live

[Hantok]

@shobhit99 not really. I tested the new release today. What I found: when I just launched the app - everything was perfect. But after some time I reproduced the issue again accidentally, because I had a lot to do with texts. 😔

[shobhit99]

@Hantok do you know how to reproduce it? i will try to reproduce it on my machine. or you can also make the necessary again and just see that supercmd shortcuts are registered properly in the fix, i will test it again and release

[Hantok]

I am happy to help. As soon as I will have more data I will share. I have different utilities on mac machine.
Unfortunately, I don't have much capacity for the project.

[shobhit99]

@Hantok did you get anything on this?

[Hantok]

Hi @shobhit99
Nothing new from my side, I switched back to Raycast. Sorry, it was so annoying having this issue that started again to reproduce after some time after launch/restart the app