Shelly 3.3 Refreshes Arch Linux Package Management

A package manager is not usually the kind of software that gets a visual redesign. It is the tool you open when something needs installing, and you want it to get out of the way. Shelly 3.3, released on November 14, 2026, decided to be different. This version of the Arch Linux package manager arrived with a new default look, a rebuilt updates page, and a set of smaller fixes aimed at the moments where package management tends to get awkward. The result is a release that cares about what the screen looks like while you wait for downloads to finish.
That may sound like a small thing, but anyone who has spent time babysitting a system upgrade knows that feedback matters. Shelly 3.3 tries to tell you what is happening, how much is left, and which parts of the update need your attention. It also makes peace with the way modern desktops switch between light and dark themes. This article covers what changed in Shelly 3.3, how the new interface is put together, what the update workflow now does, and how to install it. It also looks at where the tool fits in the broader Arch ecosystem, and which claims about the release are precise enough to rely on.
Why the Shelly 3.3 refresh matters
Shelly is a native package manager for Arch Linux that handles repository packages, the Arch User Repository, Flatpaks, and AppImages through one interface. The project is written primarily in Zig, with a GTK4 graphical front end, and it is licensed under GPL version 3. That combination is unusual. Most Arch users reach for pacman directly, then add a helper for the AUR, then use a separate command for Flatpaks. Shelly tries to fold those jobs into a single window.
The Shelly 3.3 release matters because it addresses the interface rather than the engine. Version 3.2 landed on November 5, and the 3.3 tag followed on November 14. In the space of those nine days the project shipped a fresh default appearance, a reorganized sidebar, a revised look and feel section, and a substantially reworked updates page. The official release notes describe Shelly 3.3 as bringing a fresh default look, and that phrase undersells the scope of what changed.
The reason a package manager would invest in appearance is practical. Upgrades are frequent on a rolling release distribution such as Arch, and a tool you use several times a week benefits from being legible. Shelly 3.3 is an argument that the wait during an update should be informative rather than blank, and that the interface should respect the desktop it is sitting on.
A new look borrowed from Pearl
The most visible change in Shelly 3.3 is the default theme. The official notes say the new look is inspired by Pearl, the desktop shell that the project's developer builds for the Devario and Aqueous desktops. That influence shows up in a handful of concrete decisions rather than in a vague aesthetic. Shelly 3.3 uses circular window controls, accent colored selections, card style toolbars, and larger page titles.
The sidebar has also grown. In Shelly 3.3 the settings and utilities are grouped together under a System heading, which gives the navigation a clearer hierarchy. Anyone who used earlier versions will notice the change immediately, because the previous arrangement spread those items out. Grouping them reduces the number of places you have to look when you want to change something.
It is worth being precise about the source of this look. The release notes credit Pearl directly and describe the result as closer to the rest of the Seafoam desktop. Some summaries have called it Devario's Pearl desktop environment, which is a reasonable shorthand but is not the wording the project uses. The safe description is that Shelly 3.3 follows the Pearl design language, and Pearl is the shell associated with Devario.
None of this changes how packages are resolved or installed. It changes what you see while Shelly works. For a tool that is opened constantly, that distinction is less trivial than it sounds.
Light, dark, and following the system
Alongside the visual refresh, Shelly 3.3 changed how the application decides between a light and a dark palette. By default, it now follows the desktop's own preference. If your system is set to dark mode, Shelly 3.3 opens dark. If it is set to light, the application opens light. That removes the small but persistent annoyance of an application that ignores the rest of the desktop.
For people who want a fixed choice, the settings still provide one. Under Settings, then Look and Feel, Shelly 3.3 offers three options: follow the system, light, or dark. That is a short list, but it covers the cases most users care about. It is also a better arrangement than forcing a manual switch every time the operating system changes its mind.
The project has not abandoned its older appearance. A system GTK theme remains available in Shelly 3.3 for anyone who prefers the styling of their desktop's GTK applications. That is a useful concession, because a package manager that inherits the system theme can disappear into the desktop in a way that a custom theme cannot. Keeping both paths means the redesign is a default rather than a mandate.
The broader point is that Shelly 3.3 treats theme handling as a first class feature. Many Linux utilities still treat dark mode as an afterthought, and users notice. The three way preference in Shelly 3.3 is a small piece of code that removes a daily irritation.
The updates page gets a rebuild
If the new theme is what you notice first in Shelly 3.3, the updates page is what you will use most. The release notes list a series of changes that add up to a different workflow. Source filters now show package counts for System, AUR, and Flatpak separately, so you can see at a glance how many updates are waiting from each source. That is more useful than a single undifferentiated list, because the three sources carry very different risks.
Shelly 3.3 also adds an included update summary and a total download size. Before you commit to an upgrade, you can see how much data it will consume and what is included. On a metered connection, or before a long download on a laptop, that information changes decisions. Individual selection for AUR and Flatpak updates is now supported as well, and the upgrade buttons reflect what you have chosen.
That last detail matters more than it appears. A button that updates itself to match your selection is a small safeguard against a common mistake, which is assuming you have picked a subset when you have actually selected everything. Shelly 3.3 makes the state of the upgrade visible in the control you are about to press.
The AUR deserves special attention here. Repository packages come from Arch maintainers and are generally safe to take in bulk. AUR packages are built from user submitted scripts and deserve a more careful look. By separating the sources and allowing individual selection, Shelly 3.3 gives the AUR the treatment it needs. This is the kind of design decision that separates a package manager that merely lists packages from one that understands where they come from.
Progress you can actually read
The upgrade experience in Shelly 3.3 gained a new overall progress card. It shows the download and installation stages, and includes transfer details when those are available. In practical terms, you can see whether the tool is downloading, building, or installing, and how far along it is. That is a significant improvement over a spinner, which tells you nothing except that the process has not finished.
Individual package rows in Shelly 3.3 are more informative too. They distinguish between packages that are pending, downloading, building, completed, and failed. On an AUR heavy upgrade, where building can take a long time, being able to tell which packages are still compiling is genuinely useful. A failed row is also easier to spot when it is labeled rather than implied.
Terminal output in Shelly 3.3 now starts collapsed and is one click away. This respects the fact that most users do not want to read hundreds of lines of build logs, while keeping them available when something goes wrong. It is a sensible default for a graphical tool that sits on top of command line operations.
Taken together, these changes make an upgrade feel observable. You can see what Shelly 3.3 is doing, how far it has got, and where it stopped. For anyone who has stared at an unresponsive package manager and wondered whether it was still working, that is the point.
Smaller fixes that show up in daily use
Not every change in Shelly 3.3 is visible. The release notes describe a fix for update checks that now recover from temporary contention with the system tray after an upgrade. This is the kind of bug that is hard to report precisely and easy to feel, because the application simply stops responding correctly until you restart it. Shelly 3.3 handles the recovery on its own.
Restart handling has been improved as well. Shelly 3.3 recognizes display manager aliases, including Plasma Login Manager, so that session critical services are reported instead of automatically restarted. That is a conservative choice, and a correct one. Automatically restarting a display manager in the middle of a user session can log people out and interrupt work. Reporting the need for a restart instead is safer.
These fixes will not appear in screenshots, but they are part of what makes Shelly 3.3 feel finished. A release that only changed the theme would be a cosmetic update. A release that also smooths the moments around an upgrade is a maintenance improvement. The two kinds of change together explain why 3.3 reads as a fuller release than a nine day gap would suggest.
What the AUR handling gets right
The decision to give AUR updates their own filter and their own selection controls is the most consequential part of the Shelly 3.3 redesign. The Arch User Repository is one of the distribution's great strengths, but it is not the same kind of source as the official repositories. A repository package is built and signed by Arch maintainers. An AUR package is assembled on your own machine from a script written by another user. Treating the two as identical entries in one long list hides an important difference.
Shelly 3.3 makes that difference visible in three ways. The source filter shows an AUR count separately from the system count, so you know how many user submitted packages are waiting. The update summary lets you pick AUR items one by one instead of accepting the whole batch. And the progress rows distinguish the building stage, which is where AUR packages spend most of their time. A user who wants repository updates now but wants to review an AUR change first can actually do that.
This is also where the collapsed terminal output earns its place. When an AUR build fails, the reason is usually buried in a build log. Shelly 3.3 keeps that log available with a single click, so a failure row is not a dead end. You can expand the output, read the error, and decide whether to retry or skip. None of this removes the need to judge AUR packages carefully, but it puts the relevant information within reach.
How to install Shelly 3.3
Installation depends on where your packages come from. The project's README lists several commands, and it is worth quoting them accurately. For CachyOS, or when using CachyOS packages, the recommended method is:
- sudo pacman -S shelly
That works because CachyOS carries Shelly in its repositories. On stock Arch Linux, the documented route is through an AUR helper. The README gives both yay -S shelly and paru -S shelly as options. If you are already running Shelly from an earlier version, your normal update path will pick up the 3.3 release.
A note on that distinction is important. Some write ups present the pacman command as the universal instruction. It is not. The project itself frames pacman as the CachyOS path, with the AUR helpers as the alternative. If you are on plain Arch and pacman cannot find the package, nothing is broken. You need an AUR helper, or a manual build from the project source.
The official documentation also includes a command line reference, although the graphical interface is the main draw of this release. Anyone who wants to script around the tool can consult the docs on the project's site. The release notes and the README together are the best record of what version 3.3 contains, much as the Rust debugging guide records the state of that toolchain.
Where Shelly fits among Arch tools
Arch Linux has never been short of package management tools. Pacman is the foundation, and a long list of helpers has grown around it to cover the AUR. Flatpak and AppImage add further layers, each with its own commands. The niche Shelly occupies is the unified graphical interface. It does not replace pacman underneath, and it does not ask you to abandon the command line. It gives you one place to look when you want to see everything that can be updated.
The Shelly 3.3 release strengthens that position without changing the underlying model. A tool that wants to be the single window for all your packages needs to make the queue understandable, and that is exactly where the updates page, the progress card, and the source filters are aimed. If you are happy with pacman and a helper in a terminal, Shelly 3.3 is unlikely to change your mind. If you prefer a graphical overview, the 3.3 release is the most complete version of that idea the project has shipped.
For readers who follow Linux security, it is also worth noting that package management is part of the security story. The recent discussion of kernel file sharing flaws showed how much attention the operating system layer attracts. A package manager that clearly separates repository packages from AUR builds contributes to the same goal by making provenance visible. On a distribution that moves quickly, knowing what you are installing is half the work.
The choice of Zig and GTK4 is part of the identity too. It gives Shelly 3.3 a native feel on Arch desktops and keeps the graphical layer close to the package handling code. That emphasis on local, native tooling echoes the approach behind running an emulator for AI agents locally. Whether that architecture wins over more established helpers is a question users will decide, but the 3.3 release makes the case more clearly than its predecessors did.
Questions readers are asking
When was Shelly 3.3 released? The 3.3 release is tagged as version 3.3.0 and dated November 14, 2026. It followed version 3.2.0, which was tagged on November 5. A 3.2.1 patch also exists, so the gap depends on which 3.2 release you compare against.
What is the new default look in Shelly 3.3 based on? The official release notes say the look is inspired by Pearl, the desktop shell from the same developer that is associated with Devario and Aqueous. It includes circular window controls, accent colored selections, card style toolbars, larger page titles, and a sidebar that groups settings and utilities under System.
Does Shelly 3.3 support dark mode? Yes. By default it follows the desktop's light or dark preference. You can also choose follow system, light, or dark under Settings, then Look and Feel. A system GTK theme remains available.
What changed on the updates page? Shelly 3.3 adds source filters with package counts for System, AUR, and Flatpak, an update summary with total download size, individual selection for AUR and Flatpak updates, and upgrade buttons that reflect your selection.
How do I install Shelly 3.3? On CachyOS, use sudo pacman -S shelly. On stock Arch Linux, use an AUR helper such as yay -S shelly or paru -S shelly. The pacman command is documented specifically for CachyOS.
Is Shelly 3.3 written in Rust? No. The project is written primarily in Zig, with a GTK4 graphical front end. Vala appears as a build prerequisite, but Zig is the main language.
Sources
- Shelly GitHub repository
- Shelly releases page
- Shelly v3.3.0 release notes
- Shelly tags and release dates
- Shelly official documentation
- Pearl desktop shell project