Omarchy & NixOS: custom linux

NixOS is a fully declarative operating system built on a functional package manager, whereas Omarchy is an opinionated desktop environment originally built on Arch Linux that relies on traditional system conventions.

As icyphox noted on X, while personal preferences vary regarding project ecosystems and politics, comparing the two core models reveals distinct differences in configuration, architecture, and learning curves. [1]

Core Philosophies

NixOS: Uses the purely functional Nix language to define system state, packages, and services, offering atomic upgrades and rollbacks.
Omarchy: Focuses on providing a slick, "batteries-included" developer workflow—typically featuring Hyprland, custom themes, and shell configurations—without forcing users to adopt a completely new configuration paradigm from scratch. [1, 2]

Configuration and Management

NixOS: Requires configuring system parameters, dotfiles, and user environments via Nix expressions or tools like Home Manager, demanding a steep upfront learning curve. [1, 2]
Omarchy: Operates much closer to traditional Linux setups or leverages standard shell scripting and dotfile management, though community projects like omarchy-nix have explored bringing Omarchy elements into the Nix ecosystem. [1, 2]

Ecosystem and Community

NixOS: Backed by a vast, reproducible module ecosystem, though users must navigate its unique functional paradigm and occasional discussions around corporate/sponsor associations. [1, 2]
Omarchy: Offers an immediate, stylish on-ramp for developers who prioritize aesthetics and sensible defaults, though it carries its own debates concerning project origins and leadership. [1, 2]

For a broader look at how these foundational paradigms compare in practice, watch this breakdown:

NixOS vs Arch Linux (2026) - YouTube

Omarchy is the future - even if you don't use it - YouTube

In the video "Omarchy is the future - even if you don't use it," developer and instructor Maximilian Schwarzmüller breaks down why the Omarchy Linux distribution—created by 37signals co-founder David Heinemeier Hansson (DHH)—is a significant shift in the operating system landscape, regardless of whether viewers personally switch to it.

Core Takeaways

• What Omarchy Is: It is a heavily opinionated, developer-focused Linux distribution built on Arch Linux and the Hyprland tiling window manager. It prioritizes a keyboard-centric workflow, clean UI, and deep, native integration with AI coding agents.
  
  
• Agentic Workflows as First-Class Citizens: Schwarzmüller highlights that Omarchy embeds AI coding agents directly into the OS shell—allowing the operating system to automatically route terminal crashes and setup errors directly to AI agents for quick troubleshooting.
  
  
• Pushback Against Big Tech Bloat: The video frames Omarchy as an important counter-movement to corporate OS ecosystems (like Windows and macOS), which are increasingly moving toward subscription models, mandatory data collection, and intrusive background telemetry.
  
  
• Efficiency & Reproducibility: By pairing lightweight tiling components with reproducible installation scripts, the system offers high performance on both low-end hardware and modern machines, showing a practical model for how modern Linux can challenge proprietary platforms.
  
  

The Creator's Argument

Schwarzmüller argues that Omarchy's main value is setting a precedent. Even if users prefer traditional desktop environments like GNOME or macOS, Omarchy proves how cohesive, AI-assisted, keyboard-driven Linux environments can redefine user control and productivity for modern software development.

NixOS - Wikipedia

NixOS is a Linux distribution built around the Nix package manager. Unlike traditional Linux distributions, NixOS is configured using Nix's functional programming language or one of Nix's forks. The operating system builds itself according to declarations written by the user within its config files, allowing them to manage and alter all aspects of their system, as well as install identical builds of that system on any other machine. From those files, NixOS generates complete system profiles, enabling reproducible deployments, atomic upgrades, and system rollbacks.^[6] Representing the primary implementation of the Nix package manager,^[7] NixOS is often just referred to eponymously as Nix.

nixarchy: Omarchy on NixOS, and computing that's fun again · Olaf Krasicki-Freund

The blog post, titled nixarchy: Omarchy on NixOS, and computing that's fun again, by Olaf Krasicki-Freund explores nixarchy—a port that brings the Arch Linux-focused Omarchy desktop experience to NixOS.

Key Highlights:

• Vendoring over Reimplementation: Instead of rewriting Omarchy as a native Nix module (which risks falling out of sync with upstream updates), nixarchy packages the upstream tree as a derivation, replacing only the components that rely on Arch Linux/pacman.
  
  
• Declarative Package Management: Since NixOS manages packages declaratively, the package installation menu queues selected applications into ~/.config/nixarchy/apps.nix and runs nixarchy-apply to rebuild the system.
  
  
• Tailored AI Skills: While upstream Omarchy provides Arch-specific agent tooling, nixarchy introduces 10 dedicated AI skills customized for NixOS module structures, GPU setups, security, and diagnostics.
  
  
• Stale Session Handling: It addresses edge cases where system rebuilds occur mid-session, providing checks to detect stale session paths (OMARCHY_PATH) and prompting proper re-logins.
  
  
• Integrated Ask Menu: Menu options (e.g., What's wrong?, Make it faster, Disk is full) route directly to underlying agent skills using omarchy-agent-prompt.
  
  
• Local AI Integration: Supports local execution via Ollama (programs.nixarchy.localAi.enable = true), automatically configured based on detected hardware (NVIDIA/AMD), though requiring a GPU for viable agent response times.