On X.org, AntiMicroX Auto Profiles feel almost magical: focus a game window and the right profile loads. Move to a Wayland session and the switching silently stops, which sends many users hunting through settings that were never the problem. This post states the situation plainly, because it is documented by the project itself: Auto Profiles do not work on Wayland. That is a platform limitation, not a fault in your profiles, and no checkbox in AntiMicroX changes it. The rest of this article explains why, what still works on Wayland, and the workarounds that are actually worth using. It belongs to our wider AntiMicroX troubleshooting series.
What the documentation actually says
The project README lists Wayland as supported for AntiMicroX in general, with one explicit caveat about Auto Profiles, and the project’s own changelog for version 3.5.1 records that a note was added that Auto Profiles lack Wayland support. The wiki describes Auto Profiles as loading a profile based on the active application window. On Wayland, applications are deliberately restricted in what they can know about other programs’ windows — a security design decision in the protocol. A utility cannot freely watch which window is focused and identify it the way it could on X11, so a feature built on window detection loses its foundation. That is why the honest answer is not a hidden fix: the feature depends on information Wayland does not provide in the same way. Anyone promising a simple toggle that restores true window-based Auto Profiles on Wayland is promising something the upstream project itself does not claim.
What still works on Wayland
The limitation is specific, not total. AntiMicroX itself runs on Wayland, mapping works, profiles can be loaded and switched manually, and multiple Sets inside a profile still work, including switching sets with a controller button using One Way, Two Way or While Held behaviour as documented for Sets. In practice, many users replace automatic switching with fast manual switching: keep AntiMicroX open or in the tray, assign memorable profiles per game, and load the right one before playing. Set switching deserves special attention because it survives the move to Wayland intact. If your per-game differences are modest — a different layout for menus versus gameplay, for example — one profile with well-planned Sets can cover what Auto Profiles used to juggle across several files.
Practical workarounds, honestly labelled
Workaround one is session choice: if your distribution and hardware allow it, logging in to an X.org session for gaming restores the environment Auto Profiles were built for. That is a real option for some users and an unacceptable regression for others, so treat it as a choice, not a recommendation. Workaround two is launcher habits: start AntiMicroX with the game, load the profile as part of your pre-game routine, and name profiles clearly enough that the manual step takes seconds. Workaround three is to reduce how many profiles you truly need by using Sets and per-game in-game bindings more aggressively. What not to do is install random scripts claiming to restore window detection without understanding what permissions they need; a tool that watches your windows is exactly the capability Wayland restricts for a reason. If startup itself is also failing on Linux, separate the problems using our guide to AntiMicroX not opening before mixing the two diagnoses.
Setting expectations for the future
AntiMicroX is community maintained and, per its own README, looking for a new maintainer, with limited support and no new features expected unless external contributors build them. That context matters here: a Wayland Auto Profiles solution would need both a viable technical path within Wayland’s design and a contributor to build it. Neither is promised, and release notes for recent versions show maintenance work — Flatpak and X11 fixes in 3.6.1, for example — rather than a Wayland profiling breakthrough. Keep your system and AntiMicroX current from the download page, because compositor behaviour does evolve, but plan your workflow around the documented present: manual profile loading on Wayland, Sets for in-profile flexibility, and X.org if automatic switching is essential to you. That plan works today, which no promised fix can guarantee.
Checking which session you are actually in
Many users are moved to Wayland by a distribution update without choosing it, so confirm your session type before concluding Auto Profiles are broken. On most Linux desktops you can check the session type from a terminal by looking at the session information your environment provides, or from the login screen’s session selector, which often lists separate Xorg and Wayland entries. If you recently upgraded your distribution and Auto Profiles stopped at the same moment, a silent switch of default session is a very plausible explanation, and it fits the documented limitation exactly. Record your compositor as well as your distribution when you ask for help, because Wayland behaviour is implemented per compositor, not by a single shared program. That detail also explains why a friend’s identical AntiMicroX settings can behave differently on a different desktop. None of this changes the documented position — window-based Auto Profiles are not a Wayland feature today — but knowing your session stops you debugging the wrong layer.
Keep exploring
- General AntiMicroX troubleshooting guide — the cluster overview for all common faults.
- Download AntiMicroX 3.6.1 — official GitHub release channel with hash information.
