Sunday Builders Club, Episode 5:
"The one where Wes wants an Omarchy phone."
Recorded Sunday, October 11, 2026. An hour and 49 minutes, 238 tuned in, 10 people came up to speak, and every one of them was building something.
Listen: https://x.com/i/spaces/1NGaroBgpBgJj
Full write-up and the complete transcript: https://omarchyspaces.com/ep/05/
@ncfrontiersman Wes Grimes, host, creator of OmaStorm, member of the Omarchy M team, and me @nixfred, co-host. Wes and I are the hosts but YOU are the star!
@himarkyi is giving the @omarchy Foundation $1.5 million in @grok tokens, and @namespacelabs is putting in $100,000 a year in compute for ARM testing. @JoshuaSWarren built an iPhone app on Omarchy with no Mac anywhere, and nearly 10,000 people liked that. @ryanrhughes merged 111 commits of Apple Silicon support into Omarchy itself, and Wes had a couple of them in there. The marketplace passed 5,000 plugins. And the brand new official @omarchy account on X promised that CAPS LOCK gets left alone in the next version!
Four weeks ago this @XSpaces started as a way to help newcomers. Wes renamed it for the week because the room has grown past that. Everybody here is building something, whether it is an app, a resume or a legacy, so he wanted to dig into the part nobody warns you about: what happens after the euphoria wears off. The tickets come in. The PRs come in. Anybody can be a builder, he said. It just means you are willing to roll your sleeves up, and when it gets ugly you put your head down and keep pounding, like the Panthers slogan.
Wes on the stages of AI psychosis, which go like the stages of grief. First: everything I learned does not matter anymore. Then: I could build anything in the world! Then you come back down to earth: I can, but can I support all of it? Where he landed is that he has a lot of new superpowers, but "I still got to put my mind to it."
Then we traded maintainer war stories. When I opened Blip and Infomarchy to PRs the magic happened, people sent in features and fixes I never would have come up with, but I feel guilty every time one is not the vision and I have to say no. Wes calls himself a ruthless prioritizer, because every feature is tech debt, a dependency that can break and a vulnerability that becomes his problem, and once it ships people expect it forever. His example: somebody wanted OmaStorm to follow the laptop's GPS, but not every laptop has one, so he is building a hook on the outside instead of a branch on the inside. And when the answer is no, we both say the same thing: fork it and make it yours. Don't wait on us.
Wes's rule for what to build: find a problem right around you, solve it for yourself, take it through every edge case, fix every bit of friction, then release it. Nothing is new under the sun, so if it bugs you it bugs somebody else too. And passion is what gets you through the part where you want to quit. My grandfather said it best: "If you go after the money, you'll never get it. If you do the job right, it'll hit you in the back of the head."
WES WANTS AN OMARCHY PHONE
Wes hates software keyboards. He loves the tactile kind, where you can feel the keys without looking, and he got excited about Minimal's phone: simple, a real keyboard, on pre-order and due in December. That is Omarchy in your pocket. A tool crafted to just what you need, with the GPS and the camera in your hand, and no Apple walled garden of waiting for an app store to approve you.
He does not think Apple will ever open up, so he is putting the call out. If a phone company is willing to be a hardware company first and give us the drivers, he will build a mobile OS on Omarchy. Framework, what if you made a phone? After the Studio Display kernel work, and with models like Opus 5.5, here is how he sees it: "Unless there is some very locked-down security encryption issue on the hardware, I don't see how it could not be solved." I told him I support him, and if I can help I will.
@devsec_ai
DevSec came with the part of building nobody puts in the demo, and he comes at it from cybersecurity. His app Uber Notebook is a massive one. His tip: once you have submitted a few apps and you know what the maintainer looks for, have your agent read every comment raised on your work and build a skill from it. Your agent just follows your prompts, so you repeat the same patterns, and a skill can fix a pattern. Code review will become a chore and the only way through is time, but look at the bright side: what used to take months of human peer review now takes 5 hours of agent review while you sleep, plus a pass by you.
His big warning is what he calls the disposable apps mentality. Apps get built fast and forgotten, which makes an enormous pile of waste and security holes. Build something you want to maintain, because he expects the maintainers will eventually delist apps nobody maintains, "which is the right thing to do."
I added my own: with great power comes great responsibility, and if your app wipes somebody's computer that is on you. It is easy to generate code and hard to make a surgical change without breaking something else. So ask your agent for the smallest possible implementation that still works, and ask yourself whether you could fix it by hand one day.
@neil404
Neil works in the public sector, with public defenders, and he only found out this year how good AI is. He was never a software programmer. He is building Exculpta, named for exculpatory evidence, for small publicly funded teams. Picture a public defender handed a case file with 30 body cams, statements and transcripts, with 70 cases already on the desk. You drop in the discovery and it finds the people, places, things and events, builds a chronology and a cast of characters, and links every answer to the original source. Documents get OCR'd, media gets transcribed and indexed, and you pick your own models. It runs in Docker on a Linux server with whatever GPUs you can find, on local AI where it can, because a lot of this material is confidential.
Companies charge public service folks hundreds of thousands of dollars for this and nobody has that. Neil's answer is to build it free and put it out there for everybody. Nothing to do with legal writing, by the way, so no made up citations. I retweeted it and followed him on the spot. He had to rename it this week when he found a company in Portland with the same name.
@NotJustShaking
Lee did not bring a build this time. He brought a suggestion: a Slack for the group, so the conversation does not end when the Space does, people can share their work, and the ones building plugins and tools can form groups. Cost is the question, so he wondered whether the Omacom Foundation could cover a couple of months to see if it works. If not, throw it away, or people chip in. Wes likes Slack better than Discord. I have tried to love Discord and I just cannot get there, maybe it is the Gen X in me. We are going to look into it and report back next week. In the meantime, Tim Sonner @tim_sonner set up a group chat on X for all of us. Jump in.
@calledtocnstrct
He started building little games for his grandkids, and he wanted them to work with eye tracking, because one of his grandsons is non-verbal and cannot use a joystick. Eye tracking is how he talks to the world. Back then the AI could not get there, and he could not even buy access to an SDK. He was devastated. This week he sat on his deck in the cool evening air, plugged in an eye tracker, asked the AI to build whatever driver it needed, and 30 minutes later it was working. It even built a WebSocket interface, so any web page can see where the eye is looking. Three games so far, all eye tracking compatible. "It's not as easy as it might sound to just look at something and activate it." He wants to buy every eye tracker he can, because so many hide behind the medical industry's walled gardens, and keep improving that interface.
He is also working on risk and vulnerability visibility in the package repository to bring Omarchy to corporations, and on the documentation to bring it to military and government, plus one more idea he says is too big to talk about yet. I sent him a reverse engineering playbook repo and my own eye tracking code, and Wes and I both told him we are here to help.
@StudioXRadio
Studio X Radio, call sign KB2UKA, a.k.a. Doug Serrato, runs a financial advisory firm and has been an amateur radio operator since he was 12. In March he started teaching himself LLMs, and because there was no software defined radio software for linux or mac, he and a buddy built one. It has 1,200 users now, which is big in that niche, and it talks to serious hardware, so he learned AI the hard way. That is what he brought to the M4 project, and he is on the M team with Wes.
He was holding what he believes is the first USB installer for Omarchy on the M4 MacBook Air. It boots natively from the internal SSD, with the GPU desktop, trackpad, Wi-Fi, Bluetooth mouse, speakers and audio codec working, one USB port (the one nearest the hinge), and real hardware video decoding for H.264 and VP9. Next he wipes his dev build, reloads, and tests the installer like any of us would. It is experimental, with a big disclaimer for daily Mac users, and he planned to release it as Omarchy M4 Native v0.1.0-alpha.1 within hours.
He picked up coding books many times over 35 years, and then the babies and the wife and the business came along. His line: when the chainsaw was invented, you did not see many lumberjacks swinging an axe. I told him we are not even 10% done.
@MasterMynd2004
MasterMinder built a side project to replace himself! A friend has a restaurant where a big part of the business is catering, staffing was a mess, and MasterMinder took his calls for a few weeks, thinking how hard could it be. The quoting and invoicing "kind of sucked." So he built a platform that does all the catering admin except approving the quote: intake, customer questions, the digital menu, the quote, the invoice and booking on the calendar. The chef changes his settings by messaging an assistant called Zara on WhatsApp, Telegram, email or SMS, like he would anyone else. Want the deposit split 40/60 instead of 50/50? Tell Zara and the invoices go out right. Restaurant people are busy, so no new app to learn, and no voice yet because people want to message. If something breaks, MasterMinder gets a Telegram with the problem and a suggested fix.
Now more restaurants want a trial, and the way he built it will not scale past 30 or 40 customers, so the question for the room was how to productize it. My answer: you are doing it right. You showed value first and you met people where they already are. The best problem you can have is how to scale to 45 customers. Do not spend a penny on marketing, because marketing is paying for the next customer, and you already have your next customer. Wes added: treat what you built as a prototype, point an agent at it, have it deconstruct the behavior and the specs, then build the real multi-tenant version. That kind of refactoring goes pretty well now. And the future of software is not software for other developers, it is for small businesses, freelancers and the one man show. We both offered to help. Another one from my grandfather: "We can do anything we want. We just can't do it all."
@MuchmoreIT
I know Heath in rl, and everything he does is huge. He works on the federal security hardening rules (STIGs) that tap the brakes on everything and break ports and apps, supercomputers for the hurricane models NOAA runs, and a customer looking at AMD's upcoming Helios 12 racks at roughly 235 kilowatts a rack. Where Omarchy comes in is speed. Federal teams run bloated, stock ubuntu-style linux, and that slows a lot of people down.
He and Wes share a love of weather. Heath built his own hurricane model tracker to find out how accurate each of those spaghetti models really is. He is also a former F-117A avionics guy, and he is building an Omarchy desktop version of the old MicroProse F-117A flight sim, with the things the game got wrong fixed. Wes loves weather and avionics, so they have to talk. And Heath's company's lawyers finally cleared his patents, so he may open up about quantum encryption. I say I know how to scale stuff. Heath scales me.
@JamesTervit
James was up at 4:30am in the morning in Singapore, which is Monday for him, because that is the only way to catch a Sunday in the States. What got him into Omarchy was Andrew Boyd's T1 bridge. His 2017 MacBook had been collecting dust, and for the first time a Linux build went straight on and everything just worked. The same day he put a little animated desktop character on it that takes voice commands for his agents. "I've been able to actually get all of this done in a single day. So that was a first."
He has been in the AI and security weeds since NVIDIA Morpheus in 2019, on packet radio since the bulletin board days, into LoRaWAN and embedded systems, and he did head tracking from a webcam back in 2015 because a game had too many controls, so Called To Construct's eye tracking hit home. And he is finishing Omarchy Warp: a browser on another PC on your LAN becomes your second monitor, and the mouse glides across like it is one screen. Heath wants to talk to him about software defined radio. I told him I only heard a quarter of his story, so we are setting up the next Zoom.
@thisisgm
Flea's author had a week. Wednesday he ran out of tokens, so he spent the downtime tuning performance until he was measuring key to key input latency in file managers. Dolphin won at around 11 milliseconds a key, and Flea got close. Then on Friday somebody told him Qt got bumped to 6.12 in Omarchy's dev branch and it broke Flea. He asked on X whether stable had it too, and DHH himself replied. He pushed the new features out to 0.3.10 and got the fix out first. Tundy @thetundeo, the CEO of ZeroRAMP, sponsored more AI for Flea, and GM said thank you in front of everybody.
What he wants most is people to hammer test it. Click around, try to break it, so he can spot what the AI cannot. Issues and PRs are always welcome, and he credits everybody, even if all you did was point out the issue. My specialty is breaking stuff. A month ago this was one guy in his apartment with the idea of a file manager, and now it is a whole thing worldwide. His line to everybody: "If I did it with a 9-to-5 and limited budget and tokens and time and all the excuses that people use to not make stuff, just prompt the AI, make something, put it out there." Wes says he will be the subject of a documentary one day. GM says it is a file manager. Sure.
@hicsfh
Chris closed us out with Atmos, and he is honest that he does not quite know what to call it: a config center, a control panel, a preference pane, a monitoring thing. The Windows control panel never worked as well as it could, and neither does Spotlight on a Mac. Atmos covers themes, Hyprland, default apps, your hardware down to the serial numbers, and Omarchy updates, and he just submitted it to the marketplace. He is a mouse person, 30 plus years of it, not a keyboard whiz and not a Neovim person, and he is okay with that. Wes: that is what makes Omarchy great, you make it what you want it to be.
Omarchy exploded with Quattro, but it is still a small corner of X compared with the world, and most of our colleagues have not tried it. His ask: break it, then tell him instead of walking away. He is trying to figure out how to use AI to close the blind spots all of us have in our own apps. I use Atmos every hour. I made it a super hot key and it drops down like a Quake terminal.
ASKS ON THE TABLE
Join the X group chat @tim_sonner set up, and follow everybody in the room. We are small and we all like the same things.
If you know somebody at a phone or hardware company, point them at Wes. He is serious about the Omarchy phone.
Hammer test Flea and Atmos. Click around, try to break them, and tell GM and Chris what you find.
@StudioXRadio 's Omarchy M4 alpha is headed for the wild. It is experimental, so read his disclaimer before you wipe anything.
NEXT SUNDAY
Same time, 3PM EST and X Spaces! The Top 10 list lost out to a room full of builders, so it keeps. @Shpaq4Fun was first in line and X would not promote him. Come back next week! If you did not get to speak today, we are sorry, please come back!
And remember! Help an old lady across the street, and when you get her over there, put Omarchy on her laptop. Wes says we need a T-shirt for that.
/Nix and Larry