Starsend

One signal against the dark.

Star's End is where the roads stop. Near-black ground, muted chromatics, and a single saturated amber carrying every focus state — everything that is not the signal gets out of the way.

Its ground is the darkest in the set at #05090a. And its border gradient is the only one that never reaches a second colour: it fades into itself, #f0913f to that same amber at a third of the alpha. One signal, dimming.

omarchy theme install https://github.com/r-bart/omarchy-starsend-theme.git
omarchy theme set starsend

Or use Install > Style > Theme in the Omarchy menu, then pick Starsend under Style > Theme (Super + Ctrl + Shift + Space).

Requires Omarchy 4. The palette uses the semantic key set, which does not exist in 2.x.

Window borders come from hyprland_active_border, which Hyprland and every shell card share. palette-check.png renders the whole palette into a simulated bar, terminal, menu and notification, if you want to judge the colour relationships without installing anything.

WCAG relative luminance, against both surfaces a theme renders text on. lighter_background is where tooltips, floats, status lines and Neovim's NormalFloat sit — the surface most palettes forget to check.

Every chromatic clears 4.5:1 on both. Body text clears 10:1.

colors.toml, icons.theme and backgrounds/. Nothing in this repository runs on your machine: no neovim.lua, no terminal config, no vscode.json.

Half a choice. Those three would be dropped whatever this repository did: a theme installed from a repo keeps only what is colour. The choice is the rest — a theme can ship shell.toml, btop.theme or helix.toml, and Omarchy keeps them, because omarchy-theme-set-templates only renders a template when the output file does not already exist. Leaving them out is what makes the entire desktop fall out of the palette, window borders included — and it is also why shell.toml is left to Omarchy's template, so this theme keeps picking up shell improvements on each release instead of pinning a snapshot.

No Hyprland config either, and that one is not a choice. Omarchy reads none from a theme directory, and omarchy theme install drops every .lua a cloned theme ships. The window metrics this design was drawn against are in Window metrics, to paste in yourself.

Five, cycled with Super + Ctrl + Space. The same five ship with every theme in this set; only the order differs. Omarchy picks the first in sort order, unless the background you were already on shares its filename with one of these — then it advances to the next, because omarchy-theme-set cycles from the current entry.

Two formats, and the reason is weight. Everyone who installs the theme clones backgrounds/ in full, and a wallpaper is decoded to the same framebuffer whatever it weighs. The two heaviest scenes are WebP and fall from 5.43 MB to 2.39 MB together. The other three are already under 2.2 MB and stay JPEG.

WebP is safe on Omarchy 4, and it was not always. qt6-imageformats — the Qt decoder Quickshell needs — reached the base package list on 19 August 2026, through the Add webp decoding to the shell migration. 79 of the 92 backgrounds Omarchy itself ships are now .webp, and omarchy-theme-set lists .webp among the extensions it accepts. On an install that predates the migration and has never updated, a WebP wallpaper fails at Error decoding: ... Unsupported image format and leaves a black desktop. Updating Omarchy is the fix.

All five are 2912×1632. The JPEGs are quality 95, baseline, with no chroma subsampling. Full chroma matters here. Every scene sets a saturated warm edge against a cold field, and 4:2:0 softens that edge. macOS sips writes 4:4:4 only at quality 100, which triples the file for no visible gain. These were built with cjpeg -quality 95 -sample 1x1 -optimize. The WebPs were re-encoded from them, capped at 4K wide, with magick input.jpg -strip -resize '3840>' -quality 82 output.webp.

Add your own in ~/.config/omarchy/backgrounds/starsend/ — they appear alongside these.

Not part of the theme. Omarchy never reads a Hyprland config from a theme directory; the only thing a theme sends the compositor is hyprland_active_border. To match the design, paste the block below into ~/.config/hypr/looknfeel.lua, which is loaded after both Omarchy's defaults and the active theme, so it wins over both.

This repository ships no .lua of its own, and none would survive if it did. omarchy theme install stages only what is colour and drops every .lua a cloned theme ships — a theme's Lua is code the compositor would run at login, and installing someone's theme should change what your desktop looks like, never what it runs. The block below is the whole of it, so this README stands on its own.

hl.config({
  decoration = {
    rounding_power = 4,

    -- The 0.05 gap is what marks the focused window.
    active_opacity = 0.90,
    inactive_opacity = 0.85,

    -- Translucency without blur makes text unreadable over these wallpapers.
    blur = {
      enabled = true,
      size = 6,
      passes = 2,
    },

    shadow = {
      enabled = true,
      range = 20,
      render_power = 4,
      color = "rgba(05090a99)",
      color_inactive = "rgba(05090a66)",
    },
  },
})

Omarchy 4 configures Hyprland in Lua, not .conf, and there is no ~/.config/hypr/hyprland.conf. Corner rounding is a machine-level setting that each person picks for themselves in ~/.config/hypr/looknfeel.lua, not something a theme has any say in. Omarchy ships 0; this palette is agnostic either way.

Worth knowing if you change it: the shell mirrors Hyprland's decoration:rounding into its own card corners, so rounding your windows also rounds the menu, launcher, notifications and tooltips. And it only re-reads that value on startup, on a theme change, and on the omarchy toggle window-gaps flag — a hand-edited looknfeel.lua plus hyprctl reload rounds the windows while the shell keeps the old radius until you re-apply a theme or restart it.

Same five wallpapers, different palette over them.

MIT. See LICENSE.