Mango Wayland Compositor 0.18.1 ships a stability patch on the feature-heavy 0.18.0
The wlroots-based "dwm but for Wayland" build adds right-click-close in monocle mode and a smarter client-kill while trimming GPU cost from its blur path.
Mango, the Wayland compositor that bills itself as "dwm but for Wayland," just pushed version 0.18.1. It lands today, six days after the feature-heavy 0.18.0 release, and reads as the maintainer picking up the pieces. The intent is plain from the notes: stability first, practicality over novelty.
For the uninitiated, Mango takes dwl's lean C codebase and its "compiles in seconds" ethos and bolts on the features that make a compositor genuinely usable day to day. You get animations, tags instead of workspaces, an overview, scratchpads, and per-window controls without the bloat that tends to creep into the heavier compositors.
What's new in 0.18.1
The headline additions are small but useful. A new option lets you close a window by right-clicking its bar in monocle mode. Monocle mode is the single full-screen layout that otherwise wants you to stick to the keyboard, so this is the mouse-friendly exit people had been waiting for.
Keep in mind the option name still carries the maintainer's typo. It's filed as monocle_right_buttom_close, and "buttom" has yet to be corrected. No rush there.
There's also a new dispatcher called smartkillclient that attempts a cleaner shutdown of the focused window. It sits alongside the existing kill command, aiming to leave fewer orphaned processes behind. The notes describe the behavior only qualitatively, so you'll want to check the source if the exact mechanics matter to you.
The optimization list is where this patch actually earns its keep. The blur path now uses noticeably less GPU when blur optimization is turned off, which is a real win for lighter hardware running without sacrificing the visual polish. Config syntax got tidied too: the double quotes that wrapped values are gone, so lines read key=value rather than key="value". A new guard rejects absurdly long values outright instead of letting them misbehave silently.
Several other tweaks land in the monocle tab mode that 0.18.0 introduced. Directional focus now works within monocle tabbing, maximized windows can be switched the same way, and tiled windows remember their ratio when toggled to floating and back.
The patch closes with roughly a dozen bug fixes. The most relatable one is that Alt+Space no longer pauses Chrome. That's the classic cross-layer input leak where a shortcut meant for the compositor slips all the way down to the app, and it's exactly the sort of thing that gnaws at you before you can even say what's wrong.
Other fixes cover Electron rendering glitches in the overview (VS Code, Discord, the usual suspects), number keys binding properly through globalkeybinding, and a crash triggered when a layer closes without a commit. Monitor rules now honor width, height, and refresh rate under the custom option as well.
Where Mango fits
The release cadence here is a sign of a project moving quickly. Count nearly a minor or patch release per week through autumn 2026, from 0.16.2 in late August to 0.18.1 today. It's brisk, and it's been brisk for a while.
Mango now sits at roughly 3.8k GitHub stars and 265 forks, placing it among the more popular projects in the lightweight wlroots space. And the comparison is hard to avoid. Hyprland pulls in around 38k stars, ships in Rust, and offers deep customization at the cost of a large codebase and heavier resource use. Mango asks for far less and gives up less than you'd expect.
Is it just a feature-light Hyprland? Not quite. The real pitch is that it keeps dwl's weight class while handing you most of the day-to-day polish. The trajectory suggests the maintainer is deliberately maturing things: the 0.17.0 notes declared all planned features complete, then the codebase was reorganized into a cleaner C structure with help from a small core team. This is a project shifting from gathering features toward making them stick.
For what it's worth, there's even talk of another shell starting to migrate from Hyprland to a Mango-based build, which is a telling sign of cross-pollination, though it's still early days for that one.
If you want to try it, Mango is broadly available. Arch Linux ships it in the official repo (pacman -S mangowm) and the AUR, Fedora reaches it through the Terra repo, and NixOS provides a first-party flake with both a NixOS and Home Manager module. Debian has an Intent To Package report filed, while Gentoo, Guix, and a couple of rolling distros round things out.
One caveat on installability: the stable AUR package was still sitting at 0.17.2 as this story went to press, so grabbing 0.18.1 today means building from source or taking the -git build. That's a recurring complaint for fast-moving AUR packages, and it's something Mango itself can't fully control.
Head here to the release notes for the full changelog, and hit the wiki for layout and IPC details. If you do build from source, remember you'll need to compile wlroots 0.20.2 and scenefx 0.5 first.
