An opinionated look at how I use Fedora COSMIC Atomic
How I combine Fedora's atomic base, COSMIC's keyboard-driven tiling, Flatpak, Homebrew, Mise, and containers into a low-maintenance Linux workstation.

I want an up-to-date operating system, but I do not want its maintenance to become a hobby. When I used Arch Linux, updates sometimes left me with a black screen or an unbootable system. I enjoyed the control, but not the time it demanded.
I want the same things from my OS as from my code: predictable behavior, modern tools, and something I can maintain over time. In that sense, boring is a compliment.
I am also a heavy keyboard and terminal user. Constantly arranging windows with a mouse does not suit me. Fedora COSMIC Atomic gives me a reliable, image-based system and a desktop built around automatic tiling.
One Job for Each Tool
The most important part of my setup is not any individual tool. It is the boundary between them:
| Layer | What I Put There |
|---|---|
| Fedora deployment | The kernel, drivers, desktop, system services, and critical host packages |
| Flatpak | Graphical desktop applications |
| Homebrew | Everyday command-line and terminal applications |
| Mise | Language runtimes and version-managed tools, globally and per project |
| Toolbx or Distrobox | Occasional mutable or distribution-specific environments |
This is a guideline rather than a law. It means using several package managers, but each has a clear role. I would rather update them separately than make every application and development tool part of the operating system.
Keeping Fedora Atomic Small
Fedora Atomic updates a deployment instead of changing the system that is currently running. rpm-ostree prepares the next deployment beside the current one, and the machine switches to it after a reboot. If preparation fails, I still have the complete old deployment. If the new deployment causes trouble, I can select the previous one from the bootloader.
This is why I prefer the term atomic to immutable. Fedora made the same distinction: the system is not literally immutable. /usr is normally read-only, but /etc, /var, and my home directory remain writable. I can also layer RPM packages onto the Fedora image.
I used to treat package layering like a conventional package manager. Updates became noticeably slower because rpm-ostree had to resolve my packages and build a derived deployment on every update. It also became harder to tell where Fedora’s image ended and my changes began.
Now I layer only software that must be part of the host or does not work well through the other tools. My current list contains only gcc and libatomic. Adding them resolved problems I encountered while installing and using Homebrew. They are exceptions needed by my setup, not a list of packages everyone should install.
Why Not NixOS?
NixOS offers declarative configuration and system generations that can be rolled back. I have not used it: its configuration model does not match what I want from my workstation. I do not want to manage my OS as another codebase. I prefer Fedora to publish and test the base while I keep my local changes small.
COSMIC and Automatic Tiling
COSMIC is a complete desktop developed by System76, not only a tiling compositor. I get panels, notifications, power and display settings, workspaces, keyboard shortcuts, and graphical configuration without assembling those pieces myself.
Automatic tiling is the reason I chose it. With tiling enabled, new windows arrange themselves instead of overlapping, and I can focus, move, resize, stack, or float them from the keyboard. I can enable tiling per workspace and leave it off where floating windows make more sense.
Most of my work happens in a borderless Ghostty window with Neovim, alongside a browser that I control with Vimium. These windows fit naturally into predictable regions. Workspaces separate different contexts, while window stacks let related applications share one tiled area as tabs.
Why Not Hyprland?
I used Hyprland for a while, but its level of customization goes beyond what I need. I now prefer COSMIC’s integrated desktop while keeping the tiling workflow I enjoy.
Graphical Applications with Flatpak
Most of my graphical software comes from Flathub, including browsers, editors, LibreOffice, Signal, GIMP, and OBS Studio. I also use COSMIC’s Flatpak repository for some additional applets.
These applications update separately from Fedora. Flatpak runtimes also keep their library requirements away from the host base.
I still check an application’s permissions. Flatpak sandboxing is only as restrictive as the access an application receives, and a verified Flathub badge confirms the publisher’s identity rather than guaranteeing that the application is safe.
AppImages When Flathub Is Not Enough
Flathub does not always have the applications I want. In those cases, I sometimes use AppImages, which I manage and update with Gear Lever. I would prefer to manage them through COSMIC Store too, so that my graphical applications shared one interface.
Command-Line Tools with Homebrew
Homebrew on Linux manages my editors and shells, Git tools, terminal utilities, infrastructure tools, and modern Rust-based commands. They are immediately available in my host shell, which matters because the terminal is my primary interface to the computer.
I could put these tools in Toolbx, but then I would need to enter a container, remember which container owns a command, or export wrappers back to the host. Homebrew gives me a broad and current CLI catalog without modifying /usr or creating an rpm-ostree deployment. Updating a command does not require a reboot.
I keep a Brewfile in my dotfiles so I can reinstall my usual tools on a fresh system.
The Trade-Offs
Homebrew has its own update lifecycle, uses additional storage, and has no simple transactional rollback. Third-party taps require trust, and Fedora is not a Tier 1 Homebrew host.
Development Tools with Mise
I use Mise for language runtimes and tools that need version management. I set global defaults, such as my usual Node.js version, and override them in individual projects when needed. Homebrew handles my general command-line tools.
Choosing Which Command Runs
Command lookup order matters too. I put Mise’s shims first in $PATH, followed by system paths and then Homebrew:
/home/akhansari/.local/share/mise/shims
/usr/bin
/usr/local/bin
/usr/local/sbin
/home/linuxbrew/.linuxbrew/sbin
/home/linuxbrew/.linuxbrew/bin
/home/akhansari/.cargo/bin
/home/akhansari/.local/bin
Mise comes first so its selected versions take priority, whether they come from my global configuration or a project override. For other commands, I prefer Fedora’s packages over Homebrew when their names overlap. This also means that installing a newer version with Homebrew does not automatically make it the default.
Toolbx and Distrobox for Exceptions
Toolbx gives me a mutable Fedora environment with a conventional package manager. Distrobox covers cases where I need another distribution’s userland. I keep both available for troubleshooting, experiments, and disposable environments, but I do not use either as the default home for everyday commands.
Their close host integration is convenient, but it also means they are not security sandboxes. Rootless Podman does not make container root equivalent to host root, but processes inside the container can still modify files exposed through shared directories, including my home directory, which is shared by default.
My Maintenance Routine
Once a week, I update Fedora and my Flatpak applications:
rpm-ostree upgrade
flatpak update
I reboot when convenient to start using the new Fedora deployment.
Every day, I update my Homebrew tools and run mise upgrade outside project directories to update my globally configured tools:
brew upgrade
mise upgrade
Upgrading my machine from Fedora 43 to 44 was a no-brainer and pretty fast, one command and a reboot:
rpm-ostree rebase fedora:fedora/44/x86_64/cosmic-atomic
Available targets can be checked with ostree remote refs fedora.
If a system update causes trouble, I can make the previous deployment the default again with this command and a reboot:
rpm-ostree rollback
A rollback is not a backup. It does not restore /home, application data under /var, or independently updated Flatpaks. It protects the operating-system deployment, not all the data on the machine.
There is no single update or rollback command for the whole setup. I accept that trade-off because each tool has a clear role. Apart from the initial Homebrew setup problems, this arrangement has worked well for me so far.
Conclusion
This setup asks me to manage several tools, but keeps changes to the operating system small. For the way I work, that is a worthwhile trade-off.
For me, the best operating system is the one I can mostly forget is there.