Omarchy

phux omarchy setup

Then:

Inside phux, the keys are the ones Omarchy’s tmux config uses, so your hands already know them. Switch Omarchy’s theme and phux repaints to match.

What setup changes

phux omarchy setup is safe to run again. It prints every file it writes, and --dry-run prints them without writing anything.

Omarchy gives Super Ctrl Return and Super Ctrl K to Herdr out of the box; setup rebinds them to phux. Omarchy’s tmux keys, Super Alt Return and Super Alt K, are left alone.

setup never edits text outside its marked blocks:

-- >>> phux: managed by `phux omarchy setup`; `phux omarchy remove` deletes it
o.rebind("SUPER + CTRL + RETURN", "Phux", "omarchy-launch-terminal /home/you/.local/bin/phux")
o.rebind("SUPER + CTRL + K", "Phux keybindings", [[sh -c '/home/you/.local/bin/phux omarchy keys | omarchy-menu-select "Phux keybindings" -- --width 800']])
-- <<< phux

The blocks name the phux binary by its full path, because Hyprland’s PATH may not include ~/.local/bin. If you move phux, for example from the install script to a package, run setup again. An Omarchy that still uses hyprland.conf gets the same blocks in bindings.conf and autostart.conf.

Check what’s in place:

$ phux omarchy status
✓ omarchy
✓ distro
✓ theme
✓ theme_hook
✓ desktop_keys
✓ autostart

Keys

The prefix is Ctrl Space, as in Omarchy’s tmux. A tmux window is a phux tab, and a tmux session is a phux session.

Everything else keeps phux’s default keys. Three moved to make room for tmux’s: prefix a jumps to the next pane waiting for you (phux’s prefix q), resizing uses Ctrl Alt Shift and the arrows instead of prefix R, and Ctrl Alt and the arrows move between panes instead of prefix h and k.

phux omarchy keys prints every key in effect, your own bindings included, one per line. That is the list Super Ctrl K shows.

Your settings still win

The layer sits under your own config.toml, so any key you set there wins. To change one of the keys above, bind it in your config:

[keybindings.prefix-table]
"q" = "next-attention"

To keep the opaque status bar and sidebar of phux’s own theme instead of letting the terminal’s background show through, set the theme slot:

[theme]
surface = "#1a1b26"

Setup rewrites the layer each time it runs. Put changes in your config, not the layer.

Themes

phux reads Omarchy’s colors.toml as it is, so its sidebar, status bar, pane borders and popups use the theme’s colours. When you switch themes, Omarchy runs the theme-set hook, which runs phux config reload, and attached clients repaint without detaching. Programs inside your panes use your terminal’s colours, which Omarchy changes itself.

If your config already selected a theme before setup, setup keeps it and tells you. To follow Omarchy’s theme afterwards:

phux theme set --file ~/.local/state/omarchy/current/theme/colors.toml

Undo it

phux omarchy remove

This restores the distro you had selected before setup, stops following Omarchy’s theme if setup turned that on, and deletes the hook, the layer and the marked Hyprland blocks. Everything else in those files is left as it was. Omarchy’s own bindings for Herdr come back when Hyprland reloads.