Permissions no longer break on every update
Glimble was ad-hoc signed, which makes the app's code-signing identity its own binary hash. That hash changes on every build, so each release looked like a brand-new app to macOS: your Accessibility grant was silently dropped, and from then on every keyboard shortcut and media key Glimble sent was discarded. No error, no crash, no message — gestures just stopped doing anything.
Releases are now signed with a stable certificate, so permissions survive updates.
Verified: rebuilding the app changed its binary hash while the Accessibility grant stayed intact and gestures kept working, with no re-authorization.
Glimble now tells you when it can't act
CGEvent.post is gated by a different permission bucket than the one Glimble was checking, so a blocked app looked perfectly healthy. Glimble now checks the one that actually matters, every 15 seconds. When a permission is missing, the menu bar shows a
Upgrading from 0.1.5 or earlier
macOS will ask for Accessibility one last time, because the app's signature legitimately changed. In System Settings ▸ Privacy & Security ▸ Accessibility, remove the old Glimble entry with −, then add it again. This is the final time — from 0.1.6 on, updates keep your permissions.
Install
brew tap gum798/glimble
brew trust gum798/glimble
brew install --cask glimble
xattr -dr com.apple.quarantine "/Applications/Glimble.app"
Already installed? brew upgrade --cask glimble, or use Check for Updates… in the menu bar.