Skip to content

Latest commit

 

History

1 Commit

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Permission Center

A control panel for Hyprland's permission system (≥ 0.56, Lua config provider) on Omarchy v4 ("Quattro") — honest about how that system actually works.

  • Enforcement switch — see whether ecosystem:enforce_permissions is live right now, and stage it on/off for the next restart.
  • Managed rules — one-click starter rules (allow screencopy for grim and the desktop portal so screenshots/screen sharing keep working, ask before hyprpm loads plugins, deny plugin loading via hyprctl — the wiki's hardening advice), removable per row. Stored in a single file in Omarchy's sourced toggles directory, so no Hyprland config file of yours is ever touched.
  • Your own ruleshl.permission(...) calls declared anywhere in ~/.config/hypr/*.lua are shown read-only.
  • Restart-aware — Hyprland registers permission rules only at startup, never on a live reload (a security decision upstream). The panel says so instead of pretending changes applied.

Install

omarchy plugin add https://github.com/devmobasa/omarchy-permission-center --enable
omarchy-shell shell toggle community.permission-center '{}'

What it will not do

  • List live grants: Hyprland exposes no runtime read API for permissions.
  • Persist prompt answers: "allow and remember" lives in compositor memory until Hyprland exits; only config rules are durable.
  • Restart Hyprland for you.

Tests

./test/all   # node model + contract + static QML checks, manifest, qmllint

License

MIT

About

Manage Hyprland's permission system: enforcement, screencopy/plugin/input rules, restart-aware

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages