ohmyzsh
🙃 A delightful community-driven (with 2,500+ contributors) framework for managing your zsh configuration. Includes 300+ optional plugins (rails, git, macOS, hub, docker, homebrew, node, php, python, etc), 140+ themes to spice up your morning, and an auto-update tool that makes it easy to keep up with the latest updates from the community.
Runs with mockssource: GitHubhomepageShellMITcommit 9112b53fa8b5
Shell, MIT licensed. The project labels itself: cli, cli app, oh my zsh, oh my zsh plugin, oh my zsh theme, ohmyzsh, plugin framework and plugins.
ohmyzsh runs, with stand-ins for the services it depends on. An Argusic agent installed it in 10 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Oh My Zsh is installed and working: zsh 5.9 runs with robbyrussell theme, git plugin, omz command, and completion system, with 359 plugins and 143 themes available.
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 92 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.
- Codex-bundled zsh (5.9.0.3-test) was incomplete: modules not bundled, compiled-in module path points to non-existent directory4 minutes
- zsh not installed in container: no zsh binary in PATH or system3 minutes
- zsh -n syntax check fails on certain plugins (zsh-interactive-cd, zsh-navigation-tools) because module_path not set for no-exec mode1 minute
- Install time
- 10 minutes
- Cold machine to finish
- 14 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- Model tokens used
- 104,174
- Exact commit tested
- 9112b53fa8b5
- Container image
- sha256:4c3d41857be3
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.
- How the result was proved
- runs before 2026-09-07 did not record the command used to check the result
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
# I know the session started around when the initial ls ran' in /work/repo succeeded in 0ms: Start time placeholder exec /bin/sh -lc 'echo "Session started roughly at epoch:"; date +%s' in /work/repo succeeded in 0ms: Session started roughly at epoch: 1788435067 I estimate this took approximately 10 minutes. Let me summarize the errors I encountered and their … tokens used 104,174 I estimate this took approximately 10 minutes. Let me summarize the errors I encountered and their …
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
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 10 minutes to install, slower than the median of the 24 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 25 cli projects Argusic has installed and timed, ohmyzsh was the 18th fastest to reach a running state, and 23 of 25 reached one at all.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.09 |
Topics (from GitHub)
clicli-appoh-my-zshoh-my-zsh-pluginoh-my-zsh-themeohmyzshplugin-frameworkpluginsproductivityshellterminalthemethemeszshzsh-configuration
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/ohmyzsh)Questions
- Does ohmyzsh run?
- ohmyzsh runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 10 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test ohmyzsh?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 9112b53fa8b5. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test ohmyzsh?
- The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does ohmyzsh take to install?
- 10 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 ohmyzsh need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing ohmyzsh?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does ohmyzsh compare with the alternatives?
- Of the 25 cli projects Argusic has installed and timed, ohmyzsh was the 18th fastest to reach a running state, and 23 of 25 reached one at all.
- Where is the evidence for ohmyzsh?
- 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.