ryoku-shell Go daemon — paints everything else: the frame, the bar,
the launcher, the overview, the screenshot tool, and the desktop widgets.
This page is a map of those surfaces. For the keyboard workflow — opening,
focusing, moving, and tiling windows — see Navigation; to
configure any of it, see Settings.
Shell surfaces
- Frame. The rounded screen border and the popouts that melt into it. Always present; it is the desktop’s signature chrome.
- Bar. The top bar and its popouts. QS Bar, the default, is a full-width top bar carrying the launcher, workspaces, the clock, media, the tray, and status; Sumi is a minimal left rail. Choose and arrange either in Ryoku Settings (Bar Studio). Notifications, the update island, and the GNOME keyring prompt grow from the frame.
- Launcher. The command palette (
Mod + Space): apps plus quick prefixes —=calc,;clipboard,?web,/actions,@YouTube Music, and\a Rashin ask — over a zero-query rest card with the solar-arc clock and weather. - Overview. The full-screen workspace expo (
Mod + Tab): scaled mini-desktops with live window previews. Click to switch or focus, drag windows between workspaces, and step between desktops. The Navigation page covers it in full. - Switcher. A full-screen most-recently-used window switcher. Day to day you
cycle windows through the overview above and directional focus (
Mod + Arrow); see Navigation. - Ryoshot. Screenshot capture (full screen, region, or window) and
annotation — rectangles, arrows, pen, marker, blur, and text, with undo/redo.
Mod + Shift + Sopens it; shots save as PNG to~/Pictures/Screenshots. - Keyring prompt. The GNOME keyring password prompt, grown from the frame rather than a floating dialog. System-driven — it appears when an app needs your keyring unlocked.
- Desktop widgets. A clock, a calendar, and a music player painted on the wallpaper. Right-click to move or configure; enable and lay them out from Settings → Desktop Widgets.
ryoku-shell, in ryoku/shell/ipc/) is the control plane: it
supervises the persistent components and decides what is on screen, and the QML
frontend renders it. Theme tokens flow from the wallpaper through matugen, so
picking a new wallpaper repaints every surface without restarting anything.
Getting around
Nothing is open when you log in — Hyprland is a tiling compositor, so it only shows what you launch. Open a window withMod + Return, move focus with
Mod + Arrow, and switch workspaces with Mod + 1 … 0.
Navigation walks the whole workflow — opening, focusing,
moving, resizing, floating, workspaces, the scratchpad, and multi-monitor.
Keybindings is the exhaustive bind reference.
Where things live
The Hyprland load order from
hyprland.lua is: base modules, then the active
theme, then settings (what the Hub writes), then user (your overrides,
which win). Customize covers what to put in each layer, and
Settings documents the Hub that writes the settings layer.
Logs
ryoku-shell is autostarted by Hyprland at login; ryoku reload restarts it
and rewrites the log above.
Next steps
- Navigation: the keyboard workflow for windows and workspaces.
- Settings: the Hub — every panel that configures the desktop.
- Keybindings: the full shipped reference.
- Customize: wallpapers, themes, and
user.luaoverrides.

