Omaland

A GUI for Hyprland's visual look and feel.

An Omarchy shell plugin. Applies live as you drag, and saves plain Lua into your Hyprland config.

<br><br>

Install

omarchy plugin add https://github.com/bobby-nicholas/omaland.git --enable --yes

Open it from SUPER+SPACE › Omaland. No network access, no sudo.

To remove it, omarchy plugin remove bobbynicholas.omaland --yes. Your settings stay — they are plain Lua in the files Hyprland already reads. Hit Reset all first to undo them too.

What it edits

Colors are absent on purpose: Omarchy themes own general:col:* from a file that loads before looknfeel.lua, so writing them here would pin your borders and break omarchy theme set.

Keys

How it works

Where it writes. One fenced block per file — hl.config and hl.animation in looknfeel.lua, o.window rules in hyprland.lua. Nothing outside the fences is touched, and clearing every override removes the blocks and restores both files exactly.

Reading state back is done by Lua, not by a parser. read.lua runs the block against recording stubs for hl and o and reports what it set, so the block stays pure Lua with no state comments, and a hand-edit that breaks the syntax gets a real error instead of being silently misread. Needs lua, which hyprland already depends on.

Live preview uses hyprctl eval (Hyprland's Lua parser rejects hyprctl keyword), handed the same Lua that gets written on release, so preview and saved state can't drift. hyprctl configerrors runs after every write and surfaces in the footer.

The shell follows along. The Omarchy shell mirrors rounding and outer gaps into its own menu, notifications and panels, but only re-reads them at startup and on a theme change. Omaland asks it to re-read after every preview and save, so the whole interface tracks the sliders, not just the windows.

The launcher entry is installed by the plugin, because Omarchy has no install hook. Enabling writes ~/.local/share/applications/omaland.desktop; disabling or removing deletes it. Only a file carrying X-Omaland-Managed=true is ever touched, so your own entry at that path is left alone. The plugin's own directory is resolved from Qt.resolvedUrl() rather than from the manifest — the shell hands third-party plugins a sanitized manifest with __sourceDir stripped, so asking it where we live returns nothing.

Full opacity clears the opacity = "0.985 0.96" rule Omarchy applies to every window. That rule multiplies with the opacity sliders, so without the switch 100% still renders at 0.985.

Add this to ~/.config/omarchy/extensions/omarchy-menu.jsonc to turn Style › Hyprland into a submenu. Redeclaring the id with no action flips it to a submenu, and the original editor action moves into a child:

"style.hyprland": {"icon":"","label":"Hyprland","aliases":["hyprland","looknfeel"]},
"style.hyprland.omaland": {"icon":"󰸌","label":"Visual Editor","aliases":["omaland"],"action":"omarchy-shell shell toggle bobbynicholas.omaland"},
"style.hyprland.edit": {"icon":"","label":"Edit Config","action":"omarchy-launch-config-editor \"$HOME/.config/hypr/looknfeel.lua\""},

Development

manifest.json    plugin declaration (kinds: panel, service)
Panel.qml        state, hyprctl processes, file IO, layout
OptionRow.qml    one option row
Schema.js        the option catalogue
LuaConfig.js     render the managed blocks, read read.lua's output
Paths.js         locate the plugin's own directory from a QML file's URL
read.lua         runs a block against recording stubs to report what it set
Service.qml      installs and removes the launcher entry
test/run.js      node test/run.js

Adding an option is one entry in Schema.js. Plugin QML is cached by URL, so edits need omarchy restart shell.

License

MIT