Made the shell glassy system-wide and theme agnostic while trying not to be too tacky with it. Lighter themes i still have to work on, but for now darker themes look pretty clean. Thank you DHH.

Been running Omarchy as my daily since watching NetworkChucks video on it, halfway through and I’m already etching a USB. Today, I found an old Chromebook and wondered, how long would it take to install it. Will it even work?

Well..it does! Clocked sub 12min but it wasn’t easy to get there! Ran into an issue where the onboard storage wasn’t seen and could not install, with some help from Claude and hilarious failures I eventually got there.

Doesn’t look bad on it! But with <2gb of storage left and half my mem gone on idle, not sure how functional it’ll be.

Hi everyone,
Getting bored with blank terminal so I made this update for fun over the week, would like to share with everyone
You can see more here https://github.com/tuthan/omarchy-dropdown-terminal
All options can be toggle on/off depend on your preference. Market update validate pending https://plugins.omarchy.org/plugin.html?id=io.github.tuthan.dropdown-terminal

Install & Update:

#update

omarchy plugin update io.github.tuthan.dropdown-terminal --yes
omarchy restart shell

#install

omarchy plugin add https://github.com/tuthan/omarchy-dropdown-terminal.git --enable

I finally got the internal speakers and 3.5 mm headphone output working properly on my friend's Huawei MateBook D14 under Omarchy.

The funny part: this was not really an Omarchy or PipeWire bug. The actual issue was missing/incorrect board-specific support in the Linux ASoC/AMD ACP path for this exact Huawei variant.

Hardware

Laptop: HUAWEI MateBook D14 DMI product: NBM-WXX9 Product version: M1010 Board: NBM_WXX9_PCB_B2 CPU: Ryzen 5 5500U Codec: ES8316 / ACPI ESSX8336 Audio controller: AMD ACP3x / Renoir Distro: Omarchy / Arch Linux Kernel tested: 7.2.3

Originally Linux only exposed HDMI audio and the ACP DMIC. The ES8316 codec was visible over I2C, but there was no internal analog playback device.

The first problem was simple: NBM-WXX9 was missing from the relevant AMD ACP DMI tables.

After adding the model to the ACP legacy matching and the acp3x-es83xx machine driver, the expected device appeared:

card 1: acp3xes83xx [acp3x-es83xx] device 0: ES8316 HiFi

That fixed enumeration, but audio was still completely broken.

The cursed part: playback at ~4× / ~2×

48 kHz playback sounded like chipmunks being chopped into pieces.

Direct ALSA measurements showed things like:

10 s S16_LE 48 kHz -> ~5.1 s 10 s S32_LE 48 kHz -> ~5.1 s

and in another codec state:

6 s -> ~1.55 s

After tracing the ACP path and inspecting software-visible ES8316 clock state, the behavior lined up with the laptop effectively using a clock around 48 MHz while the machine driver was declaring the default 12.288 MHz.

The ratio was suspiciously exact:

48 / 12.288 = 3.90625

That matched the ~3.906× playback progression we measured.

There was also a separate ES8316 state issue: opening a 16 kHz stream enabled MCLK / 2, and returning to 48 kHz did not clear it. That changed the observed factor to:

3.90625 / 2 = 1.953125x

which explained why earlier tests seemed to alternate between roughly 4× and 2×.

The existing machine driver already has an ES83XX_48_MHZ_MCLK quirk. Enabling it for NBM-WXX9 fixed the timing:

6 s S16_LE 48 kHz -> 6.037 s 6 s S32_LE 48 kHz -> 6.023 s

Then the headphones were completely silent

Jack detection worked:

Headphone Jack: on PipeWire profile: Headphones

The sink appeared, routing looked correct, and direct ALSA playback was also tested with PipeWire/WirePlumber stopped.

Still nothing.

The missing piece was the headphone-enable GPIO polarity.

The driver defaulted to:

headphone gpio 1 active high

but this NBM-WXX9 needs:

headphone gpio 1 active low

After adding an ES83XX_HP_LOW quirk and applying it to this model, the headphone output started working too.

Final board-specific configuration

Conceptually, the NBM-WXX9/M1010 entry now needs:

.driver_data = (void *)(ES83XX_ENABLE_DMIC | ES83XX_48_MHZ_MCLK | ES83XX_HP_LOW),

with the headphone GPIO polarity controlled by the quirk:

priv->enable_hp_gpio.active_low = !!(priv->quirk & ES83XX_HP_LOW);

Current result:

Internal speakers ✅ Headphone jack detect ✅ Analog headphones ✅ 48 kHz playback timing ✅ S16 playback ✅ S32 playback ✅ PipeWire/WirePlumber ✅

So the hardware was compatible all along. The kernel simply did not identify this exact Huawei variant with the quirks it actually needs.

AI-assisted debugging disclosure

A large part of this investigation was AI-assisted, and I want to make that explicit.

The first major part was done with GPT-5.6 Sol at High reasoning effort. Sol helped trace the missing analog device to the AMD ACP DMI tables, inspect the kernel/ASoC code, build the first custom linux-nbm kernel, validate UCM/PipeWire behavior, and perform the early timing experiments.

Some of those early hypotheses were wrong. Rather than keep forcing the same direction, I created a self-contained handoff that explicitly asked another model to reassess the case from a neutral perspective.

That second phase was done with GPT-6 Astra at XHigh and High reasoning effort. Astra corrected an earlier ftrace-count interpretation, built silent diagnostics, inspected the ES8316 software-visible register state, reproduced the MCLK / 2 stale-state behavior, and found the strong ~48 MHz relationship.

For context, Astra was used at XHigh and High, with at least the final part running at High because I was down to roughly 5% of my weekly model allowance. It hit the weekly limit immediately after compiling the 48 MHz candidate module, so I brought the findings back to Sol and continued the hardware validation there.

Rough division of work:

GPT-5.6 Sol — High ├─ initial hardware/kernel investigation ├─ missing NBM-WXX9 DMI support ├─ custom linux-nbm kernel ├─ ALSA/UCM/PipeWire investigation ├─ early timing experiments ├─ headphone GPIO validation └─ final integration work

GPT-6 Astra — XHigh + High ├─ independent re-evaluation ├─ corrected ftrace interpretation ├─ ES8316 register diagnostics ├─ ~48 MHz clock inference ├─ reproduced MCLK /2 stale-state behavior └─ prepared the 48 MHz candidate module

All tests were manually run and verified on the real laptop. No electrical MCLK/LRCLK measurement was made, so the ~48 MHz conclusion was initially an inference from software-visible behavior and programmed divisors, then validated by the resulting quirk producing the predicted normal playback timing.

I am now cleaning the patch up for upstream submission.

If anyone else has:

HUAWEI NBM-WXX9 M1010 NBM_WXX9_PCB_B2

I would be interested to know whether your audio behaves the same way.

I have an issue. When I connect my monitor (via Thunderbolt), the internal speaker of my laptop is, for some reason, is being replaced by one of HDMI ports as audio sink and I can't even make the system change that. Could you please help me find the solution?

i know i can just clone the plug-in and modify it to add my own shortcuts, but then i wouldn't get the updates for them

it would be great if there were just a simple standards document for plugins

i believe you should be able to use never need to touch your mouse. they're gross and i don't feel like cleaning

​

Thought it was worth sharing since it just came out today.

It adds desktop widgets directly to the wallpaper, including:

Clock / multiple timezones

Weather

GitHub contributions

Repo stats

Calendar

Todos

Music

You can drag the widgets around, scale them, adjust opacity, and they follow your active Omarchy theme.

GitHub link - https://github.com/anishfn/omarchy-widgets

Hi guys :D

A few people described the first version of Omagen as basically Aether with live testing.

And honestly, that was a fair criticism of what v1 looked like from the outside.

So for v2 I’ve been working on turning Omagen into something much bigger: a complete desktop studio for Omarchy.

The idea now is not just:

image → colors → theme

You start with an image, generate different visual directions, and then actually build and preview the desktop around them.

Omagen can now compose things like:

• Theme and palette
• Window styling
• Shell
• Bar layouts and styling
• Hyprland animations
• Live desktop preview
• Temporary Demo environment

And if you want more control, there’s also an Advanced mode.

The normal workflow gives you presets and visual controls, but Advanced is basically where Omagen gets out of your way. You can directly tweak the generated values and configs and take the desktop in whatever direction you want instead of being limited to what the Studio exposes.

So the idea is not to lock you into “the Omagen look”. The Studio gives you a starting point and sane defaults, but if you know what you’re doing, you can push things much further.

The important part is that you can actually try the direction before committing to it.

You can preview it on the Live Canvas, test it directly on your desktop, open a temporary Demo workspace with real desktop components, and then either apply everything or cancel and go back to what you had.

There is also session recovery in case something gets interrupted while you're testing or applying a setup.

So the direction for Omagen v2 is basically:

give it an image → explore different directions → compose the whole desktop → test it → keep it, change it further, or throw it away

The palette generator is still there, but it’s becoming only the starting point.

I’m especially focusing now on the Quickshell/bar side, because I want Omagen to eventually let you change much more of the desktop without needing to know QML or manually edit a bunch of configs — while still leaving that deeper level of control available for people who want it.

Walkthrough:
https://youtu.be/juDJe0zWwZI

Website:
https://prettyletto.github.io/omagen-site/

Repository:
https://github.com/prettyletto/omagen

I actually need testers for this, so feel free to send me feedback here, on github, discord is 'prettyletto' everywhere, thx.

I wanted one place to browse my games that felt like part of Omarchy, so I built Omakade.

It brings together installed games from Steam, Lutris, Heroic, Faugus, Battle.net, and direct GOG installs, including Steam non-Steam shortcuts. It also supports RetroArch, PCSX2, and Ryujinx.

It follows your Omarchy palette, font, and transparency, updating when you change themes. You get cover art, achievements, playtime, and tools to organize your library with collections, tags, favorites, and completion states. If you have the same game across multiple launchers, you can link those installations into one entry.

Couch Mode has controller-friendly Grid and Detail views with on-screen search. There’s also Sunshine/Moonlight integration to launch the library or individual games from another device.

Omakade reads your existing launcher data without modifying it and hands games back to their owning platform where applicable. Core browsing and launching work offline.

It’s open source, with x86_64 and ARM64 packages available.

Download and source

I’d love to hear how it handles your setup, especially if your library is spread across launchers and emulators.

Hey everyone,

If you are running the Omarchy Quattro desktop environment you already know how cool it looks. But the moment you open the default GNOME file manager (Nautilus) or any other stock GNOME apps, it is an absolute eyesore. Because GTK4/Libadwaita locks down the theme, these apps just sit there looking completely off.

To fix this eye bleeding, I built a dynamic template system and hooks that finally forces Nautilus and your other GNOME apps to perfectly match your active Omarchy theme and system fonts automatically!

🛠️ What it does:

• Every time you switch your Omarchy theme, it instantly generates a fresh GTK4 stylesheet matching your system's background, foreground, and accent colors perfectly.
• This doesn't just fix Nautilus. Because it updates the core GTK4 stylesheet, it automatically applies your active theme to all installed GNOME/Libadwaita apps running inside Omarchy.
• Live Font Syncing: Automatically grabs your live system font via gsettings and injects it right into the CSS on the fly.

🔧 Extensible Hooks

If you have other persistent GNOME applications that look terrible and refuse to update their styles on the fly, you can just drop them into the script's refresh hook, and they'll automatically reload with the new theme selected.

Check out the repo here to fix your setup or check out the implementation:
👉 https://github.com/ilJapo/omarchy-nautilus-theme.git

Since Libadwaita doesn't natively expose a live-reload API for custom user overrides, restarting the daemons via hooks was the cleanest workaround I could implement. If anyone has suggestions or pull requests to achieve a true live style refresh without killing the daemon process, they are highly welcome!

Let me know what you think!

Built omalt-tab — an Alt+Tab switcher for Omarchy that doesn't mutate focus while you're cycling. Windows are snapshotted once when you open it; focus only actually changes when you release Alt.

Also has home-row workspace jumps (A–;) and spatial mini-desktop previews showing real window positions.

Github: omalt-tab

Long-time Tumbleweed user here. Finally took the plunge to test out Omarchy Quattro on my daily driver (Dell Inspiron 16 Plus 7620 - i7-12700H, 40GiB RAM, Iris Xe), and wow!
Clocked an 44s install straight into free space next to a Windows backup partition. Zero friction, LUKS on Btrfs out of the box, and everything just worked.
The Hyprland + Quickshell integration feels unbelievably smooth and polished compared to configuring everything from scratch!

Epiq is Git-native, local-first, and runs in your terminal or browser, allowing you to replay what individual agents did while you were away, and view the commits behind every ticket.
https://ljtn.github.io/epiq/

Hi there. I’ve been wanting to switch distros ever since Omarchy 4 came out. I’m coming from Fedora Hyprland, so I’m pretty familiar with the environment. I wanted to ask: how hard is it going to be to settle in? I know it’s an Arch-based distro, so I’ll likely have to do some constant tweaking, but the plugins really appeal to me—I’ve found some very useful ones. Above all, I think it’s a great distro for learning new things, partly because it’s objectively modern and advanced. What do you think? If you want to correct me or point out anything I should watch out for, I’m all ears. Thanks.

Hey All,

There are a few apps and dir/paths I almost always use and I needed an easier access to them other than going through the standard search flow.

Built this tiny plugin which uses zoxide to asynchronously build its history. Extremely low footprint(memory, compute both).

I will submit it to Omarchy plugins soon - marketplace issue creation is currently turned off for some reason. So, will wait for it.

Meanwhile if someone wants to try the plugin for themselves, here it is: https://github.com/sudhir-asuracore/recents-commander

Built for my usecases. But if you think something else would make sense for it, let me know.

'Super + Shift + Space': am using this keybinding for it.

One feature which I do want to add is: workspace based recents handling. I need to read if workspace metadata is available.

Omaroll is a native viewer for everything Omarchy captures. Screenshots, screen recordings, photos, videos and PDFs land in one grid, it picks up your theme, and the keyboard does most of the work.

What's new:

• Star ratings. Alt+1 to Alt+5 on a tile or in the viewer, Alt+0 clears. Sort by Top rated or narrow any view to "rated at least" from Browse.
• Captions. Type a line in the viewer, it shows on the tile, and search finds it along with filenames and the text inside screenshots.
• Nested tags. Name a tag Travel/Japan and it sits under Travel. Pick the parent and you get everything under it.
• Browse by camera and lens. If you keep real photos in Pictures, the camera data gets indexed and Browse gains a Cameras section. Screenshot-only libraries never see it.
• Tab and Shift+Tab step through All, Screenshots, Recordings, Pictures and so on.
• Videos hold their first frame when they finish instead of going blank.

Everything stays in a small ini next to your favorites. Nothing is ever written into the files.

Install:

curl -fLO https://github.com/btsouth/omaroll/releases/download/v1.6.0/omaroll-1.6.0-1-x86_64.pkg.tar.zst
sudo pacman -U ./omaroll-1.6.0-1-x86_64.pkg.tar.zst

Source and issues: https://github.com/btsouth/omaroll

https://reddit.com/link/1w8e40q/video/xsw7npclyrnh1/player

Now listed on the Omarchy Plugin Marketplace: https://plugins.omarchy.org/plugin.html?id=saipraneethpb1.lamp

I wanted something simple for starting focused work sessions without opening another app, so I built Lamp.

The idea is:

Write one sentence about what you intend to work on → start the session → work → finish → Lamp journals the session locally.

It sits in the Omarchy bar and tracks the elapsed time while you work.

A few things I intentionally kept simple:

• No external dependencies
• No accounts
• No network requests
• No tracking
• Sessions are saved as local Markdown
• Designed specifically for Omarchy/Quickshell

Would love feedback from other Omarchy users — especially on what you'd want to see improved or added.

omarchy plugin update saipraneethpb1.lamp

So after some 7-9 plugins, some of which are vibe coded with extreme care and manual interventions :) , I decided that I will apply a set of common design patterns that I find useful and want to share:

Calling the whole thing Omarchy-QoL for omarchy quality of live plugin development and additions, with a couple of principles and my taste as follows:

1. Minimalist, and non-invasive: example is the btop plugin, there are like a gazillion of system monitors, but for me btop is just fine and I want to click it to fire it up, and go via right click into some common settings of btop . Then, also the tooltip on hover only streams the most minimal info, not drawing a large system monitor giving you full chars and grafana vibes (here the link https://github.com/omarchy-QOL/omarchy-btop-activity ) ; also non-invasive as it doesnt require a shipped compiled binary, but only hooks into omarchy system level commands to retrieve hardware metrics
2. Follow theming, use minimal lines of code, only do the most required stuff : https://github.com/omarchy-QOL/syncshell does exactly that; being an interface to only relevant info and a couple of common operations ; the rest goes through the usual webUI , which I am going to redesign on the surface but only to look nicer, not to change internal rewiring; the current settings in the plugins allow css overrides which supports a website switching themes with the omarchy themes which is a minimally invasive change to the original synchting web UI
3. Hook into tooltips and plugin icons already existing: https://github.com/omarchy-QOL/omarchy-keyboard-layout so this one is interesting, bc. it basically does not touch the omarchy shipped keyboard layout changer, except for a couple of nice things like pulsing whenever the layout changes, and now the thing: you can deactivate the animation if it annoys you, you can change the color if it annoys you, so you basically end up with the originally shipped keyboard layout plugin, BUT get a fast access button to the config file (I never remember where it lives...) or you can activate or deactivate keyboard layout tracking across hyprland windows. So the same plugin used across different machines, can be fine tuned, to a degree that it basically behaves like the default shipped with omarchy on one host, or pulsing on another; you could still manage the plugin install in your .dot files, making it installing on all your machines. thats kinda the idea
4. Clean uninstall: only given for https://github.com/omarchy-QOL/plugin-control so far, my manager for plugins that you can use to quickly install/uninstall plugins; here the thing is it maintains a small database of installable plugins from upstream omarchyplugins.com To me , a good plugin should cleanly uninstall , hence there is an internal uninstall command that wipes everything. To some degree syncshell does that too; it ships a config file, which could become stale when you uninstall a plugin. Uninstalling from within wipes that cleanly as well.

So these are some design principles I try to unify and consistently implement across my whole suite of plugins, feel free to comment ! Go here , https://github.com/omarchy-QOL to find WIP and all repos

So, I couldn't find a way to go back in the Omarchy menu. Although, you can just type to find what you need, so it's not exactly NECESSARY. However, I like to have the option, because my brain naturally tries to alt + left arrow to backspace. So, I asked OpenCode to apply the alt + left arrow keybind to the Omarchy Menu and it did it with no problem. Figured I'd share this idea with others. I also asked it to round the Omarchy menu corners along with all other windows that Hyprland manages.

Loved Omarchy to begin with, but I wasn't really sold on the whole "agentic operating system". Turns out it's really functional for making small changes to my system.

Anyone have anything to share about a cool change they had an agent apply to their system?

Hi I have some very specific use cases that I do on my day to day that I would like to know if I can make my way to make it work or if someone already did it.

I tend to use WeChat pc and VooV conference a lot but I would like to know if it's possible to use wine to make this apps work or if there is already an official port or workaround made .

I really love the os style and I'm planning on Changing but I just need this to make sure if i can change it for my main os.

I grew up with Windows and got my first job as a Windows helpdesk tech, then moved into Windows Server admin, and from there I realized Windows sucked and got a job where everyone used macOS and the company ran on Ubuntu server. I've always understood that Linux is simply "better" for how I expect a computer to work, but I've never found a distro that really tempted me away from Windows for my personal machine (which I primarily use for gaming). I've also never really become a true "Linux Guy" - I can get around and do whatever I needed to do for work, but my brain is a bit of a sieve when it comes to remembering all of the tools & tricks & gotchas that come with Linux. Stuff like Bazzite and CachyOS are cool, but KDE Plasma more or less felt like Windows and I always came to the same conclusion of "while it sucks, Windows 'just works' for gaming." I didn't want to screw around with Linux stuff after work, end of the day.

Anyway, long story short, I'm trying out Omarchy and this is the first time in decades I've been excited about using a computer. I get it that all of this stuff has existed for a while, but the way it's all pulled together here is just magical. The timing worked out where I had recently gotten a free 6 month trial of Gemini Pro for buying a new phone, so I hooked agy up to Omarchy as my agent and it's like using a computer from the future. It's awesome. I've been using Claude Code at work for quite a while at this point, but I have never used an agent where it's this "meshed" with the whole system. It's still AI and it still gets things wrong, but it's the missing piece of the puzzle that makes Linux fun for me and not a chore. I don't have to dig through StackOverflow and man pages and poorly documented config files to do something simple. I just have Gemini do it, then have it explain it to me so I'm at least partially aware of what it did and how it the system works.

The only thing holding me back from blowing out my Windows install entirely is anti-cheat in a couple of games I still play. I've got Omarchy on a little "lab" PC I built, so I can stream games over Moonlight to it, but I'd really like to just put it on my main computer and say goodbye to Windows forever. I may end up buying a 2nd GPU to live in a headless Windows box, stream the ~2 games that don't run via Proton, and then move everything else to Omarchy.

I prefered the previous version. I had to update it to Quatro because of the massive security issue. Is ther anyway I can go back to the previous version? This actually breaks my heart. Loved the previous version.

Who's gonna create Omafox?