Rules and Config

Managed Files

float-app stores its registry at ~/.config/float-app/config.json. The registry records the selected Hyprland config and the managed rules.

Rules are generated beside your Hyprland configuration as ~/.config/hypr/float-app.lua or ~/.config/hypr/float-app.conf. Do not edit this generated file by hand.

The selected config receives a marked include block. Existing blocks are updated rather than duplicated. If that config is a symlink, float-app writes through to its target instead of replacing the link.

Config Selection

The selected config must be a .lua or .conf file under ~/.config/hypr. float-app remembers the first selection. Pass --config <path> to select another file when adding or removing a rule.

Matching

Rules match either class or initial_class exactly. Application classes are escaped before being written as RE2 patterns, so punctuation is treated literally.

Each match adds the floating-window tag. Unless an existing Omarchy floating-window rule is detected, the generated file also floats, centres, and sizes tagged windows to 875 by 600. float-app looks for that rule under ~/.config/hypr and in Omarchy’s defaults, under $OMARCHY_PATH when Omarchy is dev-linked to a source checkout as well as /usr/share/omarchy.

With Omarchy’s Lua config, rules go through Omarchy’s o.window helper, so Omarchy’s floating workspaces leave those apps at their own size. Omarchy only records class and title matches for this, so an initial_class rule still takes the floating workspace’s size there.