oh-my-claudecode
Teams-first Multi-agent orchestration for Claude Code
Runssource: GitHubhomepageTypeScriptMITcommit aaf388290609
TypeScript, MIT licensed. The project labels itself: agentic coding, ai agents, automation, claude, claude code, multi agent systems, oh my opencode and opencode.
oh-my-claudecode runs. An Argusic agent installed it in 3 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Oh-My-ClaudeCode v5.2.0 CLI tool builds and responds to version/help/info commands; 1,094+ tests pass with 3 env-constrained failures (Node 18 engine gap + shallow git).
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 100 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.
- Node 18.19.1 below engine requirement (20.x || 22.x || 23.x || 24.x || 25.x || 26.x)
- better-sqlite3 lockfloor lint test fails on Node 18 (engine not in supported set)
- inventory-graph provenance test fails: ISSUE_3702_HEAD not ancestor of shallow checkout HEAD
- inventory-graph verify mode fails on shallow checkout
- Install time
- 3 minutes
- Cold machine to finish
- 31 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- node bin/oh-my-claudecode.js --version returned '5.2.0'; node bridge/cli.cjs info printed system info; vitest run on 10 core files (185 passed), 56 HUD files (859 passed), config+CLI+hooks (163 passed)
- Model tokens used
- 146,124
- Exact commit tested
- aaf388290609
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
All the steps were completed, verified, and observed directly. Here's the full report: **Install:** `npm install` succeeded (322 packages). `npm run build` passed — TypeScript compiled, … **CLI verification:** `node bin/oh-my-claudecode.js --version` → `5.2.0`. `--help` prints full comm… **Test verification (real):** - 10 core source test files: **185 passed, 0 failed** - HUD test suite: **56 files, 859 passed, 0 failed** - Lint tests: **70 passed, 3 failed** due to environment constraints (Node 18 engine check + shallo… - Config/hooks/CLI tests: **21 + 125 + 17 = 163 passed, 0 failed** **Errors encountered (all environment constraints, none fixable without root or Node 20+):** - `better-sqlite3/vite/vitest` engine warnings (Node 18 vs required 20+) - 3 lint tests fail: Node 18 engine check, shallow git ancestry, verify mode drift — all expected i… **No third-party credentials needed.** The project builds, tests run, and CLI operates without any …
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.
- Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 3 times, so the result is not a one-off.
What did not, or is not known
- Took 3 minutes to install, slower than the median of the 8 comparable projects Argusic has measured.
Of the 9 agentic-coding projects Argusic has installed and timed, oh-my-claudecode was the 7th fastest to reach a running state, and 8 of 9 reached one at all.
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 3 minutes after the clone.
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
Topics (from GitHub)
agentic-codingai-agentsautomationclaudeclaude-codemulti-agent-systemsoh-my-opencodeopencodeparallel-executionvibe-coding
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/oh-my-claudecode)Questions
- Does oh-my-claudecode run?
- Yes. oh-my-claudecode runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test oh-my-claudecode?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit aaf388290609. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test oh-my-claudecode?
- 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 oh-my-claudecode take to install?
- 3 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 oh-my-claudecode need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing oh-my-claudecode?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does oh-my-claudecode compare with the alternatives?
- Of the 9 agentic-coding projects Argusic has installed and timed, oh-my-claudecode was the 7th fastest to reach a running state, and 8 of 9 reached one at all.
- Where is the evidence for oh-my-claudecode?
- All 3 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.