Skip to main content
Ryoku keeps its core deliberately small: a terminal, an editor, a browser, a file manager, and the shell that ties them together. Everything else, a game launcher, a streaming rig, a security lab, a full dev stack, is added on demand through Extras. An Extra is a bundle: a curated set of software installed together, so adding a whole workflow is one click instead of an afternoon of hunting packages and their drivers. Extras install software. For the small desktop widgets you place on the wallpaper (a stock ticker, a photo frame), see Plugins, a separate system.

​
Install a bundle

1

Open the Store

Press Mod + , for Ryoku Settings and open Store (under Add-ons). The Store browses shell plugins and Extras bundles side by side; each bundle is a card with a description and its live install state.
2

Pick a bundle and install

Open a bundle to see what it contains, then Install. Ryoku opens a floating terminal so sudo and the AUR helper have a real TTY, and streams progress as each item lands.
3

Watch it fill in

Items report present or absent state live, so the card updates as the bundle installs. Remove the same way: open the bundle and choose Remove.
Under the hood the actuator is ryoku-extras-install, and ryoku-hub fetches and caches the catalogue from the ryoku-extras repo (with an offline fallback to the cache). The Hub is the normal way in; the terminal drives the same actuator.

​
The bundles

Eleven bundles ship in the catalogue. Install as many as you like, they layer.
The CachyOS Kernel bundle is a kernel swap, not an app set. Read Kernels for the trade-offs, the rollback path, and how it is wired before you install it.

​
What a bundle contains

A bundle is a list of items, each one of three kinds. You never write or see the routing, the actuator picks the right path per item.
script items are arbitrary installers, so removing a bundle does not reverse them; uninstall those tools by hand. package items go through pacman -Rs, which refuses to drop anything another installed package still needs, so removing a bundle never breaks the rest of the system. Removing a plugin item deletes its files but keeps your placement in ~/.config/ryoku/plugins.json, so reinstalling drops it back where you had it.

​
From a terminal

The Hub is the normal entry point, but ryoku-extras-install drives everything from a shell. Bundle and item ids are the ones in the ryoku-extras catalogue (for example gaming, the-developer, cachyos-kernel).
Set RYOKU_EXTRAS_DRYRUN=1 to print the plan without touching the system:
ryoku-hub owns the network and the cache. The ryoku-pkg-* and installer helpers only read the already-cached catalogue, they never fetch on their own, so a dry run and a real run see exactly the same plan.

​
Notes

  • Multilib is handled for you. A bundle that needs 32-bit libraries (Steam and the lib32 overlay in Gaming, for instance) declares requires: ["multilib"], and the actuator enables the [multilib] pacman repo with ryoku-pkg-multilib before it routes any package. The CachyOS Kernel bundle likewise pulls in the CachyOS repo the same way.
  • Live per-item status. The actuator publishes a JSON report per bundle under $XDG_RUNTIME_DIR/ryoku-extras/<id>.json; the Hub watches it, so the Store updates in place as a bundle installs or removes.

​
See also

Plugins

Small desktop widgets and frame popouts, a different system from software bundles.

Kernels

The CachyOS Kernel bundle in depth: trade-offs and rollback.

Ryoku Settings

The Hub’s Store and every other panel, opened with Mod + ,.
Last modified on July 4, 2026