Matterwiki
A simple and beautiful wiki for teams
Runssource: GitHubhomepageJavaScriptMITcommit 92ca38c89719
JavaScript, MIT licensed. The project labels itself: collaboration, javascript, knowledgebase, matterwiki, node, react, wiki and wiki engine.
Matterwiki runs. An Argusic agent installed it in 13 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Matterwiki runs on Node 18 with webpack-built frontend (bundle.js), Sqlite3 database, JWT authentication, and all API endpoints (articles, topics, users, search, archives, setup, admin) are operational.
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.
- [email protected] failed to compile from source on Node 18 — missing prebuilt binary and 'python' command not found8 minutes
- Install time
- 13 minutes
- Cold machine to finish
- 13 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- Server started on port 5003; POST /setup returned 200 with admin user; POST /api/authenticate returned JWT; GET /api/articles, POST /api/articles, GET /api/topics, GET /api/users all returned 200 with correct data
- Model tokens used
- 512,046
- Exact commit tested
- 92ca38c89719
- 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.
Here's the summary of everything I did and found: **Matterwiki** — a simple Node.js/React wiki app with Sqlite3. **Errors encountered and fixes applied:** 1. **[email protected] native compilation failed** — The pinned `[email protected]` had no prebuilt binary … 2. **Setup endpoint fails with NOT NULL constraint** — `about` field is `notNullable` in the migrat… **Verification performed:** - `npm install` succeeded (877 packages), `npm run build` succeeded (bundle.js 313kB) - Server starts on configurable port and answers on `/api/` - `POST /setup` creates admin user and default topic - `POST /api/authenticate` returns JWT - Authenticated endpoints work: `GET /api/articles`, `GET /api/topics`, `GET /api/users`, `POST /ap… - Database migrations run automatically on startup with Sqlite3
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 1 error 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 did not, or is not known
- Took 13 minutes to install, slower than the median of the 4 comparable projects Argusic has measured.
Of the 5 collaboration projects Argusic has installed and timed, Matterwiki was the 4th fastest to reach a running state, and 5 of 5 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.
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)
collaborationjavascriptknowledgebasematterwikinodereactwikiwiki-engine
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/matterwiki)Questions
- Does Matterwiki run?
- Yes. Matterwiki runs. Argusic installed and launched it on a clean machine in 13 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test Matterwiki?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 92ca38c89719. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test Matterwiki?
- The run that produced this verdict cost $0.18: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does Matterwiki take to install?
- 13 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 Matterwiki need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Matterwiki?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does Matterwiki compare with the alternatives?
- Of the 5 collaboration projects Argusic has installed and timed, Matterwiki was the 4th fastest to reach a running state, and 5 of 5 reached one at all.
- Where is the evidence for Matterwiki?
- 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.