04 — Caelestia Shell

CONFIG Sources: shell.json and active Hyprland autostart.

Active modules

• Launcher: fuzzy app/action/wallpaper search, LibreWolf favourite, Vim keys.
• Dashboard: enabled, hover reveal, 500 ms media interval.
• Sidebar: enabled with an 80 px drag threshold.
• Bar: logo, workspaces, active window, tray, clock, status, and power.
• Media: Spotify is the default player; the visualiser uses 69 bars.
• Session: shutdown, reboot, logout, and hibernate are configured state-changing actions.

READ ONLYShow help for the installed CLI

Copy

caelestia --help

Expected: A command list; no system change.

READ ONLYRead the current colour scheme

Copy

caelestia scheme get

Expected: The active scheme name and colours.

hyprland.conf → ~/.local/bin/qs-caelestia → shell.json
              → state/scheme.json → bar, launcher, dashboard, sidebar

cli.json, hypr-vars.lua, and hypr-user.lua did not exist during the audit, so no behaviour is attributed to them.

Inspect and change safely

The visible symptom determines the layer to inspect. A missing launcher or sidebar first points to the Quickshell process and logs; an incorrect colour points to scheme state; a wrong action points to the generated binding and its dispatcher. Do not replace the complete shell configuration for one local symptom.

Both commands above are READ ONLY. caelestia scheme get confirms what the installed CLI reports, but it does not prove that GTK, Kitty, or every already-running application has reloaded that scheme. Before editing JSON, create a copy, keep the document valid, and change one field. Verify the exact module, then restore the copy if startup or rendering regresses.

Related: Desktop model, Theme system, and Troubleshooting.