end-4/dots-hyprland: A Quickshell Desktop for Hyprland, and What It Asks of You

The problem: a window manager is not a desktop

Hyprland gives you a compositor. It does not give you a status bar, a launcher, a notification daemon, a wallpaper-driven color scheme, or a settings app. Most Hyprland users end up assembling those pieces from a dozen projects and then maintaining the glue themselves. end-4/dots-hyprland is one answer to that assembly problem: a curated set of configuration files plus a custom graphical shell, distributed together so the pieces are known to work with each other.

The README is unusually direct about what the project is and is not. It says the files are technically configuration files, but realistically are mostly the custom graphical shell. It also states plainly that this is not a system setup script: no graphics drivers, no zram setup. That boundary matters. If you expect the installer to prepare a bare machine, you will be disappointed. If you already have a working Arch-like system with a GPU driver and you want a finished desktop on top, the scope is right.

The audience is therefore narrow and specific. You need to be comfortable on Wayland, willing to run a shell script that modifies your home directory, and interested in a Material Design look rather than a minimal tiling setup. The project's own topics list includes ricing and unixporn, which tells you the aesthetic is part of the pitch, not an afterthought.

How the shell is built: Quickshell, QML, and a wallpaper-driven palette

The architecture has two layers. Hyprland is the compositor and handles window management. Quickshell, described in the README as a QtQuick-based widget system, renders the status bar, sidebars, and the rest of the desktop chrome. The primary language of the repository is QML, which is consistent with that split: the shell logic lives in QML, and the Hyprland configuration lives alongside it.

Color generation is one of the more visible mechanisms. The README credits @midn8hustlr with greatly improving the color generation system, and the feature list says Material themes work by choosing a wallpaper and being done. In practice that means the palette is derived from the wallpaper rather than hand-edited per theme. That is a meaningful design choice. It lowers the effort to restyle the desktop, but it also means the look is coupled to the wallpaper you pick, and a low-contrast image can produce a low-contrast interface.

Several features sit on top of the shell rather than inside Hyprland. The overview shows open apps with live previews. There is screen translation, an anti-flashbang feature, and Google Lens integration. AI support covers Gemini and Ollama. None of these are compositor features; they are shell widgets that call out to other services. The practical consequence is that the interesting parts of this project are the parts most likely to break when an upstream API or a dependency changes, and they are also the parts least covered by the compositor's own documentation.

Installing end-4/dots-hyprland and running it the first time

The README gives two installation paths. The quick one pipes a remote script into bash. The other clones the repository and runs the setup entry point, which is the top-level `setup` file visible in the repository listing. The README states that every command is shown before it is run, which is the project's transparency claim. You should still read the script before executing the curl form; that is a general habit, not a criticism of this project.

bash <(curl -s https://ii.clsty.link/get)

This downloads and executes the installer. Because it is fetched over the network at run time, the version you get is whatever is current, not a pinned release. If you want a reproducible install, use the clone path instead.

git clone https://github.com/end-4/dots-hyprland
cd dots-hyprland
./setup install

After installation, the README points to two keybinds worth learning immediately. `Super`+`/` opens the keybind list, and `Super`+`Enter` opens a terminal. The README notes the keybinds should feel somewhat familiar to Windows or GNOME users, which is a deliberate usability choice rather than an inherited tiling-WM default set.

The warning at the top of the README is the part to read before anything else. It concerns the Hyprland 0.55 update. If your distro has not shipped Hyprland 0.55, or you are not ready for it, the README tells you to switch to the Pre-Hyprland Luaification release, or simply not update yet. The most recent release listed is 2026.05.11, labelled Pre-Hyprland Luaification, which is the fallback the README is pointing at. The wiki is cited for both installation and updating details; the README itself does not document a rollback procedure.

Where this breaks: version coupling and the missing system layer

The clearest limitation is the Hyprland version dependency. A desktop shell that renders bars and sidebars is tightly coupled to the compositor it targets, and the README's own warning shows the project reacting to a compositor change by asking users to hold back or move to an older release. That is a real operational cost. You cannot simply take every update on both sides and assume they agree.

The second limitation is scope. The README explicitly excludes graphics drivers and zram setup. On a fresh minimal install, running the installer will not produce a usable graphical session by itself. That is a deliberate boundary, but it means the project is a poor fit for anyone who wants a single command that turns a blank disk into a working desktop.

The third is the surface area of the optional features. AI integration, screen translation, and Google Lens all depend on external services or local models. The README lists Gemini and Ollama as supported, but it does not describe what happens when those are unavailable, misconfigured, or rate-limited. A shell that assumes network services will degrade in ways the documentation does not spell out. If you want a desktop with no external dependencies, the AI widgets are dead weight you will need to remove.

Finally, the previous styles are marked unsupported. The README lists illogical-impulse AGS, m3ww, NovelKnock, Hybrid, and Windoes, each labelled Support: No, with sources in the `ii-ags` and `archive` branches. Anyone arriving from an older screenshot or an older tutorial is looking at an abandoned configuration.

Alternatives: hand-rolled configs and other shell stacks

The obvious alternative is assembling your own Hyprland configuration and picking a separate bar or shell. The difference is not quality, it is who owns the integration. With a hand-rolled setup you choose each component and you control when it updates. You also own every breakage. end-4/dots-hyprland makes the opposite trade: you accept the maintainer's choices about components and update cadence, and in exchange the pieces are tested together and the installer handles the wiring.

A second alternative is a different shell stack entirely. The README's own history is instructive here. Earlier versions of this project used AGS and EWW as the widget system before moving to Quickshell. Those older configurations are still reachable in the `ii-ags` and `archive` branches, but they are explicitly unsupported. Choosing them now means choosing a frozen snapshot with no upstream fixes.

A third path is to keep Hyprland and add only the parts you want. The repository layout separates `dots/` and `dots-extra/`, and there is a `diagnose` entry alongside `setup`. That structure suggests the configuration is not monolithic, but the README does not document installing a subset, so partial adoption is something you would have to work out from the files rather than from the documentation.

Maintenance, licensing, and what an upgrade actually costs

The repository is not archived, and the last push was on 2026-09-14. That is recent, so the project is being worked on. The single release listed, 2026.05.11, is four months older than that last push, which suggests development happens on the main branch rather than through tagged releases. If you want a stable target, there is no rich release history to pin to.

Upgrade cost is dominated by the Hyprland coupling described above. The README's own guidance is to consult the wiki for updating, and to fall back to the Pre-Hyprland Luaification release when the compositor version is not ready. That is a manual decision each time, not an automatic one. Budget for reading release notes on both sides before updating.

The licence is GPL-3.0, and the repository contains a `LICENSE` file and a `licenses/` directory. GPL-3.0 is a copyleft licence. If you fork these dotfiles and distribute your version, the licence terms apply to what you distribute. Configuration files that you keep to yourself are a different situation from a redistributed fork. This is not legal advice; read the licence text and the `licenses/` directory if you plan to redistribute.

Support runs through a Discord server linked in the README, with a note asking users to prefer GitHub for real issues. That preference is worth respecting: a bug report with a reproduction is more useful than a chat message, and the README says so.

Editorial conclusion

Adopt end-4/dots-hyprland if you run Arch or another distro that already ships Hyprland 0.55 and you want a complete Quickshell desktop rather than a bare window manager config. Skip it if you are on a distro without 0.55, or if you want a system setup script, because the README states this is not one. Verify three things first: your Hyprland version, whether your distro packages the dependencies listed in sdata/deps-info.md, and whether you can live with the Pre-Hyprland Luaification release until your distro catches up.

Frequently asked questions

Official sources

1. end-4/dots-hyprland on GitHub
2. License: GPL-3.0
3. Project website
4. README
5. Releases