OpenLogi

Per-app profiles

Switch button actions and Actions Ring layouts by application, with focused or pointer-selected mouse profiles.

Per-app profiles change a device automatically when an application matches. Edit them in Buttons or Actions Ring.

A profile can override button actions and select an Actions Ring layout. OpenLogi matches the target application by its platform identifier.

What a profile changes

A button profile is a sparse overlay on the device's Default profile. An Actions Ring profile is a complete layout for the focused application.

  • Buttons — each listed button replaces the default with one action. Unlisted buttons inherit the Default profile. Gestures remain in the Default profile.
  • Actions Ring — a matching focused application uses its complete saved layout. It does not merge with the default layout.

A button override can replace a gesture-capable button with one action. Clear that override to restore the default gesture map.

Add and manage a profile

Select a device, open Buttons or Actions Ring, and use the Profile selector. The two editors have independent profiles for the same application.

The Add app profile picker open over the Buttons tab

Add app lists recent applications first.
  1. Select Add app.
  2. Choose an application from Recent applications or All applications.
  3. Change a button or an Actions Ring slot to save a profile.

Recent applications contains foreground applications that the agent observed. Choose it when possible, because its identifier is the runtime identifier.

All applications is an installed-application catalog. Its selected identifier is platform-specific, so it might not equal an application's runtime identifier.

Selecting an application creates an editor draft, not an empty entry in config.toml. Switching profiles in the editor never forces the runtime to use that profile.

Use Profile options to change the selected profile:

  • Reset to default… removes custom settings in the current editor. The editor remains on that application. It does not change the other editor or another application.
  • Remove profile… removes the current editor's profile and returns that editor to Default. It does not change the other editor or another application.
  • Delete all app settings… removes that application's button bindings and Actions Ring layout on this device. Other applications, devices, and default settings remain unchanged.

Choose the mouse target

In Settings, set Mouse button profiles to Mouse pointer or Focused application. The setting also persists in config.toml.

schema_version = 9

[app_settings]
mouse_profile_target = "pointer" # Or "focused".
  • Mouse pointer is the default. Mouse profiles follow the identified window under the pointer. The desktop uses global bindings.
  • Focused application makes mouse profiles follow keyboard focus. Keyboard profiles always follow keyboard focus.

Pointer targeting works on macOS, Windows, and X11. On unsupported sessions, OpenLogi uses the focused application.

If OpenLogi cannot identify the pointer surface, it also uses the focused application. This includes a system overlay or a failed lookup. With no focused application, OpenLogi uses global bindings.

OpenLogi never focuses a background window to send input. In pointer mode, a binding that produces keystrokes or runs a workflow runs in the focused application when that application binds the button the same way. A global shortcut therefore works over the desktop and over unfocused windows.

A button that the hovered application binds differently, through a per-app profile on either side, is skipped for an unfocused hovered window. It does not run in the focused application. Global actions, such as switching desktops, can run without changing focus.

The Actions Ring always selects the foreground application. It does not use the pointer target.

Identifiers and Linux backends

Profile keys match the reported identifier exactly. OpenLogi does not support wildcards or pattern matching.

PlatformReported identifierExample
macOSBundle identifier, or executable path without a bundle identifiercom.microsoft.VSCode
Linux (X11 / XWayland, GNOME Shell)WM_CLASS classCode
Linux (wlroots compositor, including Sway or Hyprland)xdg-shell app_idcode
WindowsLower-cased executable path, or exe:<filename>.exeexe:sharex.exe

On Windows, an exact executable path wins over exe:<filename>.exe. Use the exe: form when a Store or self-updating application's path changes.

Linux WM_CLASS and xdg-shell app_id identifiers are separate namespaces. A wlroots profile does not match on GNOME or X11, and vice versa.

GNOME Wayland requires the installed and enabled OpenLogi GNOME Shell extension for native windows. Without it, the X11 backend matches only XWayland windows.

KDE KWin does not expose the wlroots protocol. In v0.8.15, native KDE Wayland windows have no dedicated foreground-application backend.

Share a profile across platforms

Use an [apps] alias when one profile must match the same application on macOS, Linux, and Windows. Reference the alias with an app:<alias> profile key.

schema_version = 9

[apps.chrome]
name = "Google Chrome"
macos = "com.google.Chrome"
linux = ["google-chrome", "Google-chrome"]
windows = "exe:chrome.exe"

[devices."unit:6be9d300".per_app_bindings."app:chrome"]
Back = "PrevTab"

Each macos, linux, or windows field accepts one identifier or an array. An alias without an identifier for the current platform remains in the file but does not apply there.

The same selector works in per_app_bindings and action_ring.per_app. OpenLogi uses this precedence order:

  1. Exact identifier.
  2. Windows exe:<filename>.exe selector.
  3. Alias that lists the exact identifier.
  4. Alias that lists the exe:<filename>.exe selector.

A platform-specific profile therefore wins over an alias profile. Config loading stops when an app: profile names no alias.

Config loading also stops for empty identifiers, an identifier beginning with app:, duplicate identifiers on one platform, or upper-case Windows identifiers.

The GUI shows alias profiles but does not create aliases. It uses the configured name, an agent-reported name, or the alias name. It uses the first identifier's platform icon. Edit config.toml to create or change aliases.

Status: button profiles and Actions Ring layouts work on macOS, Linux, and Windows. Pointer targeting works on macOS, Windows, and X11. Application identification uses operating-system APIs, not HID++.

On this page