For many Linux users, the Flatpak is the easiest way to run AntiMicroX: it is an official route listed in the project’s own README, published on Flathub under the app ID io.github.antimicrox.antimicrox. AntiMicroX is a graphical program used to map gamepad keys to keyboard, mouse, scripts and macros, and it is free, open-source software under GPL-3.0-or-later. This guide covers installing the Flatpak, keeping it updated, understanding the permissions a controller mapper needs, and the version context — including why the current release, 3.6.1, paid unusual attention to the Flatpak package.
Installing the Flatpak
- Make sure Flatpak is set up on your system and the Flathub remote is enabled — most desktop distributions either ship this or offer it as a standard setup step.
- Install AntiMicroX with:
flatpak install flathub io.github.antimicrox.antimicrox - Launch it from your application menu, or run it with:
flatpak run io.github.antimicrox.antimicrox - Connect a controller and confirm AntiMicroX detects it. Detection works through SDL2.
- Create and save a profile, mapping buttons and axes to keyboard keys, mouse actions, scripts or macros.
The app ID is the detail worth copying exactly. io.github.antimicrox.antimicrox is the identifier the project itself publishes, and using it guarantees you are installing the project’s Flathub package rather than a similarly named item. If you prefer a graphical route, the same package is what a software centre shows when it sources AntiMicroX from Flathub.
Updating — and Why 3.6.1 Mattered for Flatpak Users
Updating a Flatpak is a single routine step: run flatpak update, or accept the update through your desktop’s software centre, and AntiMicroX refreshes alongside your other Flatpak applications. That routine paid off visibly in the current release. Version 3.6.1, dated 22 May 2026, was described by the project as a minor release mainly tackling issues related to the Flatpak package. Its listed changes include fixing a blank tray icon for the Flatpak build — the kind of small, annoying bug Flatpak users would actually meet — and fixing a crash on X11 for builds compiled with X11 support disabled. The same release bumped the Qt and SDL2 versions used in release builds and made Qt6 the default build, alongside translation updates. If you installed the Flatpak a while ago and have been skipping updates, 3.6.1 is a concrete reason to run one: two of its fixes are aimed at exactly your install route and desktop situation.
The previous release is useful context too. Version 3.6.0, from 6 May 2026, added InputDevice IPC via D-Bus, fixed the key assignment dialog on Wayland and fixed AppImage dependencies. A Flatpak user updating today receives that whole line of work at once, which is how a maintenance-phase project delivers value: not in one headline feature, but in a stack of small correctness fixes. The complete record is in our version history.
Permissions: What a Mapper Needs and Why
Flatpak applications run inside a sandbox, and a gamepad mapper is an unusual tenant for one, because its entire job is to see input devices and then send keyboard and mouse input elsewhere. Understanding that shape helps you judge permission prompts sensibly. AntiMicroX needs to detect your controller — input handling runs through SDL2 — and it needs access to your configuration so profiles persist between sessions. Profiles are the heart of the program: each one holds mappings for buttons and axes, can contain up to eight switchable sets of assignments, and can use advanced slots such as macros, tap-and-hold, double-tap, turbo behaviour, delays and distance, hold and cycle zones. If a profile you saved seems to vanish, or a controller never appears, the first questions are practical: is the device visible to the system at all, and did the application keep the access it needs to do its job? The project’s own documentation points Linux users to SDL2-based testing tools for checking whether a gamepad is recognised before blaming the mapper.
One documented limitation belongs in this section rather than in a footnote: Auto Profiles — loading a profile automatically based on the active application window — do not work on Wayland. The README states this, and release 3.5.1 added an explicit note about the lack of Wayland support for that feature. AntiMicroX otherwise supports X.org and Wayland, and it has shipped Wayland fixes for keyboard input and dialogs in recent releases. So on a Wayland desktop, Flatpak or not, plan on manual profile switching; on X.org, Auto Profiles work as documented. No permission setting changes that distinction, because it is a feature limitation of the display protocol, not of the package.
Flatpak or Another Route?
The Flatpak is one of several official Linux routes. The project’s README also describes distribution packages — for example, Fedora users can install AntiMicroX with dnf, and there are openSUSE and Arch routes — and the GitHub release offers .deb packages for Ubuntu 22.04 and 24.04 plus an x86_64 AppImage. The Flatpak’s advantages are uniformity and managed updates: the same package works across distributions, and updates flow through one mechanism. Its trade-off is the sandbox described above, which a native package does not impose in the same way. Our Linux hub compares the routes, and the Steam Deck guide shows the Flatpak route applied to a specific device, where it is the natural choice.
After Installing: A Sensible First Session
Start with one game or application rather than mapping everything at once. Build a profile, assign the handful of keyboard keys or mouse actions that program actually needs, and test it. Add a second set inside the same profile only when you find yourself wanting a menu layout alongside a gameplay layout. Tune stick deadzones if movement feels twitchy — the project’s profile tips discuss typical deadzone values, including the XInput standard of 8,000 — and explore mouse acceleration curves if you map a stick to pointer movement. Keep expectations calibrated about the project’s phase: AntiMicroX is seeking a new maintainer, support is limited and new features depend on external contributors, but patches are still shipping, as the May 2026 releases prove. For downloads and the other platform routes, see the download page. On Linux, for most desktop users, the Flathub package in this guide is the version we would install.
