November 9, 2026

Theo says Omarchy has almost all the agent capabilities he’s building into t3os, and recommends it for remote agents

0

The t3os author says he doesn’t know when his own OS will be finished. His early computer-use numbers are still unpublished, but he’s already telling his audience where to run remote agents.

Omarchy agents panel showing 23.8M tokens today, with usage bars for Claude Code, Codex, Grok and Cursor accounts

Image: Omarchy 4.5 release notes (omarchy.org)

Theo of t3.gg is building his own operating system, t3os, and he just told his audience to use someone else’s. “The more I benchmark, the more I realize Omarchy has almost all the agent capabilities I am trying to bake in. It’s a really good choice for remote agents, and you should probably use it,” he wrote on X on November 7, 2026. By the morning of November 9, the post had more than 186,000 views and nearly 3,500 likes.

The same post opens with an apology, but it isn’t a goodbye. “Idk when I’ll have the time to finalize t3os. Sorry for those still waiting,” he wrote. A minute later he was already looking ahead: “Best part: I know @dhh and @ryanrhughes will immediately match t3os in agent capability the day it drops. I plan to send them the os/computer use benchmarks ahead of time so they can keep hill climbing on their end,” he added in the thread. So t3os has no date, but as far as Theo is concerned, it’s still happening.

The benchmarking goes back to October 31, 2026, when Theo said he was “working on a computer use bench to measure task success and fail rates on various OSs.” His “current state” at the time: “MacOS at the bottom (27% pass rate). Omarchy and t3os at the top (100%).” DHH’s reply was short: “A saturated benchmark is a bad benchmark. Bring it on!”

Take those numbers for what they are. They are preliminary figures from a single post, and as of November 9 we could not find a published task list, run count or repository for the benchmark. Later on October 31, Theo also told DHH “Good news (I think the android omarchy one was a flake – investigating now)”, without explaining in that post what the “android omarchy” result was. And he is hardly a neutral referee: t3os is his own project, and it shares the top spot in his own test.

So why not just use Ubuntu? A reader who runs Omarchy on laptops but Ubuntu on always-on boxes asked exactly that. “Too many permission issues and computer use edge cases on Ubuntu by default. Once set up right it’s pretty good but getting it there is fkn obnoxious,” Theo answered, before landing the line of the thread: “Agents understand Ubuntu better, but they use Omarchy better.”

There is a catch if you’re picturing a bare server. Reminded that he once said Omarchy was only useful with a screen, Theo replied: “Still mostly true! It’s not optimized for headless usage but agents can work around that well enough.” He added: “I promise my statements on this will make way more sense when t3os drops.”

Theo didn’t name an Omarchy version in these posts, and his October 31 numbers predate Omarchy 4.5, which shipped on November 4, 2026. Agents were still a big part of that release. The 4.5 release notes call Omarchy “the agentic OS” and say the agents panel “now tracks 23 agents and providers, up from 6.” For working across machines, omarchy agent account copy brings your agent logins over SSH, and the new default app Gliff “gives you a remote desktop over SSH.” Whether any of that figured in his recommendation, he hasn’t said.

The Omarchy crowd noticed. Ryan R. Hughes reposted Theo’s post without comment, and Marcelo Alcantara, who recently joined Omarchy Core, replied “Thanks for the note.” Tom Ballard was more effusive: “when Theo speaks like this, makes me happy I’m pinning my mast to Omarchy.”

As of November 9, we found no reply or quote from DHH on the recommendation itself. If those benchmarks do reach him, he has already said what he wants from them: something harder than 100%.

Source: https://x.com/theo/status/2119159746393731109

Leave a Reply

Your email address will not be published. Required fields are marked *