omarchy
Beautiful, Modern & Opinionated Linux
Runssource: GitHubhomepageShellMITcommit c352b62d6745
Shell, MIT licensed.
omarchy runs. An Argusic agent installed it in 0 minutes and hit 15 errors on a clean machine with no GPU, and the whole session was recorded.
CLI test suite passes clean (68/68). The core template rendering engine no longer jams multi-line output onto one line. The ascii art and Grok registry migration tests reflect current code. The hardware and browser launcher tests find their helper commands.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 89.3 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Template renderer lost newlines by using awk's RT in a getline loop5 minutes
- Grok migration uses mise unuse -y -g but tests expected unuse -g4 minutes
- ASCII test expected Hi=18 columns, font now produces 302 minutes
- hw-hybrid-gpu test PATH missing $ROOT/bin2 minutes
- launch-browser test PATH missing $ROOT/bin2 minutes
- mise not installed in container (rootless)2 minutes
- Install time
- under a minute
- Cold machine to finish
- 74 minutes
- Errors hit and fixed
- 15 hit, 7 fixed with no human help
- How the result was proved
- bash ./test/cli exited 0 with 0 not-ok lines; 4 individual shell tests verified fixed: ascii-test.sh 0/17 failures, default-agent-test.sh 0/40 failures, hw-hybrid-gpu-test.sh 0/8, launch-browser-test.sh 0/3
- Model tokens used
- 1,182,281
- Exact commit tested
- c352b62d6745
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
4. hw-hybrid-gpu-test.sh: missing ROOT/bin in PATH 5. launch-browser-test.sh: missing ROOT/bin in PATH exec /bin/sh -lc 'date +%s' in /work/repo succeeded in 0ms: 1791534554 2026-10-09T08:30:06.697687Z ERROR codex_core::session: failed to record rollout items: thread 01a11… 2026-10-09T08:30:06.697738Z ERROR codex_core::session: failed to record rollout items: thread 01a11… 2026-10-09T08:30:06.697777Z ERROR codex_core::session: failed to record rollout items: thread 01a11… 2026-10-09T08:30:06.697798Z ERROR codex_core::session: failed to record rollout items: thread 01a11… tokens used 1,182,281
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 0 minutes.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Hit 15 errors during setup, 8 of which were not solved.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 0 minutes after the clone.
Run history
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/omarchy)Questions
- Does omarchy run?
- Yes. omarchy runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 15 errors on the way, and recorded the session.
- How did Argusic test omarchy?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit c352b62d6745. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test omarchy?
- The run that produced this verdict cost $0.48: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does omarchy take to install?
- 0 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does omarchy need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing omarchy?
- 15 things broke in the recorded run, and 7 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for omarchy?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.