Compatibility¶
This page answers one question: will Amri detect which window has focus on your system, and detect your games. Both feed auto-switch, where a profile activates on its own when the game or application it claims takes focus.
Why focus detection matters¶
Focus detection is how Amri knows which window is in front. Per-app profile switching reads that signal to pick the right profile, so the commands for the window you are looking at are the ones that are live. If Amri cannot see the focused window on your desktop, auto-switch by window still falls back to game detection (below), and you can always switch profiles by voice or by a key.
Supported desktops¶
Amri detects the focused window on X11 and on several Wayland desktops. It picks the right method for your session automatically.
| Environment | Focus detection |
|---|---|
| X11 (any desktop) | Supported |
| KDE Plasma (Wayland) | Supported |
| GNOME (Wayland) | Supported, through the desktop accessibility interface |
| Wayland compositors built on wlroots (Sway, Hyprland, and similar) | Supported |
| Other Wayland compositors | Not detected; Amri tries the wlroots method and reports if it is unavailable |
When no display server is detected, focus auto-switching is disabled and Amri continues to run every other way. Voice profile switches and a profile-override key still work.
Wayland is stricter than X11
Wayland does not expose focus the way X11 does, so each desktop needs its own method. X11, KDE Plasma, GNOME, and wlroots-based compositors are covered. A Wayland compositor outside that list may not report the focused window to Amri.
Game detection¶
Amri detects a running game two ways:
- By Steam AppID. For any Steam-launched game, Amri detects the game by its AppID from Steam directly. This is reliable on every supported system, including ones where the game window is not reported to focus detection.
- By focused window. Where focus detection is available, Amri also matches a game or application by its window title or process name.
A profile advertises its games with steam_app_ids and app_match. See
auto-switch for both fields and a full example.
Prefer the AppID for games
On KDE Plasma under Wayland and on the Steam Deck, the game window is not
reported to Amri's focus detection, so window matching cannot see a running
game there. The Steam AppID is detected regardless. List steam_app_ids for
any game, and reserve app_match for desktop applications.
Steam Deck¶
Amri runs on the Steam Deck. Games are detected by their Steam AppID, which is the path that works there. Window-based focus detection under the Deck's compositor is not relied on for games.