Mango Wayland Compositor Lands 0.16.1 With Per-Device Rules and Tidy Tag Management
The dwl-based compositor adds breaking config changes alongside practical workflow improvements.
Mango Wayland Compositor just dropped version 0.16.1, and if you're running it from source, you'll want to update your config before you restart. The release, tagged by maintainer DreamMaoMao on August 16, 2026, splits mouse and trackpad settings into separate namespaces while quietly packing in some features that make daily driving feel a lot less like wrestling a window manager.
Mango has been steadily carving out space in the Wayland scene since it forked dwl and layered wlroots on top. It keeps the original dwm philosophy of lean, focused code, but the project has grown enough to warrant its own mmsg IPC tool, a dedicated animation framework, and a community that already numbers in the thousands. The repository currently sits around 3,500 stars, with over 1,900 commits and a healthy mix of open issues and pull requests. It's not tiny anymore, but it's still refusing to become bloated.
Breaking Changes and the New Config Layout
The most immediate change for existing users is the forced separation of mouse and trackpad configuration. You now have to prefix affected options with mouse_ or trackpad_. Config hygiene, enforced. You'll trip over it the first time you restart, but it keeps the pointer options from colliding as the compositor adds more hardware profiles. The changelog warns about it up front, which is fair. You'll also want to double-check your keyboard mappings, since a previous layout quirk was masking crashes on certain setups.
What Actually Ships in 0.16.1
The headline addition is devicerule, which lets you assign independent settings to individual input devices. If you swap keyboards or pair a trackpad alongside a mouse, you can finally give each one its own layout, keybindings, or pointer behavior without juggling global overrides. There's also a new mmsg get layouts IPC call for scripting, touch input that now maps to specific monitors, and a tag_gather toggle that silently drops empty tags from your bar. The tag clean-up alone saves a few mental cycles per work session.
Bug fixes round out the release. The client kill crash that was showing up in edge cases is patched, and the screenshot tool finally respects screen rotation instead of stretching the output into a puddle. Frame skipping also behaves correctly now, which matters more than it sounds if you're pushing high refresh rates.
Ecosystem and Where to Get It
You can grab Mango straight from its GitHub repo using Meson, or pick it up through Arch (yay -S mangowm-git), Fedora, Gentoo, Guix, NixOS, openSUSE, and a few rolling distros that prefer bleeding edge. The project ships with a wiki, a dedicated docs site, and an active Discord channel if you need help untangling the new config structure. Sponsorship runs through crypto donations, which is a small detail but worth knowing if you want to support the maintainer directly.
It's a solid step toward making a dwm-style compositor feel at home on Wayland. The devicerule feature closes a gap that kept Mango out of some multi-device setups, though the forced config split means you'll spend the first ten minutes of this update relearning your hotkeys. Keep in mind that breaking changes in 0.x releases are usually reserved for structural shifts like this, so the underlying architecture is clearly stabilizing.
Head here to the Mango GitHub repository for the full changelog, or check the official wiki for migration notes on the new mouse and trackpad prefixes. The next tag will likely land in early September, assuming the current pull requests merge on schedule.
