I gave a Roadster the Tokyo Night treatment and now I can’t pick a wallpaper. Electric blue. Violet reflections. An entirely unreasonable amount of time staring at my desktop. Tokyo Roadster for Omarchy. Four of the eight below. Good luck choosing ✌️

Still this the Omarchy Tokyo Night version looks better 👀 Hit me up next time @elonmusk

I now have a @Bot with its own Omarchy machine. That’s fricken cool 😅 Here it is switching themes, tiling windows and opening my markets widget. Fairly ordinary desktop stuff, until you remember who’s driving. It means I can start delegating visual QA for my plugins. Have it open panels, try different themes, check layouts and show me what actually happens on screen. Still some tweaks needed for cloud setups like this (help a fella out @poteto) but having another pair of eyes and a separate machine to test on is a pretty exciting step. I gave my bot a Linux desktop. Naturally, I’m putting it to work.

Not a clue why GitHub decided to launch a social media platform… I’d rather they improved their uptime tbh But I’m there now anyway dev-null.sh/@tcballard

Dozens more attempts to get Linux booting on an iPad tonight. A8 decryption passed. Boot patches passed. iBSS and iBEC transferred. Then the connection died before the device tree. No Linux yet. “Just one more attempt” is apparently how I live in Chicago

I wanted a shortcut wheel on Omarchy. So I built Orb 🟠 Press Super+Alt+O, pick your shortcut, get on with it. Another “that would be fun to build” now living on my desktop 😅 github.com/tcballard/omarchy…

I’ve installed Try Omarchy for Linux on my Grok Bot’s computer. Turns out giving an AI its own computer just gives me another machine to install Omarchy on. Nobody escapes the “have you tried Omarchy?” conversation. Not even the bots 😅

Someone got Linux booting on an A13 iPhone after six months of work. Exactly the encouragement I needed to aim for another 25 attempts at booting iOMARCHY on my iPad tonight. Trying Hoolock next. My definition of a relaxing evening in Chicago needs work 😅

Someone got Linux booting on an A13 iPhone after six months of work. Exactly the encouragement I needed to aim for another 25 attempts at booting iOMARCHY on my iPad tonight. Trying Hoolock next. My definition of a relaxing evening in Chicago needs work 😅

Today in Omarchy (19-Oct-2026) Yesterday’s edition covered an update that stopped partway through. Today’s biggest announcement is about testing the next ones. 🧪 Nightly QA gets a rollout plan @ThePrimeagen says he is starting to connect Omarchy’s agent-driven QA to nightly builds, with the aim of running it every day. He describes a working dashboard with live job tracking and cancellation, plus the state handling needed to manage jobs, suites and servers. The test runner still needs performance work, and the site remains private. This is an announced rollout, not a public record showing every nightly has passed. @DHH welcomed the work as a way to reduce the hours he has spent manually checking releases. 💻 Try Omarchy makes room for the notch Try Omarchy 1.1 shipped today. Fullscreen can now use the display area around a MacBook’s notch, with bar items moved out of its way. You can toggle that behaviour in the launcher. It also fixes Chromium and Electron apps crashing with illegal-instruction errors on M4 Macs, corrects Apple’s Italian keyboard layout and restores the guest clock after Mac sleep. The clock bug could make Touch ID sudo approvals fail until time caught up. Replace the app to upgrade an existing VM. The M4 fix also needs the next guest kernel update, or the release notes’ manual Limine update and reboot. This remains a VM running Omarchy’s development channel. 🤖 T3 Code can use its own updater Ryan Hughes (@ryanrhughes) merged a Quattro change that installs T3 Code’s official AppImage instead of the package its own updater couldn’t modify. The installer offers Stable or Nightly, keeps Omarchy’s initial theme selection and migrates existing users without deleting their ~/.t3 data. A failed download keeps the old package working. This is development work. The PR reports one hands-on Omarchy check; a second-machine check remains outstanding. On shared machines, another existing user may need to reinstall from the menu after the package migration. 🧰 Manual setup means manual setup The marketplace catalogue now marks six more plugins as requiring manual setup. Their authors’ notes explain the missing native build, backend or system configuration instead of offering a command that cannot finish the job. @hancore_linux also migrated 36 renamed or transferred repositories after checking their immutable GitHub identities. Existing review evidence remains tied to the reviewed snapshot, rather than automatically blessing newer code. As someone who has spent far too long trying to make installation feel simple, I approve of an honest label. A copy button is not an installer just because it looks reassuring.

Fifty attempts to boot Omarchy on my iPad mini 4. DFU works. Pongo loads. Linux, so far, does not. I do have logs. I also have an unreasonable amount of stubbornness. iOMARCHY is very much still a work in progress. If you’ve ever got Linux running on an old iPad, I’d love to hear how 👀

This week: work by day, iOMARCHY by night. One pays the bills. The other involves arguing with an iPad about who owns the hardware. Sharing my Orb plugin + demo tomorrow, too. A quiet week, then 😅

Coming in to land in Chicago. Orb demo recorded for later. Omarchy work ready to send @DHH for review. Another musing started. And 50 attempts trying to boot iOMARCHY... getting closer, DFU and Pongo there but not actual Linux :( Pretty productive nine-hour flight, if you ask me. The plane and I both had several things in progress. Thankfully, the pilot finished his first 😅

Today in Omarchy (18-Oct-2026) Omarchy 4.0.5 is out. There's plenty worth having, but OpenClaw users need to read the issue tracker as well as the release notes. 🔧 4.0.5 ships, with an OpenClaw catch Today's stable release brings Linux 7.2.8 with the BORE scheduler, Qt 6.12, faster browser and web-app launches, and fixes for shell colours and third-party plugins under the new Qt version. There are hardware fixes too, including built-in speakers on the Dell XPS 13 Panther Lake. That's a specific model, not a blanket fix for every XPS. The catch is the OpenClaw migration. It expects replacement package files that the stable repository wasn't supplying, so affected updates stop there and skip the remaining phases. Maintainer Emir confirmed the failure and posted a temporary workaround in issue #15804. Fixes merged into Quattro later today, followed by a partial revert of the migration machinery. No follow-up release was published by this edition's cutoff. If you hit that error, use the maintainer's issue guidance rather than assuming the update finished. 🖥️ Each screen gets its own workspaces Ryan Hughes (@ryanrhughes) merged a change that gives each monitor its own workspaces 1 through 10. Super+2 goes to the second workspace on the screen you're using, and its bar shows that screen's workspaces. Unplugging a monitor merges its workspaces onto the remaining screen. Reconnecting it restores them. A same-day follow-up fixes identical monitors swapping identities and stale return records. This is Quattro development work, not part of the earlier 4.0.5 release. Saved layout choices still follow workspace numbers rather than travelling with a renumbered workspace. 📝 Omawrite stops search stealing your afternoon Omawrite released 0.7.1 and 0.7.2 today. The standout is search in large documents. The 0.7.2 notes report roughly 0.7 seconds instead of 40 seconds per query on a 2 MB file, plus repaint time. The fix avoids repeated document layout and waits for a short pause in typing before restyling. That's a reported test result, not a speed promise for every document. Plain letters can also find accented forms, and word counting moves into the background. In 0.7.1, file dialogs moved out of Omawrite's process so a GTK chooser crash cannot take your unsaved writing with it. 💸 Codex gets another visible limit A new Quattro change displays Codex's individual spend cap and reset countdown when the account supplies one, including the cap-only response observed on a Business account. Previously, that response could leave the Agents panel without a limits row. It uses the reset timestamp returned by the server and doesn't guess whether the allowance is weekly or monthly. Given my ability to turn a passing idea into a token bill, having the limit visible seems sensible 😂

My Grok Bot is getting rate limited accessing X and kicked out of the browser on its own computer. Built by xAI. Evicted by X. @poteto please let the little guy back in. He’s trying to organise my life and now I’m organising his. Or do I need to email tibo@mail.grokbot.com 😅