Most people who self-host on Arch have stopped reading the package review screen. Not because they do not care, but because the screen is so painful that skimming becomes the only sane option. Shelly 3.1.4 lands as an attempt to fix exactly that pain. If the team succeeds, more people will actually read what they are about to install. If they fail, the review screen stays a checkbox.
Shelly is a graphical front end for the package sources Arch users already work with, pacman, the AUR, Flathub, Flatpak, and AppImage. The 3.1.4 release touches every one of those surfaces in small but meaningful ways. None of the changes are headline features. Most of them are patches to the spots where someone said “I will just run pacman from the terminal instead” and never came back.
What This Release Is Actually For
Picture a Tuesday morning. You are doing routine upgrades. You open Shelly, click into a PKGBUILD diff (a side-by-side comparison showing what changed in the recipe file that builds the package from source), and the diff is 400 lines. Without collapsing, you are either reading everything or trusting everything. Both options are bad. The 3.1.4 release lets you collapse the boring sections and expand only the parts that look suspicious. That is the whole pitch. Everything else is polish around that core idea.
Here is the part that will affect most daily users:
- Diff collapsing for large AUR PKGBUILDS, so skimming actually works
- Per-package review before continuing the upgrade batch
- A copy button on package details, useful for pasting into a chat thread
- Tray service changes started from the CLI now stick across restarts
- Optional dependencies handled more sensibly in the UI
- Long package names truncate cleanly in the column view
If you only touch the AUR once a month, none of this changes your life. If you do real work in there, the first big diff after upgrading will tell you whether the team pulled it off.
The Native Builder Got The Attention It Deserved
Building from source instead of pulling a binary is the mode that breaks in the worst ways. 3.1.4 takes that mode seriously. Detection of build dependencies is more reliable. Two source files with the same name no longer collide mid-build. Git source cloning now works from upstream URLs, which means the niche case of “this package wants a fork on a specific branch” no longer requires babysitting. There are also fixes for four runner setups I have not tested myself, Anydesk, Mandolin, Remora, and Pi. They tell me the team is listening to people with less common hardware.
The systemd (the init system, the first program that runs at boot) home directory bug for isolated builds is fixed. If you build inside a chroot (a sandboxed mini-filesystem that keeps the build separate from the rest of your machine), you have probably seen $HOME vanish and a build die for a reason that was actually a setup glitch. That whole class of failure should be gone.
The Review Screen Is Why I Use Shelly At All
The reason to run a graphical front end over pacman is to slow down before installing something unknown. Without that friction, you might as well paste install commands into a terminal. The 3.1.4 release makes the review screen better at its actual job.
A few quality of life patches from the changelog worth noting:
- Ignored packages stay visible inside filtered views, which removes one source of “is this filter broken?”
- Package status updates land reliably after installs and upgrades
- Command output wording is less ambiguous, less guessing about what a wall of text means
- PGP (Pretty Good Privacy, a way to cryptographically sign files so others can confirm they came from the right developer) key import confirmations got a polish pass
I have not verified every one of these, and the less obvious ones stay on my unverified list until I confirm them on a clean install.
Flatpak, Cache, And The Unsexy Plumbing
Flatpak flows have always felt like a different app inside Shelly. 3.1.4 aligns them with pacman behavior so installation and updates feel consistent. The --needed flag, which tells pacman to skip reinstalling packages you already have, is finally wired into the right place. If you script installs or run them from a saved list, that flag location matters. Cache cleanup also gets a one-click purge for old AUR build artifacts.
The full changelog lives on the GitHub project page. Binary and source tarball are available from the same place.
How To Get It
CachyOS users run sudo pacman -S shelly. Plain Arch users grab the binary or build from source. The README walks through both routes.
If you already run Shelly, update, open one AUR package you have been avoiding, and try the collapsed diff. That single workflow will show you whether the team pulled off the changes they promised. If you do not run Shelly yet, install it alongside pacman, use it for a week, and decide whether the GUI earns the dock space. The package is in CachyOS repos and the binary lives on GitHub for plain Arch users.
A few practical notes before you commit. First, the source tarball is small and builds quickly on most modern machines. Second, if you are running Shelly from the AUR already, you will need to rebuild for the new release. Third, take a backup of your Shelly config directory before upgrading, just in case the upgrade writes a new default that overwrites something you had customized. None of these are blockers, and the team has been good about not breaking config files between minor releases, but a backup takes ten seconds and saves a Saturday.
If you are new to package managers that try to be friendlier than pacman, here is the honest framing. Shelly is not magic. It is a UI over a CLI you already know. What it does well is slow you down at the moments when slowing down matters most. What it does not do well is explain pacman’s error messages when pacman itself fails. Treat Shelly as a complementary tool, not a replacement for understanding how your system installs software. With that frame, the 3.1.4 release is a meaningful step forward for the people who use it every day.
Trade-Offs
A graphical layer on top of pacman is a convenience, not a replacement. When pacman itself does something surprising, Shelly cannot always explain it. You still need to understand what pacman is doing. 3.1.4 fixes friction in the review workflow, not the philosophy.
A few things to weigh before adopting or upgrading:
- You add another dependency, and any convenience layer can fall behind upstream pacman on edge cases
- The native builder depends on your local toolchain, so a broken compiler on your box is still your problem
- Collapsed diffs are great for skimming, but skipping too aggressively will hide the one line that mattered
- Shelly is community-maintained, and updates ship when contributors have the time, not on a corporate schedule
None of these are dealbreakers. They are the costs of running a friendly cockpit on top of a system that already expects you to read the manual.
Coach’s note: do not skip the review step just because the diff looks long. The collapsed sections are designed for exactly that moment. Expand, read, then click upgrade.