Stop hyprpm asking permission to load plugins on every login
Checked against Hyprland v0.56.2 source and this workstation, omarchy 4.0.2-1 and hyprland 0.56.2-1. The record's headline symptom cannot occur on a stock Omarchy 4 install, and its cause statement about enforcement being off is the reverse of what the code does. Confirmed live here that hyprctl getoption ecosystem:enforce_permissions returns bool: false with set: false, so Omarchy 4 leaves the value at Hyprland's own default. In src/managers/permissions/DynamicPermissionManager.cpp, both clientPermissionMode and clientPermissionModeWithString open with a read of ecosystem:enforce_permissions and if (*PPERM == 0) return PERMISSION_RULE_ALLOW_MODE_ALLOW;, which returns before any rule walk and before askForPermission is ever called. So with enforcement off there is no popup at all, not a popup without remember as the record claims. The wiki's BSD paragraph is where that claim comes from and it does not match 0.56.2, so the page is kept as a source for the rest but the sentence was dropped. The record's fix then makes it worse by telling an Omarchy 4 reader to set enforce_permissions = true, which switches on ASK prompts for screencopy, cursorpos and input-capture system wide in order to suppress one prompt they were not getting. The fix is rewritten to check the option first and branch. Two mechanics were added after reading the source. src/plugins/PluginSystem.cpp calls clientPermissionModeWithString(pid, path, PERMISSION_TYPE_PLUGIN) with no wl_client, and in askForPermission the {Deny, Allow and remember, Allow once} option set requires !binaryPath.empty() && client, so a plugin prompt only ever offers Deny and Allow: there is no remember button for plugins. And the grant is stored nowhere on disk. Rules live in the manager's in-memory m_rules vector with no write path, and the cache entry matches on e->m_pid, so each new hyprpm process is asked again. The only file that persists a grant is the Lua config holding hl.permission, ~/.config/hypr/hyprland.lua on Omarchy 4. Confirmed the record's table form is valid: hlPermission in src/config/lua/bindings/LuaBindingsConfigRules.cpp accepts both {binary, type, mode} and the three positional strings, and /usr/share/hypr/stubs/hl.meta.lua declares permission fun(spec: HL.PermissionSpec). Confirmed hyprland-guiutils 0.2.2-2 is installed here and that the no-hot-reload claim holds, both from the wiki and from the comment at lines 67 and 68 of the shipped /usr/share/hypr/hyprland.lua. Frequency lowered from common to rare, because the state is reachable only for someone who deliberately enabled a feature that both Hyprland and Omarchy 4 ship off. NOT exercised: enforcement was not enabled and no dialog was triggered, since that would mean writing to the operator's live config and restarting the session.
Do not blanket-allow plugin for hyprctl. Anyone who can reach your hyprctl socket could then run hyprctl plugin load /tmp/malicious.so inside your compositor. Allow the hyprpm binary path specifically. Likewise a blanket screencopy allow for .* lets any local process silently record your screen. The opposite mistake is worth naming too: switching ecosystem:enforce_permissions on and then pasting broad allow rules to stop the resulting prompts leaves you worse off than the Omarchy 4 default, which at least does not claim to enforce anything. If you enable it, add narrow rules only for binaries you can name.
Symptom
You turned Hyprland's permission enforcement on, and now every hyprpm reload, including the one in your autostart, pops a Hyprland dialog asking whether to let hyprpm load a plugin. The plugins only load if you click Allow. The dialog offers only Deny and Allow, with no option to remember the choice, so it returns on the next run even inside the same session. On a stock Omarchy 4 install you will not see this at all, because permission enforcement is off by default and nothing is ever asked.
Cause
Hyprland's permission system gates plugin loading and the plugin permission defaults to ASK, but the gate is only reached when ecosystem:enforce_permissions is true. In Hyprland 0.56.2 both entry points in src/managers/permissions/DynamicPermissionManager.cpp read that option first and return PERMISSION_RULE_ALLOW_MODE_ALLOW immediately when it is 0, so with enforcement off no rule is consulted and no dialog is drawn. Omarchy 4 ships it off: on a stock 4.0.2-1 install hyprctl getoption ecosystem:enforce_permissions reports bool: false and set: false, and /usr/share/omarchy sets no permission rules of its own. Once enforcement is on, a plugin load arrives through clientPermissionModeWithString with no wl_client, and that branch builds the dialog with only Deny and Allow. The allow and remember option exists only where a wl_client is present, which covers permissions such as screencopy and never covers plugins. Nothing is written to disk either way: granted rules live in an in-memory vector for the life of the compositor, and a cached grant is keyed on the requesting process id, so a fresh hyprpm process never matches an earlier one and is asked again. The only persistent grant is a config rule. hyprland-guiutils must also be installed, because without it Hyprland logs that it cannot ask and falls back to allowing.
Fix
Decide first whether you want the permission system at all, because on Omarchy 4 it is off and this problem cannot happen.
Check what you have:
hyprctl getoption ecosystem:enforce_permissions
If it reports bool: false, enforcement is off, hyprpm is never gated, and there is nothing to fix. That is the Omarchy 4 default. Do not turn enforcement on in order to stop a prompt you are not getting: screencopy, cursorpos and input-capture all default to ASK, so enabling it starts prompting for screenshots, screen sharing and cursor access across the whole system.
If it reports bool: true, you opted into the permission system and the fix is an explicit allow rule for the hyprpm binary. Put it in ~/.config/hypr/hyprland.lua on Omarchy 4, or in your main Lua config on any Hyprland 0.55 or newer:
hl.permission({ binary = "/usr/(bin|local/bin)/hyprpm", type = "plugin", mode = "allow" })
binary is a regex matched against the full path of the calling binary. On Omarchy 4 hyprpm is at /usr/bin/hyprpm and is owned by the hyprland package, so the pattern above covers it.
While enforcement is on you will also want to name the screen capture tools you actually use, rather than clicking through a dialog every time:
hl.permission({ binary = "/usr/bin/grim", type = "screencopy", mode = "allow" })
hl.permission({ binary = "/usr/(lib|libexec|lib64)/xdg-desktop-portal-hyprland", type = "screencopy", mode = "allow" })
Permission rules are deliberately not hot reloaded. hyprctl reload will not apply them. Log out and back in.
The dialog needs hyprland-guiutils. Confirm it is installed, because without it Hyprland cannot ask and quietly allows instead:
pacman -Q hyprland-guiutils
The older package name hyprland-qtutils is not what Omarchy 4 ships.
Verify
hyprctl getoption ecosystem:enforce_permissions reports the value you meant to have. With enforcement on and the rule in place, log out and back in, then hyprpm reload -n loads the plugins with no dialog and hyprctl plugin list names them instead of printing no plugins loaded.
Sources
- https://wiki.hypr.land/Configuring/Advanced-and-Cool/Permissions/
- https://wiki.hypr.land/Plugins/Using-Plugins/
- https://github.com/hyprwm/hyprland-wiki/blob/main/content/configuring/core/advanced-configuration/permissions.md
- https://github.com/hyprwm/hyprland-wiki/blob/main/content/hyprland-plugins/using-plugins.md
- https://github.com/hyprwm/Hyprland/blob/v0.56.2/src/managers/permissions/DynamicPermissionManager.cpp
- https://github.com/hyprwm/Hyprland/blob/v0.56.2/src/plugins/PluginSystem.cpp
- https://github.com/hyprwm/Hyprland/blob/v0.56.2/src/config/lua/bindings/LuaBindingsConfigRules.cpp