Skip to main content
Everything Ryoku does from a keybind or a Settings page is also a command, so anything the desktop can do, a terminal (or a script of yours) can do too. This page is the map. The commands that matter most on a daily driver come first; the rest is reference.

The five that matter

If something feels wrong, the order is ryoku doctor, then ryoku update, then ryoku rollback. recovery is for a machine that cannot help itself.

ryoku, the system CLI

The front door to the machine. Full detail on The ryoku command; the short version:
ryoku keyboard apply exists because the disk passphrase prompt reads a copy of the keymap baked into the boot image at build time. Changing the layout anywhere else, even with localectl, never reaches it; the rebuild does.

ryoku-shell, the desktop’s remote control

Every surface the shell draws answers to ryoku-shell <verb>, which is what the keybinds call. Useful from a terminal when scripting or diagnosing:

Desktop helpers

The small tools behind keybinds and Settings pages. All on $PATH, all fine to call directly:

Hardware and power

Where these live

The ryoku CLI is Go under ryoku/cli/; the shell daemon and its verbs are ryoku/shell/ipc/; the ryoku-cmd-* helpers are shell scripts in ryoku/hyprland/scripts/; hardware tools live in system/hardware/. Every one of them ships in the packages, so a script that works on your machine works on any Ryoku install.
Last modified on July 29, 2026