Mechvibes not working on Mac? Fixes, and what to use instead

Before fixing anything, check which one you installed, because the fixes differ a little.

Mechvibes is the original. It's free and open source (MIT), built with Electron, and its GitHub page has releases for Mac, Windows and Linux, with a big library of community sound packs. Its README now says it will become legacy once the new version is stable.

MechvibesDX is the successor, rewritten in Rust by the same maker. As of October 2026 its own page is honest about the Mac build: it's experimental, Apple Silicon only, ad-hoc signed and not notarized, and the maker says it hasn't been tested on real Mac hardware yet.

Neither of these is a criticism. It's a free project made in someone's spare time, and Apple's notarization costs a paid developer account. But it explains most of what goes wrong on a Mac: macOS is strict with apps it can't verify, and strict with anything that listens to the keyboard.

If you have an Intel Mac, MechvibesDX's Mac build won't run on it today. Use the original Mechvibes.

When you double-click an app that isn't notarized, macOS shows a warning that it can't check the app for malicious software, with Done and Move to Trash. Click Done. Then:

1. Open System Settings → Privacy & Security.
2. Scroll down to the Security part. You'll see a line saying Mechvibes was blocked, with an Open Anyway button.
3. Click it, confirm with your password or Touch ID, and open the app again.

On macOS 14 Sonoma and earlier, the shortcut still works: Control-click the app in Applications, choose Open, then Open again. macOS 15 removed that shortcut, which is why the old tutorials stopped working.

If the message says the app “is damaged and can't be opened”, macOS usually means it's unsigned and still marked as downloaded from the internet. People clear that mark in Terminal:

xattr -dr com.apple.quarantine /Applications/Mechvibes.app

Only do either of these for a copy you downloaded from the project's own GitHub releases page, never from a random mirror. You're telling macOS to trust that exact file.

If Mechvibes clicks while you type in its own window and goes silent the moment you switch to Safari or Notes, it's missing Input Monitoring. That's the macOS permission that lets an app hear key presses while another app is in front. MechvibesDX's own README puts it plainly: without it, the app runs but stays silent unless its window has focus.

The fix:

1. Open System Settings → Privacy & Security → Input Monitoring.
2. Find Mechvibes (or MechvibesDX) and switch it on. If it isn't listed, click + and add it from Applications.
3. Quit the app completely (from its menu bar or Dock icon, not just the window) and open it again. macOS applies the switch when the app starts, which catches almost everyone.

If it was already switched on, it's probably a stale permission. That happens after an update or a reinstall: the switch belongs to the old copy, not the one you're running. Select the app in the list, click − to remove it, add it again with +, then quit and reopen the app. Do the same in the Accessibility list if Mechvibes is there too.

Every keyboard sound app on a Mac needs this permission, Clacky included. So it's fair to ask what each one does with it; I wrote about that in do keyboard sound apps record what you type.

When a password field has focus, macOS turns on Secure Input and stops sending key presses to every other app. That's a good thing: no keyboard app can hear your password. The problem is when an app forgets to turn it off again. A password manager's unlock window, a login prompt left open, or Terminal with Secure Keyboard Entry ticked can keep it on for hours, and every keyboard sound app goes quiet.

To find out which app is holding it, paste this into Terminal:

ioreg -l -w 0 | grep -i SecureInput

If it prints a line with kCGSSessionSecureInputPID, the number after it is the process ID. Find that number in Activity Monitor (the PID column), then click out of that app's password field or quit it. The sounds come back straight away.

Try it below: focus the password box and watch what a keyboard sound app would hear.

Two boring checks save a lot of time.

The keyboard. If only some keys are silent, the keys themselves might not be reaching your Mac, for example a Bluetooth keyboard that drops presses or a key that needs cleaning. Open the free keyboard tester and press the silent keys. Each one turns green when the Mac gets it. If a key never turns green, the problem is the keyboard, not Mechvibes.

The sound output. Click the volume in the menu bar and check which output is picked. AirPods that disconnected, a monitor with its own speakers, or an audio interface can quietly take over. Mechvibes also has its own volume slider, separate from the Mac's.

Then one more: some apps that also listen to the keyboard (text expanders, key remappers) can get in the way. Quit them for a minute and try again.

Prices from each app's own listing, October 2026:

If you love a specific community pack, staying with Mechvibes is worth the setup above. Nothing else has that library.

Clacky is the one I make, so weigh this paragraph accordingly. It has 29 keyboard sounds in 9 families, synthesized so no two presses sound exactly alike, plus sounds for clicks and scrolling. It's notarized by Apple, so it opens like any other app, and it walks you through Input Monitoring the first time. Keyboard sounds listen for key down/up only; Clacky never records, stores or sends which keys are typed, and it respects Secure Input. There's a 7-day free trial with no card. You can hear the click sounds right here: