wikiman
Wikiman is a universal offline documentation search engine for manual pages, tldr-pages, ArchWiki, Gentoo Wiki, DevDocs, and FreeBSD documentation
Runssource: GitHubShellMITcommit 353e165bf95c
Shell, MIT licensed. The project labels itself: arch wiki, cli, devdocs, documentation, freebsd, gentoo wiki, linux and man pages.
wikiman runs. An Argusic agent installed it in 14 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Wikiman 2.15 is built, installed under ~/.local with pre-built runtime deps, and verified searching real man pages plus working arch/tldr/devdocs/gentoo/fbsd sources through raw and interactive paths with no errors.
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 96 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.
- container had no man-db man binary (stub printed 'system minimized') and no fzf/rg/w3m/parallel/gawk6 minutes
- mawk 1.3.4 crashes with 'REcompile() - panic' on gentoo source regex, making the default full search emit a crash line4 minutes
- user-install layout mismatch: app computes ~/.local/share/share (build prefix $HOME/.local) and ~/.local/bin/wikiman symlink needed2 minutes
- initial mock wiki trees for tldr/arch/fbsd/gentoo/devdocs did not match source-module directory conventions, producing no results or malformed rows2 minutes
- Install time
- 14 minutes
- Cold machine to finish
- 14 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- make all exit 0; make install exit 0; wikiman -v returned 2.15; wikiman -S shows 6/6 sources active (man 316 pages); wikiman -R -s man -q intro returned 9 rows exit 0; wikiman -R -q grep returned tldr row exit 0; PTY TUI: fzf menu rendered, Enter rendered intro(8) manpage, clean exit code 0
- Model tokens used
- 1,308,991
- Exact commit tested
- 353e165bf95c
- 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.
**Verification summary (all observed, this container):** - `make all` exit 0; `make install prefix=$HOME/.local` exit 0; `wikiman -v` → `2.15` - `wikiman -S` → all 6 sources `+` (man 316 pages real; arch/devdocs/fbsd/gentoo/tldr from schema-c… - `wikiman -R -s man -q intro` → 9 rows of real man pages (exit 0) - `wikiman -R -q grep` → tldr row (exit 0), `-R -q pacman` → arch row, `-R -s devdocs -q '=python p… - Interactive TUI: fzf menu displayed, Enter opened `intro(8)` man page, clean alt-screen exit, pro… - `-h`, `-W bash/zsh` all exit 0 **Errors hit and fixed:** 1. Container missing `man-db` (real `man` was a stub), plus all runtime deps (`fzf`, `rg`, `w3m`, `… 2. `RH`-line: user install needed `~/.local/share` and `~/.local/bin` symlinks because the installe… 3. Source modules didn't find data because the tldr/arch/etc. layouts I first created were wrong; f… 4. **Code fix committed to repo**: `wikiman.sh`'s awk probe now prefers `gawk` when both `gawk` and…
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 14 minutes.
- 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 2 times, so the result is not a one-off.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
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.03 | |
| Argusic Runner | 1/3 | Runs | 100.00 | 0.28 |
Topics (from GitHub)
arch-wikiclidevdocsdocumentationfreebsdgentoo-wikilinuxman-pagesofflinesearch-engineterminal-basedtldr-pagestui
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/wikiman)Questions
- Does wikiman run?
- Yes. wikiman runs. Argusic installed and launched it on a clean machine in 14 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test wikiman?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 353e165bf95c. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test wikiman?
- The run that produced this verdict cost $0.28: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does wikiman take to install?
- 14 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 wikiman need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing wikiman?
- 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.
- Where is the evidence for wikiman?
- 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.