Mechvibes 3.0: What Changed and How to Upgrade
Mechvibes 3.0.0 was released on October 30, 2026. MechvibesDX is now called Mechvibes, and it replaces the original Electron app, Mechvibes 2. If you have been following the DX releases, the jump from 0.8.4 to 3.0.0 marks that change in the official app.
You can get the installers from the download page. The 3.0.0 release notes include the complete changes and downloadable files. Here is what to expect before you update.
What changes in this release
On Linux, mouse buttons now work across Wayland applications. Previously, mouse capture depended on X11 and could miss clicks in native Wayland windows, even while clicks in XWayland applications worked. Mechvibes now reads the buttons directly from input devices when it can access them.
Mouse wheel events also reach the sound engine on Wayland. You will hear them only if your selected pack defines MouseWheelUp and MouseWheelDown. This change does not add wheel capture on X11, and two-finger scrolling on a touchpad stays silent. A mouse connected or reconnected while Mechvibes is running needs an app restart before its buttons can be heard.
The Linux tray menu also works while the window is hidden. Mute, Show and Exit keep responding, and showing the window raises it to the front.
Sound pack imports now refuse an ID that already belongs to an installed pack, including a built-in pack. Previously, a failed duplicate check could let an import overwrite files. If an import is refused, check the pack you already have instead of repeatedly importing the same ZIP.
On Windows, uninstalling now keeps settings and custom packs unless you choose to delete them. This fixes a bug where the data folder was removed before the uninstaller asked.
Updating from MechvibesDX
On Windows, use the in-app update action or run the new installer. Keep MechvibesDX installed until you do this: the release notes explicitly warn against uninstalling it first. Your existing settings, sound packs and Start at login preference carry over.
On Linux, installing the new Debian package replaces the previous MechvibesDX package. If you use the AppImage, download the new file, make it executable and launch it. The download page has both formats.
On macOS, open the disk image and drag Mechvibes into Applications, choosing Replace if prompted. For 3.0.0, move the old MechvibesDX application to the Trash yourself. You may need to grant Accessibility and Input Monitoring again.
Updating from Mechvibes Legacy
If you use Mechvibes 2 on Windows, run the new installer and accept its offer to remove the old app. Leaving both applications running can make each key play twice.
On Linux, the new Debian package replaces Mechvibes 2. Custom packs you added to Legacy need to be imported again as ZIP files in 3.0.0. Automatic migration of those packs is not part of this release.
After installation, open Sound packs, choose Keyboard or Mouse, select Add, then Select file. Import a pack and select it on Home. The sound pack library is another place to find something to try.
Check your platform setup
The macOS download is for Apple Silicon and is not notarized. Linux input capture may require adding your account to the input group, especially on Wayland. See the setup notes for those steps, then test a built-in pack before troubleshooting a custom one.