Unable to run skhd directly after Sequoia upgrade

[nickcorin]

After upgrading to macOS Sequoia, I was prompted to re-grant skhd access to accessibility features. It was already enabled, and flipping the toggle off and on did nothing. To rid the prompt appearing when running skhd --start-service or skhd --restart-service, I had to:

1. Remove the skhd entry from the list of applications which have been granted accessibility access.
2. Run skhd --restart-service.
3. Grant access to the new entry through following the prompt once more.

However, I still cannot just run skhd directly in my terminal. I am constantly met with a prompt to grant accessibility access to eitherskhd, or alacritty. Both of these have been granted permissions, and all has worked fine until the upgrade.

All of this is to debug and test some broken features with Sequoia, specifically to interact with yabai, and more specifically, this, which seems to have broken every single keybind I have configured in skhd.

For clarity, even with skhd running as a service, none of my keybinds are working. Assumed due to the link above.

[maturk]

Funny temporary fix, I found that typing skhd -V in the terminal, and leaving the output open in the terminal returns the hot keys back.

But I can replicate the above issue, currently skhd --restart-service is completely stuck

[enweg]

I had a similar problem. Doing an install from source into another location than the standard homebrew location and starting the service from Terminal worked for me. I also had to allow Accessibility services for the Terminal app though. Some key bindings for yabai (those moving windows to other spaces) still don't work but this may well be due to yabai and not skhd.