RSS
Built with Claude

yami: a pixel-art desktop shell for niri, with its own files, viewer and player

yami is a pixel-art desktop for the niri Wayland compositor, built in Rust as a light shell with separate modules for files, viewing, playing, screenshots and login.

Computer monitor on a wooden desk illustrating the yami pixel-art desktop shell for niri
Photo by ilya on Unsplash

What is yami?

yami is a pixel-art desktop for the niri Wayland compositor, built in Rust as a shell with separate modules for files, viewing, playing, screenshots and login, from the Trendorin/yami repository.

The shell, yami-shell, draws the bar, launcher, dock, notifications, lock screen, widgets and settings itself, in Rust with no toolkit, and idles at about 15 MB of RAM.

The file manager, image viewer, player, screenshots and login screen are modules of their own, so a reader can take the whole desktop or only the pieces an existing setup needs, and every app follows the same palette, with updates arriving signed as ready binaries on x86_64.

It uses software rendering into shared memory through layer-shell, with no GPU context, no toolkit and no JavaScript, and redraws only happen when something changes.

Who is yami for?

yami is for Linux users who use the niri Wayland compositor, or want a finished desktop built around niri on Linux with Wayland.

The installer covers eight distributions: Arch, Fedora including atomic, Debian/Ubuntu, openSUSE, Void, Alpine, Gentoo and NixOS.

It also fits a reader who wants one piece without the shell: the modules work without the yami shell, yami-files and yami-view work on any Wayland compositor, yami-play needs libmpv, yami-shot needs layer-shell and grim, and yami-greet needs greetd and niri.

The interface is available in eight languages: English, Russian, Brazilian Portuguese, Spanish, German, French, Ukrainian and Polish, switchable live in settings, and the modules, the login screen and the installer speak them too.

Is yami free and open source?

yami is free and open source: its code is under the MIT License, which grants permission free of charge.

  • Platform: Linux with Wayland.
  • Language: Rust.
  • Rust 1.89 or newer is needed to build the shell.
  • Ready binaries need x86_64 with glibc 2.34 or newer.
  • The README names niri 26.04.
  • License: MIT for the code; bundled fonts keep their own SIL Open Font License texts.
  • Latest release: the latest release as of November 18, 2026 is 3.0.0, published November 12, 2026.
  • GitHub stars: about 200 GitHub stars as of November 18, 2026.
  • Idle size: the shell idles at about 15 MB of RAM.

What stands out

  • A complete shell in one program: bar, app launcher with clipboard history, power menu, lock screen with PAM, notification server with history and do-not-disturb, system tray, calendar, sound, music, network, Bluetooth and system popups, and its own polkit password window.
  • One palette everywhere: seven presets or any custom accent recolour the shell, wallpaper, niri borders, kitty, foot, cava, starship, btop, fastfetch, Qt and KDE and GTK apps, the pixel cursor and the login screen at once, and custom templates can recolour any other app.
  • Standalone modules: yami-files offers tabs, split view, devices, network shares and the file dialog of every app that uses the portal; yami-view offers rotate, flip, crop, save as and wallpaper; yami-play offers every format ffmpeg knows, subtitles and audio tracks, a folder playlist and resume where playback stopped, and it provides no media content of its own.
  • Screenshots and a stream curtain: Print freezes the screen under a pixel overlay for area, window or monitor capture, with pen, frame, arrow, marker, mosaic and numbered badges, text recognition and QR codes; Mod+Shift+H covers a stream with a frozen blurred screen while the desktop stays usable, and this curtain needs yami-niri, while on other niri the windows turn black in the stream instead.
  • Widgets, dock and bar that move: desktop widgets for clock, calendar, weather, Bluetooth devices, script output, music and CPU, RAM, temperature and network graphs; a pixel dock on any edge; and a bar that can sit on the top, bottom, left or right edge.

How do I install yami?

yami installs with one installer command from the project's README, run as yourself and not with sudo, followed by logging out and picking the Niri session.

From the project's README at https://github.com/Trendorin/yami, with releases at https://github.com/Trendorin/yami/releases, the install command is:

bash <(curl -fsSL https://raw.githubusercontent.com/Trendorin/yami/main/install.sh)

On x86_64 with glibc 2.34 or newer, a release installs ready binaries with a checked signature, with no compiler, in a few minutes, and anywhere else it builds from source.

Where the distribution has no niri 26.04 or newer yet, namely Debian 13 and Ubuntu 26.04, niri and xwayland-satellite are built once from source, needing a compiler and about half an hour.

The installer installs only the base, niri, the shell, a terminal and what the desktop cannot start without, asks for the password once where it is needed, and before anything else says how long it will take and how much disk it needs.

The first-run setup meets the reader at first login, one topic per screen, and it can be opened again at any time with yami setup, while running the same install command again later updates and repairs what is there and keeps the reader's choices.

Packages for Arch, Debian, Fedora, Gentoo and Nix are described in the project's packaging documentation, and on NixOS the flake is used instead, with a NixOS module for the system half and a Home Manager module for the home half.

From the project's README, the shell can also be built by hand with the following commands:

cd shell
cargo build --release --locked
install -Dm755 target/release/yami-shell ~/.local/bin/yami-shell

How it was built with Claude

The README has a Made with Claude section stating that yami is written with the help of Claude by Anthropic, through Claude Code, and that much of the code, the yami-niri patches and the docs came out of those sessions.

Commits in the repository carry a Co-Authored-By trailer naming Claude, and the README states that every change is still built, checked and used every day on a real machine before it ships.

Try it with your AI. Use this prompt with your own AI assistant to plan a yami install from the README, without changing the official commands.

Help me plan installing yami on [my Linux distribution and version] using only the
official commands and interfaces named in the README of Trendorin/yami. First, check
what the README says about my distribution, niri 26.04, Rust 1.89 or newer for building
from source, and glibc 2.34 or newer for ready binaries on x86_64, and tell me which
install path applies. Show me the exact installer command from the README, and show any
risky step first and wait for me to confirm before I run anything. Do not install
anything from unknown sources, do not touch credential files, and do not delete
anything. Then help me choose which modules I want from yami-files, yami-view,
yami-play, yami-shot and yami-greet, which palette from [palette name], and whether to
open the first-run setup again with yami setup. Explain what to check after logging into
the Niri session, and stop at any step the README does not describe.

What are yami's limits?

yami's limits are platform, binary and feature limits: it is a Linux Wayland desktop for niri, ready binaries cover only x86_64 with newer glibc, and the stream curtain needs the yami-niri fork.

The privacy curtain needs yami-niri, and the security notes state that niri's Alt+Tab switcher draws above every layer and is not covered, and that wlr-screencopy capture with grim or OBS wlrobs is not covered.

The installer command runs code from the network, and the security notes advise reading install.sh first if the reader does not trust the source, and note that a dry-run shows the plan.

yami has no telemetry from the shell, and the install count is one anonymous request, once per machine, after an install has finished, which can be turned off with install.sh --no-count, YAMI_NO_COUNT=1 or DO_NOT_TRACK=1, while GitHub sees the IP address on any download, as with the git clone the installer already does.

Clipboard history skips entries password managers mark as secret, but anything else copied is stored until it is deleted.

On a machine shared with untrusted users, the security notes advise making the login screen look folder root-owned, because that folder belongs to the installing user so the palette and wallpaper can follow the shell.

The license is for the code and gives no rights to the project's name, so a fork or rebuild goes under its own name and logo and does not present itself as yami or as made by its authors, while bundled fonts keep their own licenses and yami-niri is built from upstream niri under GPL-3.0.

Vulnerabilities must not be posted in public issues; the security notes ask for a private report on GitHub, seen only by the maintainer.

Problems and feedback

Report problems on the project's Issues page at https://github.com/Trendorin/yami/issues, and use the private security report page for vulnerabilities instead of a public issue.

The yami report command builds an archive for an issue, with versions, doctor output, journal and configs without secrets, and the security notes state that nothing is sent and the archive is meant to be read before it is attached.

Source: yami repository and README, yami releases, yami issues, yami security notes, yami changelog, yami license, yami packaging documentation, yami shell Cargo.toml, yami private security report page

This story first appeared in the claudefox daily briefing for November 18, 2026.