Report a bug
A short form on GitHub: what happened, how to reproduce it, and your system details.
Open a bug reportNot a fork, not a reimplementation: NixOS itself, with the standard Linux filesystem layout laid back on top. Nothing is patched and nothing is overlaid, so every package stays exactly as its maintainers shipped it.
That one missing layer is what everything else follows from. Your existing Linux software runs unmodified. Any desktop you want runs on it. And the whole system is one text file you can read, change, and roll back.
Every Omnix desktop shares the same NixOS base. Choose Hyprland - Omarchy for keyboard-driven tiling, or KDE Plasma - Atrium for a familiar taskbar desktop.
Don’t like the look? Pick another theme and switch immediately. Hyprland - Omarchy includes Omarchy’s built-in themes, from Tokyo Night and Catppuccin to Gruvbox, Nord and Rosé Pine. Press Super + Ctrl + Shift + Space, choose one, and the bar, window borders, terminal and editor change color on the spot, with no rebuild and no logout. Try it in the preview.
Want a different desktop altogether? Change one line in your configuration and rebuild. Your previous desktop stays in the boot menu, so trying something new is never a one-way trip.
Hyprland tiles every window automatically. Open and close windows, switch workspaces and try Omarchy’s themes.
Hyprland - Omarchy · interactive illustration · colors from Omarchy’s themes
Omnix integration · under development
Omarchy’s plugin system lets you add bar widgets, open custom panels, run background services, or replace the whole bar. Community plugins are shared as Git repositories and managed from Omarchy’s plugin menu.
Hyprland - Omarchy already includes the plugin host. We’re working toward verified installation, updates and removal on Omnix, with support tracked in our public roadmap.
Run Qwen, Llama and Gemma on your own hardware, with no account, no API bill and no data leaving your machine. Omnix turns the usual afternoon of drivers, CUDA versions and install guides into a few lines of configuration and a single rebuild.
The tools you already know, set up correctly. Ollama, LM Studio and llama.cpp each come with the GPU runtime that matches your card, built and tested to work together. Switching between them is a one-line change.
Built to keep pace with AI. New models and runtimes arrive every month. Your
setup stays exactly as it is until you choose to update, then moves forward as a whole with
nix flake update. If an update misbehaves, the previous version is one reboot away.
Compatible with the wider ecosystem. Because Omnix provides the standard Linux layout, CUDA wheels from PyPI, conda environments and vendor AI SDKs run without workarounds.
Ollama serves models over a local API, and Open WebUI gives you a polished, ChatGPT-style chat in the browser.
Illustration. Configurations use modules and packages that ship with NixOS and nixpkgs; models need matching GPU memory.
Each Omnix system update becomes a new entry in the boot menu. If one breaks something, pick the previous entry: system apps, libraries and settings come back as they were. Your files and personal settings stay untouched.
Your system is a Nix flake that you own in /etc/nixos, and your desktop is one
input in it. The Linux compatibility layer is versioned with it, so a rollback restores the library layout too.
Omnix ▸ Generation 14 Hyprland - Omarchy (stable) 2026-10-03 Generation 13 KDE Plasma - Atrium 2026-09-28 Generation 12 KDE Plasma - Atrium 2026-09-21 Generation 11 Minimal 2026-09-20 $ sudo nixos-rebuild switch --rollback switched to generation 13 (KDE Plasma - Atrium)
Python wheels, rustup, AppImages, Electron apps and vendor SDKs expect standard Linux folders such as
/bin/bash, /usr/lib and /lib64. Omnix adds them to NixOS.
Add, never relocate. Packages stay unmodified in /nix/store and download
from the same cache.nixos.org as NixOS. Omnix uses no overlays, and patches only what it has to fix
itself, sending each fix upstream: today, one envfs patch that lets relocatable interpreters run through
#!/usr/bin/python3.
nixpkgs // unmodified packages |-- cache.nixos.org // download when available '-- local builds // compile when needed | v /nix/store // packages stay here | v Omnix FHS layer // familiar Linux paths |-- /bin/bash // shell for scripts |-- /usr/lib // shared libraries '-- /lib64 // compatibility loader
Your whole system is one file you own in /etc/nixos: the packages, the desktop, the
keyboard shortcuts, the wallpaper. Change it in a text editor, commit it, and the history is the record of
what you changed and when.
Share it as an Omnix flake. Point a friend, a teammate or an AI assistant at the repo and they get the same machine. Nothing is hidden in a GUI, and nothing is lost when the disk dies.
$ git init && git remote add origin [email protected]:you/omnix-config.git $ cat flake.nix { // the whole machine, as text inputs.nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable"; inputs.omnix.url = "github:Omnix-Linux/Omnix"; outputs = { nixpkgs, omnix, ... }: { nixosConfigurations."laptop" = nixpkgs.lib.nixosSystem { modules = [ omnix.nixosModules.default ./hardware.nix // disks, GPU ./desktop.nix // Hyprland - Omarchy ]; }; }; } $ git push ✓ same machine, anywhere
On Omnix, cargo is aliased to soldr cargo. You type the commands you
already know; underneath, the build is cleaned up for you — the right toolchain fetched and pinned, each
compilation cached, and nothing rebuilt that does not have to be.
Warm builds come back in seconds. The cache is content-addressed, so a build reuses the exact compilation it already did — and shares it across branches and pull requests, which a per-branch CI cache cannot do. Cross-PR builds run about twice as fast.
Cross-compilation is a first-class citizen. The tools for it are built in, not bolted on, so cross-compiling is as easy as compiling: one command provisions the SDK and builds a macOS binary from Linux, or a Windows one, without renting a runner to produce it.
# cargo is aliased to soldr cargo $ cargo build --release // warm cache · no recompile $ cargo build --target mac-arm64 // macOS, built from Linux ✓ your-app (macOS arm64) $ cargo test // shares the cache across branches
The alias points at Soldr, the toolchain behind it — developed by the same person behind Omnix and used to build its own projects. It is beta software: pin the release you use.
Running prebuilt software already works out of the box: the base ships a loader, so ordinary Linux programs run unmodified. What comes next covers the two kinds that do not need a Linux binary at all.
Cosmopolitan-style single-file programs, treated as a first-class app beside Nix packages: download one file and it runs, whichever system you land on. No build step, no per-platform binaries to chase.
app.ape // one file, many OSes '-- first-class app // runs like any app
Small sandboxed WASM modules, aiming for near-native speed on top of a stable kernel API — programs with no Linux build at all, hosted on an interface that stays stable as the system underneath it changes.
micro.wasm // no Linux build needed '-- kernel-API // sandboxed, stable host
Planned, not shipped. Both of these are on the roadmap; the loader and the desktop work above are what Omnix does today.
app.ape // one file, many OSes '-- first-class app // runs like any app micro.wasm // no Linux build needed '-- kernel-API platform // sandboxed, stable host /* planned · not shipped */
Omnix is NixOS with the standard Linux filesystem layout. It adds that layout as a layer — no forked packages, no overlays — so Omarchy's Hyprland desktop, KDE Plasma - Atrium and prebuilt Linux software run unmodified, with declarative configuration and boot-menu rollbacks.
Yes. The Hyprland - Omarchy flavor of Omnix runs Omarchy's own Hyprland configuration, keybindings, themes and scripts on a NixOS base. Choose stable for a pinned Omarchy release (4.0.4) or latest to follow Omarchy's development branch.
Yes. KDE Plasma - Atrium is a declarative KDE Plasma 6 desktop that borrows Omarchy habits such as a Meta+W overview, per-screen virtual desktops, the JetBrainsMono Nerd Font and fast key repeat, while staying a familiar, mouse-first taskbar desktop.
Open an issue with the bug report form on GitHub. It covers the installer, the base system, both desktops and local AI, and asks for the system details we need. You can also browse known issues first.
Yes. In Hyprland - Omarchy, press Super + Ctrl + Shift + Space and pick one of Omarchy's built-in themes; the bar, window borders, terminal and editor change immediately, with no rebuild. To change the whole desktop, change one line in your configuration and rebuild, and the previous desktop stays in the boot menu.
No. Omnix is NixOS (nixos-unstable) with unmodified nixpkgs packages from cache.nixos.org. It adds the standard Linux filesystem layout as a layer built from nix-ld and envfs — symlinks and a library cache, with no overlays, no patched packages and nothing forked.
System apps, libraries, system settings and the Linux compatibility layer. Every update is a new boot-menu entry, so you can pick the previous one or run sudo nixos-rebuild switch --rollback. Files and personal settings in your home folder are not changed.
Most prebuilt software that expects /bin/bash, /usr/lib and /lib64/ld-linux-x86-64.so.2 runs unmodified, including manylinux Python wheels, rustup, AppImages, Electron apps and Playwright's Chromium.
omarchy-nix recreates Omarchy as a NixOS and home-manager configuration. Omnix runs Omarchy's own sources on a NixOS base with standard Linux paths, and also offers a KDE Plasma desktop. Both are independent community projects.
Omnix currently supports 64-bit Intel and AMD PCs (x86-64). The Try Omnix Docker app, which runs the real installer in a virtual machine, needs x86-64 Linux, Docker and KVM.
No. Omnix is an independent project and is not affiliated with or endorsed by Omarchy, 37signals, Basecamp or the NixOS Foundation.
Omnix is in preview, and every report makes it better. If the installer stalls, a program will not start, a desktop misbehaves or your GPU sits idle under a local model, open an issue. It takes about two minutes.
One place for everything. The form asks where the problem is, so reports about the installer, the base system, either desktop or local AI all reach the right people.
// paste the output into the form $ nixos-version $ uname -rm $ lspci -nn | grep -Ei 'vga|3d|display' $ nix flake metadata /etc/nixos // a service failed $ journalctl -b -u <service> | tail -n 100 // broke after an update? roll back first, // then tell us which generation worked $ sudo nixos-rebuild switch --rollback ✓ back to work while we fix it
Install it on a PC, or try it in a virtual machine first.
Omnix supports 64-bit Intel and AMD PCs (x86-64). Boot the installer ISO, or run the real installer in a virtual machine with the Try Omnix Docker app.
Welcome to the Omnix installer. Run: sudo omnix-install
[nixos@nixos:~]$ ▌
Simulated from the boot ISO: terminal menus, individual prompts, then console output. Timing and log lines are illustrative. This preview uses a wired connection, btrfs and LUKS; Wi-Fi setup opens nmtui. Each loop tries the other desktop.