Mechvibes not working on Mac: fixes for “can't be opened”, permissions and no sound

First, check which Mechvibes you have

Select Mechvibes in Applications and choose File › Get Info to see its version.

• 3.x is Mechvibes 3, the current app, written in Rust. Version 3.4.0 came out on November 1, 2026. Its Mac download reads macOS Apple Silicon (experimental) (download page).
• 2.x is Mechvibes 2, the older Electron app. The download page says Using Mechvibes 2? It is no longer developed. Its repository was archived on October 30, 2026. If that's what you have, most fixes below won't help. Replace it with Mechvibes 3 from mechvibes.com/download.

Setting up from scratch? Do it in this order

1. Download the right file. Get the Apple silicon DMG (v3.4.0, 52.0 MB) from mechvibes.com/download. There's no Intel build yet.
2. Drag Mechvibes to Applications. Open the DMG and drag the app into your Applications folder.
3. Open it, then allow it in Privacy & Security. macOS blocks the first launch because the build isn't notarized. Fix 1 below shows how to allow it.
4. Turn on Accessibility and Input Monitoring. Mechvibes needs both, in System Settings › Privacy & Security.
5. Quit and reopen Mechvibes, then pick a pack. The permissions take effect on the next launch. Type in any app to test it.

Fix 1: “Mechvibes Not Opened” or “can't be opened”

This is expected. The Mac build's README says: It carries only an ad-hoc signature and is NOT notarized. Notarization is Apple's automated check for apps downloaded outside the App Store, so without it, macOS won't open the app until you say so.

macOS 15 Sequoia and later

1. Try to open Mechvibes once. macOS stops it. Click Done.
2. Open System Settings › Privacy & Security. Scroll down to Security. You'll see a line saying Mechvibes was blocked.
3. Click Open Anyway. Confirm, and enter your password or use Touch ID when macOS asks. Mechvibes opens.

Apple says the Open Anyway button is there for about an hour after you try to open the app (Apple: open an app from an unknown developer). If it's gone, try opening Mechvibes again first.

macOS 14 Sonoma and earlier

Control-click Mechvibes in Applications, choose Open, then click Open in the dialog. The System Settings route above works too.

Fix 1b: “Mechvibes is damaged and can't be opened”

On Apple silicon, macOS can show this for an ad-hoc signed app downloaded from the web, even when the file is fine, and Open Anyway may not appear. First, download it again from the official page, in case the file really did break. If the message comes back, you can clear macOS's quarantine flag for this one app:

1. Check where it came from. Only do this for a copy from mechvibes.com/download or the GitHub release.
2. Open Terminal and type the command below, with a space at the end. Don't press Return yet.
3. Drag Mechvibes from Applications into the Terminal window. That fills in the path. Now press Return.
4. Open Mechvibes again. It should start without the warning.

xattr -dr com.apple.quarantine 

This switches off Gatekeeper's check for that app entirely, so be sure about the source. For what you're trusting when you do this, see is Mechvibes safe?

Fix 2: it opens, but there's no sound when you type

Mechvibes needs two switches on: Accessibility, which lets an app control your Mac through accessibility features (Apple), and Input Monitoring, which lets it see key presses while you work in other apps (Apple). Its macOS README talks about both entries, so check both.

1. Open System Settings › Privacy & Security › Accessibility. Turn Mechvibes on. If it isn't in the list, click + and choose it from Applications.
2. Go back and open Input Monitoring. Turn Mechvibes on there too, adding it with + if needed.
3. Quit Mechvibes and open it again. Permissions take effect on the next launch. If you can't find its Quit command, select it in Activity Monitor and click the Stop button in the toolbar.

Fix 3: it stopped working after an update

This is the one people least expect, and Mechvibes warns about it. Its README for v3.4.0 says: You have to remove and re-add both entries after replacing the app with a newer build.

1. Quit Mechvibes.
2. In Privacy & Security › Accessibility, select Mechvibes and click − to remove it. Turning the switch off isn't enough; remove the entry.
3. Do the same in Input Monitoring.
4. Open Mechvibes and add it back to both lists. Approve the prompts, or use + in each list. Then quit and reopen it once more.

The likely reason: macOS ties these permissions to an app's code signature, and an ad-hoc signature is different for every build. After an update, macOS sees a new app, even if the old entry's switch still looks on. Expect to repeat this after each update while the Mac build is ad-hoc signed.

Fix 4: no sound, or the sound comes late

If both permissions are on and Mechvibes has been relaunched, work down this list:

• Check the output. Open Control Center › Sound, or System Settings › Sound › Output. Is the speaker or headphones you're listening on selected, and is the volume up?
• Check Mechvibes itself. Make sure a sound pack is selected and its volume isn't turned down.
• Check for secure input. macOS doesn't pass password-field keystrokes to apps that monitor input, so every keyboard sound app is silent there, by design. Terminal's Secure Keyboard Entry does the same for everything you type in Terminal. If sounds stop everywhere after you've typed a password, the app with that field may still be holding secure input; quitting it usually brings the sound back. More in what Input Monitoring can and can't see.

How to fix Mechvibes delay

Bluetooth headphones and speakers, AirPods included, add a delay to every sound your Mac plays, and with typing sounds you notice it. To check, switch the output to the built-in speakers or wired headphones and type again. If the delay goes away, it was the Bluetooth link. If it's there on built-in speakers too, report it (below).

Still silent?

The README is frank that this build has never been run on a real Mac by the maintainer, so you may have found a real bug. Open an issue on Mechvibes' GitHub with your Mac model, macOS version, and the steps you've tried. Reports from real Macs are how Mac bugs get found.

Fix 5: Mechvibes on an Intel Mac

There's no fix yet. Mechvibes' own troubleshooting post says: Intel Macs are not supported yet ( issue #128 ). The good news is in that issue: an Intel Mac build is now merged and ships with the next release. Watch the download page for it.

Don't fall back on the old Homebrew cask (next fix). If you'd rather not wait, see keyboard sound apps that run on Intel Macs today.

Fix 6: Homebrew won't install Mechvibes

The mechvibes cask still points at Mechvibes 2 (version 2.3.4), and Homebrew disabled it on September 1, 2026. Its cask data gives the reason as "disable_reason":"fails_gatekeeper_check". So brew install --cask mechvibes won't give you a working app. Download Mechvibes 3 from mechvibes.com/download instead.

Fix 7: sound packs won't install

The library's one-click button isn't meant for Macs. In Mechvibes' words: The Install in Mechvibes button in the library works on Windows and Linux. On a Mac, click Download zip on a pack's page. Then import that ZIP in the Mechvibes app. To make your own pack, use the editor on mechvibes.com.

Rather not fix it?

If Mechvibes is working for you now, there's no need to switch. It's free, and nothing above is hard once you know it. If you'd rather have something that installs like an ordinary Mac app, two options:

• KeyEcho is free with optional paid packs. Its macOS builds are notarized, with separate downloads for Apple silicon and Intel. See KeyEcho's packs and prices.
• Keyslam is our app: $3.99 once after a 7-day free trial. It asks for Input Monitoring only, makes no network connections, runs on macOS 13 Ventura or later on Apple silicon or Intel, and on MacBooks with the motion sensor it follows how hard you type. It's Developer ID-signed and notarized by Apple, so Gatekeeper opens it with the normal prompt for apps from the internet; see the install steps and requirements.

Everything else, free and paid, is in the Mac keyboard sound app comparison, and the Mechvibes trade-offs are laid out in Mechvibes vs Keyslam vs Klack.