After last update 6.286 I have constant Command key pressed!

Keyboard is Keychron (I believe it doesn’t matter, but never know). I have some shortcuts for macros and others. I pressed my good known shortcut (Ctrl – F11 in this case) but nothing happen. I go to the settings, try to repeat my keys for the shortcut - but instead of Ctrl - F11 I see Command - Ctrl - F11! Then, I try to open Firefox from the browser, but instead of opening, Finder shows me the app in the Applications folder! After closing BTT everything works fine.

Please, don’t tell me that I have to delete my prefs and start from scratch. It’s a few years configuration with a lot of the near forgotten combinations.

And please, fix it :slight_smile:

almost certainly this:

Thanks for the fast response.

Yeah, I have some shortucts with Command key, but only for specific application. Not for the others! (Windows related apps, so I have changed Command into Ctrl).

Seems like this is the new bug, where “only send key down” is not honored, but it extend over settings for the specific app. I think this is the way.

What's even weirder is that the constant Command press happens some time after BTT starts. Not immediately.

have you checked the recently used section? I'm 99% sure it's a misconfigured action (a keyboard shortcut that is being sent, but with the option to only send the key down-event)

If you want you can export your preset and send it to me (andreas@folivora.ai), then I can tell which trigger is sending the shortcut

It would be great if it turns out these are just my bad settings. Thanks for this option, I'm sending my settings to you right now.

Your silence worries me, Andreas.

But I have good news.
Downgrading to version btt6.000-2026010502 solved my problem. No more sticky Command key here.

Best to you.

Sorry, was just asleep :wink:
The issue is a drawing gesture you have set up. It's named "dół" and you have assigned CMD+W to it but it is set to only execute the key-down press and not release it afterwards:

Wow! You’re a proper investigator! Thanks for this.

But why downgrading solves this problem?

Because of the old bug that has been fixed recently, I described in the first reply After last update 6.286 I have constant Command key pressed! - #2 by Andreas_Hegenberg

Downgrading to a version that still has the bug will make it so the "only key down" option is ignored (even though it should not be).

Wow. This just goes to show how complex software development is. Troubleshooting it is truly an investigation, like something out of a good detective story.

I upgraded to the latest version. And it works!

You're a genius, Andreas. Thanks!