Skip to content

How goat installs

Gabriel Gonzalez Manana edited this page Oct 12, 2026 · 1 revision

How goat installs

./install.sh links each part of the repo into place, so the repo stays the single place to edit. Keep it where you cloned it. Re-running it is safe.

Folder What it is Linked to
theme/ Palette, wallpapers, lock-screen logo, icon set name ~/.config/omarchy/themes/goat
icons/ build.py draws the goat-cream folder icons (Yaru for the rest) ~/.local/share/icons/goat-cream
daynight/ Swaps each wallpaper for its night twin at sunset run by the hooks
harmony/ Themes Zen and GTK apps from the active palette run by the hooks
hooks/ post-boot starts the wallpaper daemon; theme-set reruns harmony and daynight ~/.config/omarchy/hooks/*.d/goat
hypr/ Monitors, hotkeys, frosted glass, workspaces, startup layout and scripts ~/.config/hypr/
shell/ Bar layout, widget settings, plugin list, and the notifications plugin restored into ~/.config/omarchy/

Apps Omarchy already themes from colors.toml follow goat on their own: terminals, Brave and Chromium, VS Code, Obsidian, Neovim, btop, tmux, and the Claude app.

Saving bar changes

Omarchy rewrites its own bar settings, so they're restored from a saved copy rather than linked. After changing the bar or adding a plugin, save it back:

./install.sh --export

Uninstalling

./uninstall.sh

This removes every link, puts back any file goat replaced (kept as *.goat-bak), stops the wallpaper daemon and removes the Zen and GTK styles. Plugins installed from git and your bar layout stay.

Careful: omarchy refresh hyprland writes Omarchy's defaults through the links into the repo. Restore with git checkout if you run it.

Clone this wiki locally