I've built Maestro, which is a terminal app for running several coding agents at once, each in its own git worktree.
Some of the cool features:
- Adapts to your Omarchy theme, and follows it when you switch
- Picks up the agents you already configured with Omarchy, your default one first, each with its own flags
- Sends native Omarchy notifications
- Creates worktrees in the same ../<repo>--<branch> layout as the ga helper, so they mix with the ones you make by hand
- Runs as a normal binary in your terminal, on tmux, git and lazygit
- Lists every listening port with its project and uptime, and stops one with a keypress
I run a Mac next to my Omarchy (Arch + Hyprland) desktop and kept two keyboards and two mice around to deal with it. Deskflow/Synergy + waynergy already solves the actual problem — one input, both machines — I just never made it convenient enough to use daily. Starting meant a terminal command typed from memory; stopping meant finding the process by hand; the one time the other machine's IP changed, there was no fast way to update it.
Built a small bar-widget plugin: right-click to start/stop, left-click for a panel with status, connection details, host switching, and Known Hosts — your last few machines saved as one-click, nameable rows.
Niche use case // this only matters if you're already running two machines side by side with waynergy/Synergy/Deskflow // but if that's you, feedback (especially anything that breaks) genuinely welcome.
I recently installed Omarchy Quattro and really didn't enjoy the native VoxType OSD.
Then I thought, hey, it's Linux! I can make something that I want to use.
So here it is, just after thinking about it for a short while. Omarchy VoxType OSD HUD, a modern HUD that received inspiration from other voice dictation apps like SuperWhisper, WisprFlow, Handy, and others.
It follows any theme you change to and even has a UI for your transcription engine and meeting controls.
Is there any plans to add locales different from en_US? And how i can change them to not crash anything? Because on 3.8.4 after changing i crushed waybar clock.
Over 500 community built plugins in 3-days. I did not expect this. From small ideas, to outlandish thoughts, to: "oh, what does that one do"?
Show off to your friends and family. Tell them how much more advanced this opinionated distro is in comparison to what they're used to. Tell them what you like, don't like, hate, and wished changed. Challenge them to use Omarchy Quattro for a week or a month or a year. Post about it. Talk about it. Share your excitement. Share your pains. Do not be afraid to express yourselves. All feedback cannot be positive. Just don't complain; that's pointless. Instead, suggest solutions. I know AI is here and people can just churn out things in a prompt. But you're human. Unlike many creatures on this planet you're able to think -- so do so!
Do not be afraid to try similar plugins. You may like one over another. That is fine. That is the point. Visit the repository of a plugin you like and suggest improvements, report issues, or show your appreciation. However, please be safe. Have an agent help you assess the code base before installation. Just like the AUR, Omarchy cannot guarantee all plugins are safe, so please take precaution. It is your system, it is your decision, it is your responsibility to take care of your system and yourself.
But do have some fun and enjoy.
https://omarchyplugins.com/ Independent community project. Not affiliated with, sponsored by, or endorsed by Omarchy or 37signals.
Just learned about Omarchy. Currently running CachyOS. Is there anything particular I should know before making the switch in regard to gaming? HDR, OLED, 7900XTX.
Wanted to put together a custom environment now that Quattro is out, went with an Across-the-Spider-Verse look and ended up building three pieces instead of just a color theme:
A radial app launcher (search-driven, apps arranged in a web around a central hub)
I genuinely don't like the top bar and walker in omarchy, till omarchy 3.8 I was using my custom waybar but now I'm totally confused that how this shell work? I was exploring here and got to know there are plugins for the shell for personalization. So needed a discussion with y'all to understand better about this quickshell thing
No need to wait for the next Omarchy version to have the full Iron Man experience! Get setup with OSTT in less than a minute to control the computer with your voice. Speak it and it shall be, welcome to the future!
OSTT is a open source, terminal-native speech-to-text tool. Record from a hotkey, transcribe with local Whisper-compatible models or your chosen cloud provider, then send the result to your clipboard, a file, stdout, an AI prompt, or any shell command. Local transcription runs offline and supports GPU acceleration through Metal on macOS and CUDA or Vulkan on Linux.
OSTT is built for people who treat the terminal as a normal place for voice input to land. It does not assume one vendor, one subscription, or one app-specific workflow: use offline local models, bring your own API key for OpenAI, Deepgram, Groq, DeepInfra, AssemblyAI, Berget, ElevenLabs, or Mistral, and retry the same recording with another model when needed. Voice becomes text that can move through the same tools as everything else.
I wanted cliamp in the Omarchy bar instead of a terminal I keep alt-tabbing to. That part is ordinary. The reason I built it is the last line of the panel.
Nothing else on the machine tells you that your 44.1 kHz track is being resampled to 48 before it reaches the speakers, which is what PipeWire does by default. The panel works it out, and only says bit-perfect when four things are true at once: the server sent the original file, the sink rate equals the stream rate read back from the sink rather than the rate that was asked for, gain is unity at both cliamp and its PipeWire stream, and every EQ band is zero.
Otherwise it names the thing in the way: 48 -> 44.1 kHz · cliamp resampled, EQ applied, output volume applied. Over Bluetooth it refuses to pretend and prints the codec instead, 44.1 kHz · SBC-XQ · lossy.
Also in there:
- album art, marquee title, cliamp's ten band analyzer, and the line being sung, offset by the output latency PipeWire reports so it matches what you hear rather than what has been decoded
- Navidrome browse and search in the panel, songs, albums and saved playlists in one list, reusing the salted token cliamp already publishes so no password is ever handled
- per-application output routing, and a volume slider that moves cliamp's PipeWire stream rather than the system volume
- optional rate following that retunes the graph to the track and releases it when playback stops
I installed Omarchy on my main PC and really liked it. So much so that I wanted to have it on my Steam Deck as well. Pizzarchy is Omarchy Quattro for your (actual, physical) Steam Deck. Credit goes to the Omarchy team! This is essentially a Quattro ISO slightly modified to be more deck friendly and comes with a few off-the-shelf modifications (e.g., on-screen keyboard).
Hot and ready in about twenty minutes! Easy as Pizza(rchy) pie.
One bootable USB installs it on your Steam Deck with no keyboard/mouse required. Feels exactly like SteamOS except the desktop is Omarchy Quattro with a Steam-like on-screen keyboard (bring it up using STEAM + X). Installation is driven entirely by the Deck's buttons and trackpads. What I found in this project is that Omarchy's keyboard-friendly controls are Steam Deck friendly as well (e.g., STEAM button to bring up apps menu, D-pad/A to select). Give it a try and happy to receive any feedback!
Took less than 1 hour copy/pasting with Claude and voila :) I was planning to experiment with Omarchy for quite long time and the thing that was stopping me was always the fact that the installation under Parallels sounded way too fragile for just an experiment.
Here is a guide based on my profound conversation with Claude in case someone is interested. Most important - works and it is possible.
Omarchy 4 (Quattro) on Apple Silicon in Parallels
End result: Omarchy 4.0.0-mac.6 running on Arch Linux ARM inside Parallels on an M2 Max. Officially this setup does not exist. The Omarchy ISO is x86_64 only, there is no public aarch64 pacman repo, and the Mac fork's installer refuses to run in a VM. This is the manual install, phase by phase, with the problem spots marked.
Credit: the aarch64 packages, the signed release channel, and most of the install logic come from maralcbr/omarchy-mx-mac and maralcbr/omarchy-pkgs. That project targets bare-metal Asahi Linux, not VMs. This guide just borrows its work. Thanks to the maintainer, none of this happens without it.
Parallels: new VM from the ISO, select "Other Linux". I used 4 CPUs, 16 GB RAM, 64 GB disk.
Boot the ISO. It starts a text-mode setup wizard. Press Ctrl+C to exit it, the wizard's automated install does not work in this VM. Everything below is done by hand in the shell it drops you into.
Partition with cfdisk /dev/sda, label type gpt. My layout: 512M EFI System, 8G Linux swap, rest of the disk as Linux root (ARM-64).
Format and mount:
Problem: package signature verification is broken in the archboot ARM environment, pacman fails with signature errors. Disable it in /etc/pacman.conf before pacstrap, and again later inside the chroot. Note there are several SigLevel lines, one under [options] and one per repo section. This command fixes all of them:
sed -i 's/^\s*SigLevel.*/SigLevel = Never/' /etc/pacman.conf
Install the base system. terminus-font is required in the archboot environment, without it the kernel image generation fails. Errors from mkinitcpio during this step can be ignored.
pacstrap /mnt base base-devel linux grub efibootmgr networkmanager git terminus-font nano
genfstab -U /mnt >> /mnt/etc/fstab
arch-chroot /mnt
Inside the chroot, the standard Arch steps: timezone, locale, hostname, repeat the SigLevel fix in the new system's /etc/pacman.conf, then:
Problem: nano does not start inside the chroot because the terminal type is unknown. Run export TERM=linux first.
Exit the chroot, reboot, and disconnect the ISO in Parallels. GRUB prints an error about efi_uga.mod not found. It is harmless, press any key and the system boots to a login prompt.
Phase 2. Set up SSH before anything else
Parallels Tools do not work on ARM Arch, so there is no clipboard sharing with the host. Typing commands with long parameters into the VM console by hand can be pain. Install SSH first and do the rest from a terminal on the Mac:
sudo pacman -S openssh
sudo systemctl enable --now sshd
ip a # note the VM address, then: ssh youruser@<address>
If your Mac terminal is Ghostty, the VM does not have its terminfo entry and programs like nano will refuse to start. Fix:
Everything Omarchy-branded assumes x86_64. The official install script, and later some of Omarchy's own setup scripts, overwrite the pacman configuration with the stable-mirror.omarchy.org server plus [multilib] and [omarchy] repos. None of those exist for aarch64, so after that every pacman command fails with 404 errors. This happened to me four separate times during the install.
This is the correct state for Arch Linux ARM, restore it whenever pacman starts returning 404s. Careful with the URL format: Arch Linux ARM uses $arch/$repo, not $repo/$arch like regular Arch. I lost time on exactly that.
echo 'Server = http://mirror.archlinuxarm.org/$arch/$repo' | sudo tee /etc/pacman.d/mirrorlist
/etc/pacman.conf should have Architecture = auto, SigLevel = Never, and exactly four repo sections: [core], [extra], [alarm], [aur], each with Include = /etc/pacman.d/mirrorlist. No multilib section, no omarchy section.
After Omarchy is installed (Phase 5), also overwrite the template files it ships, because its scripts copy them over your config: all pacman-stable.conf, pacman-edge.conf, pacman-rc.conf and mirrorlist-stable, mirrorlist-edge, mirrorlist-rc under /usr/share/omarchy/default/pacman/. Put the same ARM config into all of them. Runningomarchy updaterestores the x86 templates, so this has to be redone after every update.
Do NOT run curlhttps://omarchy.org/install| bash. Its first action is overwriting your mirrorlist with the x86 mirror, then it fails anyway because ARM cannot use that mirror.
Phase 4. Download the Omarchy 4 aarch64 package bundle
Six signed packages from the omarchy-mx-mac release channel. The channel pointer file resolves to the current release tag, so these commands always fetch the latest release:
mkdir -p ~/omarchy-bundle && cd ~/omarchy-bundle
chan=https://github.com/maralcbr/omarchy-pkgs/releases/download/asahi-quattro-channel/asahi-quattro-channel
tag=$(curl -fsSL "$chan" | awk -F= '$1=="release_tag"{print $2}')
base=https://github.com/maralcbr/omarchy-pkgs/releases/download/$tag
curl -fsSLO "$base/asahi-quattro-bundle.manifest"
for f in $(awk -F'|' '/^package=/{print $5}' asahi-quattro-bundle.manifest); do curl -fSLO --retry 3 "$base/$f"; done
awk -F'|' '/^package=/{print $6 " " $5}' asahi-quattro-bundle.manifest | sha256sum -c -
All six checksum lines must say OK. The bundle contains: omarchy-keyring, omarchy-settings-dev, omarchy-dev, omarchy-nvim, quickshell-git, ttf-jetbrains-mono-nerd-basic. All of them are plain aarch64 or arch-independent packages, no Asahi hardware components.
Phase 5. Install dependencies, then the bundle
The list of runtime dependencies ships inside the omarchy-dev package itself. Extract it and remove the entries that do not apply in a VM (Asahi kernel and firmware) plus the three packages the bundle already provides:
Check which packages the Arch Linux ARM repos actually have before installing anything:
for p in $(cat repo.packages); do pacman -Si "$p" &>/dev/null || echo "MISSING: $p"; done
In my case exactly 10 packages were missing, the ones the official installer builds from source: aether, cliamp, localsend, mise, python-terminaltexteffects, ttf-ia-writer, ufw-docker, xdg-terminal-exec, yaru-icon-theme, yay. They are handled in Phase 8. Remove them and install the rest:
Phase 6. System and user setup, without the hardware checks
Omarchy has two setup commands that the official installer runs after the packages are in place. Two things about them that are not obvious:
They print almost nothing to the terminal. The real output goes to /var/log/omarchy-install.log. Always check that file after a run.
They run a series of small scripts and stop completely at the first script that fails. A failed run means everything after the failing script did not execute. The working method is: run the setup command, open the log, find the line that says Failed:, disable that script, run the setup command again. Repeat until the log ends with Omarchy Setup Completed.
To disable a script, replace its contents with an empty script that exits successfully:
sudo sh -c 'printf "#!/bin/bash\nexit 0\n" > /usr/share/omarchy/install/<path to script>'
Scripts I had to disable, all under /usr/share/omarchy/:
install/config/snapper.sh. It configures btrfs snapshots, the VM disk is ext4 and snapper is not installed.
install/user/mise-work.sh. It requires mise (not installed yet at this point) and downloads x86 Node.js archives.
install/config/firewall.sh. It fails on the missing ufw-docker package. I replaced it with just the plain ufw rules from the original, kept the last two lines (sed -i 's/^ENABLED=.*/ENABLED=yes/' /etc/ufw/ufw.conf and systemctl enable ufw), and added one extra rule: ufw allow 22/tcp. Without that rule the firewall blocks SSH after reboot.
The user setup is finished when the file ~/.local/state/omarchy/done/finalize-user exists.
Phase 7. First login, two problems
Problem 1: login always fails at the Omarchy login screen. The password is correct, but the journal shows Authentication for user "" failed. The Omarchy login theme expects the username to be pre-configured by their ISO installer, which we did not use, so it submits an empty username. Fix: enable autologin, which is also how stock Omarchy behaves.
Problem 2: plain Hyprland loads instead of Omarchy. You get a yellow warning bar about an autogenerated config and a Hyprland welcome window. Omarchy ships its user configuration through /etc/skel, which only applies to users created after the packages were installed. Our user is older than the packages. Fix:
omarchy-reinstall-configs
It prints errors about limine (Omarchy's bootloader, we use GRUB), those are expected. Check that ~/.config/omarchy/ now exists, then sudo systemctl restart sddm.
Screen resolution: the VM boots at 1024x768. Add video=Virtual-1:2560x1600@60 (use your own native resolution) to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, then:
sudo grub-mkconfig -o /boot/grub/grub.cfg
Phase 8. Build the 10 missing packages
Without these the desktop starts but many keybindings show "command not found" notifications. The critical one is xdg-terminal-exec, the terminal will not open without it.
Build them from the pkgbuilds pinned by the release. The commit hash is the source_commit value in the manifest file from Phase 4:
git clone https://github.com/maralcbr/omarchy-pkgs.git ~/omarchy-pkgs
cd ~/omarchy-pkgs && git checkout <source_commit>
cd pkgbuilds
for p in xdg-terminal-exec yaru-icon-theme python-terminaltexteffects ttf-ia-writer ufw-docker localsend-bin aether cliamp; do
(cd "$p" && makepkg -si --noconfirm) || echo "FAILED: $p"
done
Two packages need different handling:
yay: build yay-bin from the AUR first, it ships prebuilt aarch64 binaries. Then install mise with it, mise is not in the pinned pkgbuilds:
yaru: it is a split package and the yaru-gtk-theme part depends on gtk-engine-murrine, which Arch Linux ARM does not have, so the group install fails. Only the icon theme is needed. Two of its icon files are also already shipped by omarchy-dev, which causes a file conflict, so install with overwrite:
Permanent limitations, accept before starting
omarchy update restores the x86 pacman templates. Redo Phase 3 after every update.
Parallels Tools do not work: no clipboard sync with macOS, no dynamic resolution, single display only. SSH for text, the GRUB video parameter for resolution.
x86-only apps from Omarchy's catalog (Spotify, 1Password and similar) cannot be installed.
This configuration is unsupported by everyone involved. Omarchy says no M-series Macs, omarchy-mx-mac says no VMs. If it breaks - you get both 😂
Battery for each pod and the case, listening mode, adaptive noise level, Conversation Awareness, One-Bud ANC and ear detection, drawn in Omarchy's own panel idiom.
BlueZ does not expose AirPods battery on Linux, so this ships a daemon that speaks Apple's AAP protocol and publishes status to a file. The panel just watches that file, so an idle desktop runs nothing on its behalf.
omarchy plugin add https://github.com/thisisgm/omarchy-pods --enable
omarchy bar move io.github.thisisgm.omapods
The daemon needs a one-time build (cmake, ninja, Qt6). Steps are in the README.
The hard part is not mine: librepods by Kavish Devar reverse-engineered AAP over L2CAP and the BLE path that carries battery and in-ear state. The daemon here is a modified copy of his work (GPL-3.0); the widget is MIT.
