The reading order
-
1.
I Put Omarchy on an M1 MacBook Pro
What happens when you stop buying the Mac and run the agent stack on Linux instead. Omarchy on an M1 via omarchy-mac and Asahi Alarm — thirteen coding agents pre-wired, a usage panel in the top bar, and segfaults handed to whichever agent you set as default. The catch: arm64 container images don't run on GCP, and buildx-plus-QEMU costs 3-5x on every build.
-
2.
Linux Setup Was a Hazing Ritual. Agents Changed It.
The opinion piece: Linux setup was a skills test, and the test was reading wikis. Six breakages across an M1 and an x86 desktop, from aquamarine mid-install to WoW mouse input to two printers, mostly fixed in five minutes or less with an agent against an estimated two to five hours each before. The keyboard and the card scanner took longer, and the post says so.
-
3.
I Read Omarchy's AGENTS.md So You Don't Have To
Someone else's AGENTS.md, read from the source: a 133-line router into seven task skills, a docs tree split by genre and audience, a skill that makes the agent screenshot its own UI change before finishing, and five design docs where every one that reached revision 2 names an adversarial Codex review in its third line. Six of the 30 most recent commits carried an agent trailer.
-
4.
Omarchy Shortcuts on a Mac Keyboard: What Changes
The reference page for the parent post: Omarchy's 200+ keybindings mostly survive a MacBook keyboard, and about fifteen don't — no Print Screen key, media keys on the top row, a lid switch with a different name, a trackpad that ships tap-to-click off. What the Mac fork rewires, and the one-line reason for each from its own source comments.
-
5.
Omarchy Runs Your Coding Agent With the Safety Off
The attack surface a security lead inherits when an engineer installs Omarchy: eleven of the fourteen agents its launcher knows get their own skip-approval flag by default, thirteen CLIs each hold a credential, crash notifications hand a core dump — which Omarchy's own skill says can hold passwords and tokens — to that same launcher. Credited in the same post: mandatory LUKS, a default-deny firewall, and a passwordless-sudo toggle that expires in 15 minutes and fails closed. What a vCISO would require before it goes on a company laptop.
-
6.
Omarchy on a Company Laptop: The SOC 2 Verdict
The compliance verdict for a founder or CTO: yes, under six controls. LUKS and a default-deny firewall ship and need nothing; screen lock ships a 300-second default the user can switch off from a hotkey, so the control is the policy, not the software. MDM enrollment (Fleet added Arch and Omarchy in 4.75.0), patch-cadence evidence for a rolling release, one vault for thirteen separately authenticated agent CLIs, a backup target with a restore test, and a written approval-mode policy for unattended agent runs.
-
7.
Would I Trust Agents to QA My Daily Driver?
Omarchy's release QA is now a swarm of agents driving fresh QEMU guests, and I take updates within days, so it's my QA gate too. What the harness gets right: one tool call per model reply, a fresh disk per test, 16 failure points written down, 1334 unit tests green. What it can't catch: anything working as designed. And the open question: the diagnose step runs OpenCode with --auto and two permissions set to allow, on a host holding an OpenRouter key.
Other topic guides
- AI engineering What production AI engineering actually looks like in 2026 — the autonomy ladder for agents, the workflow shift, telemetry, and team sizing.
- Security for startups A guided reading order for startup security — what to read first on SOC 2 as a revenue tool, vCISO hiring, and securing AI-native products.
- Engineering leadership Engineering leadership at startup scale — hiring from one engineer to fifteen, rituals that work at small teams, the staff-engineer interview loop.
- Elixir and the BEAM for AI systems Why language choice matters for AI systems — BEAM concurrency for agents, what Go frameworks cost you, and why Elixir is the language AI writes best.