# HyprFlux: an Arch Linux desktop built as a whole operating system

> HyprFlux is not a collection of dotfiles but a complete Arch Linux desktop project, spanning a branded archiso live image, a text mode installer with automatic and manual partitioning, a boot pipeline from GRUB through Plymouth to SDDM, and a maintained Hyprland session with Waybar, Rofi, Kitty, Neovim, Zsh and Tmux. It targets x86_64 machines with 4 GB of memory and a network connection.

**ahmad9059/HyprFlux** — HyprFlux : Minimal, productive, elegant, and fast

- Repository: https://github.com/ahmad9059/HyprFlux
- Website: https://hyprflux.dev
- Stars: 913 · Forks: 63
- Language: CSS
- License: MIT
- Published: 2026-10-20 · Updated: 2026-10-20 · Language: en
- Canonical page: https://hysenlabs.com/projects/ahmad9059-hyprflux

## An operating system project, not a dotfiles repository

HyprFlux is described as a complete Arch Linux desktop operating system project built around Hyprland, and the scope section lists what that covers: a branded live ISO built on archiso, a custom TUI installer with automatic and manual partitioning flows, a reproducible install flow, a branded boot pipeline from GRUB to Plymouth to SDDM, a maintained Hyprland desktop environment, curated applications and developer tools, and opinionated defaults with room for customization.

That list is the difference between a dotfiles repository and this. A dotfiles repository hands you files to copy into a home directory and leaves you to assemble the rest. HyprFlux starts from a fresh Arch installation and aims to end at a polished, consistent, production-ready Hyprland system without you piecing anything together manually.

The stated result is an operating system level experience with a single identity, carrying through from power-on to login to daily use. That is the design claim to hold the project to: not a set of parts, but one continuous surface.

The project is MIT licensed, its primary language is listed as CSS, which fits a repository whose centre of gravity is theming, and the homepage is hyprflux.dev. The releases are v1.5.0 from 2026-09-09 and 1.0.0 from 2026-03-17, and the last push was on 2026-10-13.

## Two layers, an ISO and a desktop

The overview splits the project into two layers, and the split explains the repository structure.

The live ISO layer is a custom archiso-based image with HyprFlux branding, boot assets and a text mode installation flow. The desktop environment layer is the session itself: Hyprland, Waybar, Rofi, Kitty, Zsh, Tmux, Neovim, scripts, keybinds and workflow customisation.

The ISO is built on archiso and boots directly into a branded text based installer that prepares a full HyprFlux system from a fresh machine. Its listed capabilities are an x86_64 Arch Linux live image built with archiso, support for both UEFI and legacy BIOS boot, a centered HyprFlux TUI installer launched automatically on tty1, automatic and manual partitioning modes, an online installation flow with target system provisioning, and QEMU test tooling with CI-based ISO builds.

The UEFI and legacy BIOS support is the detail that decides who can install it. A lot of modern images drop BIOS support, and the machines that end up on an installer USB are often old desktops that only boot in legacy mode. Keeping both costs the project effort and keeps the audience wider.

The TUI installer launching on tty1 is also deliberate. A graphical installer on a live image has to cope with whatever graphics driver the machine has, and a text installer on the first virtual console has no such problem.

## Verify the ISO before you write it to a USB stick

The production ISO and its SHA256 checksum are published on the HyprFlux releases page, and the README tells you to verify the download before writing it to USB.

```bash
sha256sum -c hyprflux-*.iso.sha256
```

That is the whole check, and it is the one step people skip. An ISO is an operating system installer, and it is the artefact with the most authority on the machine and the most likely to be fetched from a mirror or a link shared in a chat.

The repository split is worth understanding before you dig in. The ISO work currently lives under references/Hyprflux-ISO as a companion project reference, while the main HyprFlux repository continues to own the desktop stack, the assets, the modules and the platform layer. So a reader looking for the ISO build scripts in the root of the repository will not find them, and the ISO is still described as a dedicated project within the wider platform direction.

That arrangement is temporary by its own description, and it is the kind of thing that changes without a version bump, so it is worth checking the current layout rather than assuming where things live.

## The desktop layer, curated rather than minimal

The desktop features section is where the project states its choices rather than its principles.

Hyprland comes with maintained configs and workflow-oriented defaults. Waybar is included with curated layouts and custom modules. Rofi handles launching, switching, searching and custom menus. SDDM carries a HyprFlux-branded login theme. Neovim has a separate maintained config of its own, and Tmux and Zsh are preconfigured for daily work. The configuration lives in the repository as dotfiles of its own, with .tmux.conf, a .tmuxifier directory and a .zshrc at the root, plus a .config directory and a .themes directory.

Two feature lines are more unusual. AI tooling support comes through AUR packages for Claude Code, OpenAI Codex, Gemini CLI and OpenCode, which puts the assistant tooling in the base system rather than leaving it to the user. And web apps and utilities are pre-integrated for modern workflows.

The design direction is stated in three lines: a HyprFlux identity of custom logos, boot branding and consistent naming, a deep modern aesthetic built on a purple-led accent system and a dark user interface, and practical customisation where wallpapers, layouts, profiles, themes and scripts are easy to swap.

The last point is the one to test before adopting. A project that has opinions is only useful if the opinions are separated from the parts you want. Wallpapers, layouts, profiles, themes and scripts being swappable is the mechanism that makes an opinionated system usable by someone whose taste differs.

## Hardware-aware provisioning and the branded boot pipeline

The platform features list contains the parts that separate an operating system project from a wallpaper.

The custom boot experience is a branded integration of GRUB, Plymouth and SDDM, which is the full chain from firmware to login screen. It is the layer most users see and, in a project whose stated goal is a single identity from power-on to login, the layer that has to be consistent.

System theming covers GTK, icons, cursors and wallpapers, so the applications inherit the look rather than being a separate application with its own theme.

Then there is hardware-aware setup, which is listed as monitor configuration, cursor setup, theme wiring and post-install scripts. That is the part with real technical content. A compositor needs to know about the displays it is driving, a cursor theme has to be set for every toolkit that draws one, themes have to be wired into the settings of each application rather than assumed, and the post-install scripts are where the remaining per-machine decisions are applied once, at the point where the machine's specifics are known.

The same split appears in the desktop layer: the automated install flow is described as modular setup with sane defaults and minimal manual work, which is only achievable if the modules can detect what they need on the machine they are running on.

## Requirements, entry points and the shape of the repository

The requirements are modest and clearly stated: Arch Linux as the base, x86_64 architecture, 4 GB of memory as a minimum with 8 GB or more recommended, 10 GB of minimum free storage, and an active internet connection for package installation. The recommended starting point is a fresh Arch Linux installation with a working connection, a user account with sudo privileges, and the basic tools curl, git and sudo.

There are two platform entry points. The direct install script is for users starting from an existing Arch Linux install, and the ISO workflow is the full live-image-based installation path. The one-line installer is this.

```bash
sh <(curl -fsSL https://hyprflux.dev/install)
```

That one-liner pipes a remote script into a shell, which is the standard convenience for installers and also the standard thing to think about for a moment before running it. The README lists what the installer does, beginning with installing required packages and desktop components, and the fuller set of steps is in the documentation at hyprflux.dev.

The repository layout explains how the project is assembled. There are base-dots and base-installer directories, config, modules, scripts, utilities and lib directories, a docs directory, and the review directory holding the screenshots. At the root sit install.sh and dotsSetup.sh as the entry points,.config,.themes,.tmux.conf,.tmuxifier and.zshrc for the desktop layer, and the usual project files including CHANGELOG.md, CONTRIBUTING.md, CODE_OF_CONDUCT.md and SECURITY.md.

## Conclusion

Adopt HyprFlux when you want a complete, coherent Hyprland desktop rather than an assembled one, and when you are comfortable on Arch Linux and willing to let the installer provision a machine end to end. Do not adopt it if you want to keep your current system and copy a few files, because this is an operating system level project, and treat the live ISO as the route with the most moving parts. Before you start, confirm the machine meets the stated requirements of x86_64, 4 GB of memory and 10 GB of free space, verify the ISO download against its SHA256 checksum before writing it to USB, and read the documentation on hyprflux.dev, since the project distinguishes between the direct install script and the ISO workflow.

## FAQ

### What is HyprFlux and what does it include?

HyprFlux is a complete Arch Linux desktop operating system project built around Hyprland. It spans a branded live ISO built on archiso, a text mode installer with automatic and manual partitioning, automated provisioning, a branded boot pipeline from GRUB to Plymouth to SDDM, and a maintained desktop with Hyprland, Waybar, Rofi, Kitty, Zsh, Tmux and Neovim.

### How do I install HyprFlux on an existing Arch Linux machine?

The one-line installer is sh <(curl -fsSL https://hyprflux.dev/install), which installs the required packages and desktop components. The README also documents a recommended starting point of a fresh Arch installation, an internet connection, a user account with sudo privileges, and curl, git and sudo available.

### How do I verify the HyprFlux ISO download?

Download the ISO and its SHA256 checksum from the HyprFlux releases page and run sha256sum -c hyprflux-*.iso.sha256 before writing it to USB. The README asks you to verify the download before writing it to a USB stick.

### What are the system requirements for HyprFlux?

Arch Linux as the base, x86_64 architecture, 4 GB of memory minimum with 8 GB or more recommended, 10 GB of minimum free storage, and an active internet connection for package installation.

### Does the HyprFlux live ISO support legacy BIOS systems?

Yes. The ISO capabilities list both UEFI and legacy BIOS boot support, alongside the x86_64 image built with archiso and a centered TUI installer that launches automatically on tty1.

## Sources

- [ahmad9059/HyprFlux on GitHub](https://github.com/ahmad9059/HyprFlux)
- [License: MIT](https://github.com/ahmad9059/HyprFlux/blob/main/LICENSE)
- [Project website](https://hyprflux.dev)
- [README](https://github.com/ahmad9059/HyprFlux/blob/main/README.md)
- [Releases](https://github.com/ahmad9059/HyprFlux/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/ahmad9059-hyprflux