You wouldn't believe the hours I spent manually testing and verifying Omarchy releases during the first year. With Prime's stellar work leading the QA effort, we can finally replace all that toil with agents 🤘
Big Omarchy QA News:
The Headline:
* Omarchy QA will start running against nightly every day. Still some huge hurdles to figure out, but that is the fun stuff.
The Meat:
Omarchy QA is going slower than I hoped for, but its getting into place. This is my second fully running agent test harness where they decide what is good.
* A nice running dashboard with cancellable states
* Jobs, suites, servers: have all the possible states and transitions you would expect from build servers. This part was the most surprising as it is really in depth how much effort you have to spend thinking about every possibility
* suite states, live updating website that ... runs fast? Yes I did something crazy... I made a cache, i know, actual crime...
** I even have an idea to make this load instant for every single user, and make updating cache contents LIGHTNING fast...
*** Fun side note. WTF ARE YOU DOING EVERYONE, WEBSITES ARE FUN TO MAKE FAST AND YOU ALL ARE MAKING HORESHIT SITES... STOP.
* ability to follow live running jobs and cancel them
The sad part is I have had no time to get the actual custom harness running fast, which is ok, but its hard. Now, starting today, I am going to be hooking up nightly builds and actually running this against production!
Will think about how to make this a public site, but for now, its private :(
Oct 19, 2026 · 3:51 PM UTC
I’m working on a desktop environment on top of XLibre, with similar features to Hyprland. Since it’s on XLibre I running builds in a VM/qemu and agents can ssh in with X screen sharing and screenshot the desktop and agents then analyze the screenshots. Basically no human to test all the visual and windowing functionality.
Use a ladder
(jk but basically)
'Ask another model' isn't one feature. My agents climb a ladder:
review → found a High-severity bug
blind → exposed a race
disagree? → a panel settles it
UI change? → a browser agent clicks through it
409 second opinions in 5 weeks. 70% cost $0.
How:
It's one MCP server. Claude Code and Codex call it before a risky step, and it always asks the other model family.

Anthony Russano@russanoOct 19
United States
United StatesConnected via United States App StoreAccount-level information, not a live location or per-post device.
This is the correct use of agents. Glad Prime’s building this out... the stress reduction should be massive once it's fully live.

rakesh@SublimeCoderXOct 19
India!
IndiaConnected via India App StoreLocation may be affected by a proxy or VPN.Account-level information, not a live location or per-post device.
release qa is the perfect agent job... right up until it decides a flaky test is "probably fine"
The interesting line in Prime's thread is "agents decide what is good." I'd keep one split strict: agents can run the suite every night and block a release on their own, but shipping a build should still take a human yes. A wrongly blocked release costs you a few hours. A bad build in users' hands is much harder to take back. Is Omarchy QA allowed to stop a release yet?
Manual testing is such an endless pain. I’ve spent nights staying up and making sure everything works before each release of @OmarchyMac
Prime’s harness will be a relief for us!





































