ThePrimeagen launches Bug or Not so the community can help Omarchy’s QA decide what is a bug
Sign in with an email, look at a case, vote bug or not. ThePrimeagen admits the site is rough, and its first voters are already asking for a skip button.
Image: Omarchy (omarchy.org)
ThePrimeagen wants a second opinion on Omarchy’s bugs, and he is asking the community for it. “So the QA has been a bit difficult to always gauge things as bugs or not,” he wrote in a post on X on November 13, 2026, addressed to “all people that like Omarchy”. “If you want to help out a bit, I made a Bug or Not site.” Then: “Just sign in with an email and you can say whether something is or is not a bug.”
It follows the QA work he took on when he joined Omarchy Core to lead Agentic QA, less than a month after he said Omarchy QA would start running against nightly builds. The post itself does not say where the cases on the site come from, or whether the votes feed back into the omacom/omarchy repository. It says “I made”, and does not present Bug or Not as an Omacom project.
Bug or Not sits behind a sign-in: logged out, it only answers “Sign in to vote.” When a reader said the email sign-in and the domain set off his “scam spidey senses”, ThePrimeagen replied that “i don’t save it other than for the durable object name effectively,” and that every voter gets “your own ordered list of bugs”, so that anyone who goes through, say, five items “could very well touch 5 unique items compared to everyone else.” Asked whether the code is on GitHub, he answered: “yes, just private.”
He is not pretending it is polished. Seconds after the announcement he added: “this is SUPER slopped site, please …. don’t worry about it.” The most common request in the replies was a way out of cases you can’t judge, under names like “skip”, “IDK” or “not sure”. To one of them, he answered that he would open up a “text third option” to people who “vote a decent amount and are correct”.
The first voters’ reports, which are their own observations, show what is still rough. Two said the first cases they got were already marked “Fixed”. One wrote that in four of the five cases he tried, the screenshots “don’t really show the bug or the alleged fix”, pointing to a Quake console case. Another saw duplicate images, and one found the whole thing “WAY harder than i thought it would be.” Others were wary of the trm.sh domain and the email sign-in too, while one reader offered to help, citing seven years in software and hardware QA.
Source: https://x.com/ThePrimeagen/status/2121340299234402484
