Lumi.

Linux, with a point of view

A quieter system. More room to make it your own.

Lumi is an opinionated Linux built on openSUSE Tumbleweed, with a custom desktop for developers and the agents working beside them.

Read the build log

Early development. No release to download yet.

One coherent Core. Room to grow.

Strong defaults.
Less housekeeping.

The Core is designed to stay useful on its own. Optional modules add capabilities without becoming prerequisites.

Desktop

Start at the keyboard.

Search with a double tap of Super. Find your windows at a glance. Use the built-in cheatsheet when a shortcut slips your mind. The mouse is still welcome.

Maintenance

Keep a way back.

The design pairs tested rolling snapshots with restore points before risky changes. One update command covers the system and its apps; recovery is part of the plan, not an afterthought.

Consistency

One theme, across the desk.

One theme file drives the desktop and included apps. Lumi Earth Dark is the starting point; light and dark themes and your choice of wallpaper make it yours.

A deliberate starting set.

The planned Core keeps the app list small. Everything beyond it is your choice to install—or leave out.

Core applications

Ghostty
The terminal, where most Lumi work happens.
Zed
The editor for daily development.
Zen Browser
The web browser.
Thunar
The file manager for when you want one.
btop
A live view of what the machine is doing.
Cockpit
System controls in your browser.
git
Version control from the start.
fastfetch
A quick summary of your system.
starship
A readable terminal prompt.

Flake, beside your work.

Flake is Lumi’s local assistant, designed into the Core at no charge. Its sidepanel answers questions about Lumi’s tools, defaults and commands, as well as everyday tasks. No account or subscription is required.

Voice input is optional and stays off until you turn it on.

Sula, if you want the whole stack.

Sula is a planned optional subscription bundling Pi, Herdr workspaces and the surrounding AI coding tools into one configured environment. It is a way to fund Lumi—not a requirement for using the Core. You can assemble your own tools instead.

Sula is not shipping yet. Pricing, terms and availability are not decided.

Your machine should stay yours.

Core first.

Installable, updatable and recoverable without optional modules. If the Core needs a module to work, that is a bug.

Changes made explicit.

Modules declare what they need, what they change and where they conflict before they touch the system.

People and agents, one contract.

Discoverable commands, structured output and repeatable operations—with checks that people and agents can both run.

Defaults, not a lock-in.

Lumi makes choices so you can start working. You keep the choice to replace them.

Built on open work.

openSUSE TumbleweedRolling base

Tested snapshots beneath Lumi’s desktop and Core.

HyprlandCompositor

The Wayland compositor running the desktop.

QuickshellShell toolkit

The toolkit behind Lumi’s visible desktop surface.

end-4Starting point

The dotfiles that began the desktop work. Lumi now uses its own panels and themes.

For people who like the terminal.

You like the keyboard more than the mouse. You want strong defaults, not a setup project. You want agents that can run commands and check results—not guess from the sidelines.

If you want a system that hides the terminal or makes every desktop choice for you, Lumi is not for you. That is fine.

These are independent projects. Lumi is not affiliated with, endorsed by or maintained by them, and does not claim their work as its own. Omarchy 4’s approach to installation and theming is also an inspiration.

Still being built.
In the open.

There is no release to download yet. The Core comes first: coherent, installable and recoverable before it ships.

Hardware

Lumi targets standard x86_64 machines with UEFI. Partitioning, dual boot and your choice of GPU remain your responsibility; no universal hardware compatibility is promised.

Privacy

The default is no telemetry. Your data stays on your machine.

Follow the decisions, dead ends and progress.

Read the build log