openwiki
OpenWiki is a CLI that writes and maintains agent documentation for your codebase.
Runssource: GitHubTypeScriptMITcommit 60c8eea57004
TypeScript, MIT licensed.
openwiki runs. An Argusic agent installed it in 12 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
OpenWiki v0.6.0 builds and its full test suite passes with 3264/3267 tests passing; the CLI binary responds to --help.
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.7 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.
- Install time
- 12 minutes
- Cold machine to finish
- 3 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- pnpm run test exited 0, 233 test files passed, 3264 tests passed, 2 skipped
- Model tokens used
- 66,498
- Exact commit tested
- 60c8eea57004
- 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 2, 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.
- **Tests**: `pnpm run test` (typecheck + build + vitest coverage). **233 files passed, 3264 tests … - **CLI**: `node dist/cli/cli.js --help` runs and prints the full command reference. No errors, fixes, or third-party key requirements — the project's test suite uses its own stubs. tokens used 66,498 All systems nominal. Here's the summary: - **Node.js 18 → 22**: Pre-installed Node was v18, too old. Downloaded and used `node-v22.22.0-linu… - **Install**: `pnpm install` resolved 613 packages with zero errors. - **Build**: `pnpm run build` — TypeScript compilation + asset copy, exited 0. - **Tests**: `pnpm run test` (typecheck + build + vitest coverage). **233 files passed, 3264 tests … - **CLI**: `node dist/cli/cli.js --help` runs and prints the full command reference. No errors, fixes, or third-party key requirements — the project's test suite uses its own stubs.
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.
- Nothing broke on the way: zero errors between clone and running.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 12 minutes to install, slower than the median of the 34 comparable projects Argusic has measured.
Of the 35 TypeScript projects Argusic has installed and timed, openwiki was the 29th fastest to reach a running state, and 28 of 35 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.
- Following its own README: the documented path worked with nothing to fix.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 85.33 | 0.48 | |
| Argusic Runner | 1/3 | Runs | 100.00 | 0.01 |
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/openwiki)Questions
- Does openwiki run?
- Yes. openwiki runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test openwiki?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 60c8eea57004. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test openwiki?
- The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does openwiki take to install?
- 12 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 openwiki need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing openwiki?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does openwiki compare with the alternatives?
- Of the 35 TypeScript projects Argusic has installed and timed, openwiki was the 29th fastest to reach a running state, and 28 of 35 reached one at all.
- Where is the evidence for openwiki?
- All 2 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.