My head exploded a long time ago, so it doesn't matter to me anymore. 
Seriously, double-taps aren't even necessary. You could define right ⌘ as ⌘ + ⇧. Isn't that easier than pressing two modifiers? A matter of opinion.
I rarely use Caps Lock (Hyerkey) because the key is too far away from my fingers.
But there are users who want a hyperkey with Caps Lock without ⌥. Maybe this works if you add “opt up” virtually, I don't know, it's all a bit crazy anyway. 
I prefer Caps Lock precisely because it’s a bit harder to reach, so I don’t press it accidentally. 
Plus, I build most of my shortcuts around it because it’s easier for me to remember that Caps Lock is for my shortcuts, while Shift, Cmd, Ctrl, Opt, and Fn/Globe (and their combinations) are reserved for macOS or specific apps.
By the way, I just thought of something—can I remap the right Cmd or Opt key to act as the Globe key? My external keyboard doesn’t have it; it only has an Fn key, which isn’t available to the OS and only modifies functions directly through the keyboard firmware.
yes, I will soon add a function to a generic remap of single keys now that I know how to do it Maybe I get to it later today
I've been happily using BTT for years to enable hyper key. Since updating to Sequoia a few weeks ago, I'm experiencing issue with Caps Lock staying on after using the hyper key.
When I restart BTT, the issue is fixed for a brief moment, but resurfaces again after a few minutes.
I've updated via alpha channel to 4.9998, but the issue persists.
I'm curious if others are experiencing something similar, or whether there was a recent change that might be causing this?
could you go to help -> export diagnostic debug information and send the result to me? (andreas@folivora.ai)
Thank you for such a swift response, Andreas. I've just sent the debug info to your email.
@ilijusin thanks for the logs! Unfortunately I couldn't find anything obvious. Are you using an external keyboard? Does the issue happen on all keyboards you use?
one more note: in 4.9999 alpha I added an explicit call to disable capslock after using the hyper key (although it should not be necessay). Would be great if you could check whether that helps in your case
I've deleted my previous settings and set up the hyper key anew. It seems to have resolved the issue!
Thank you again for a prompt and helpful response.
Sorry for jumping in here, but for my specific use case the newest implementations also seem to have broken things.
Use case:
Until one of the recent updates, this worked by using a named trigger.
Now I migrated it to the new feature to directly configure "actions executed on (unused) hyperkey release":
Toggling they caps lock does only turn it on but I cannot turn it off by only pressing caps lock.
The caps lock as hyper key triggers work together with e.g. "hyperkey + f" to switch to finder. As introduced in 4.9999, they also turn off caps lock as a side effect now.
A 3rd trigger to use "option + caps lock" also used to work before and is now broken - not sure if this is related. (I use it together with alttab to switch to another window of the current application).
Any ideas?
Thanks a lot in advance!
I have exactly the same problem @sibbl! Have you managed to find a solution yet? At this point I can't be sure if it's something we can fix or it has to be fixed with an update.
Unfortunately I couldn't get it working.
I played around with older versions, though. In versions 4.9997 and 4.9998 actions within the "Actions Executed On (Unsued) Hyperkey Release" part don't seem to do anything at all. Even if I chose another action like "show desktop" - nothing happens.
For version 4.9999 actions like "show desktop" work fine. Only the "Toogle Caps Lock On/Off" seems to make troubles. Whatever I do, the 3 bugs persist:
I guess only an update will be able to solve it, if one doesn't want to downgrade to older version before the "Big improvements for Capslock as Hyperkey" change.
I’ll look into the caps lock toggle issue next week when I’m back @ developing. Should be easy to fix
So great to see Hyper Key working that well, thank you!
One thing I've noticed is that it is not properly recognised by some applications.
I have set up window resizing in Raycast, because it allows you to toggle between different layouts (example, if you press left half multiple times it will toggle between one-third, half and two-thirds).
I've configured the keyboard shortcut with the newly assigned hyperkey through BTT, but it will fail to trigger the command.
I had no issues with using Superkey to trigger it before.
BTT can do this natively:
I have it triggered with hyperkey and it works well with 4.9999:
Not sure about Raycast, but i use alfred a lot and Alfred keys are passing with hyperkey without issue.
@lukasvac, @sibbl, the issue has been patched with the v5.070. If you update, you can now use caps lock as hyper key and also turn on/turn off caps lock
Awesome, thanks for the hint and the fix itself! Just pulled the update and "caps lock toggling caps lock on/off" + "caps lock as hyper key" both work as expected.
Some side-effects are strange though: as soon as I have "caps lock act as hyper key" configured, I cannot add new shortcuts containing caps lock. The sortcut recorder simply doesn't catch anything.
If I had e.g. the trigger "caps lock + option -> show desktop" configured before, it breaks as soon as I add "caps lock as hyperkey" trigger+action. Without "caps lock act as hyper key" being configured, the same trigger works as expected.
It feels to me that this behavior may not be intended and is related to this thread.
this is expected, as soon as you remap capslock to hyper, it doesn’t act as capslock anmore
That's good to know, thanks for the quick reply!
