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 35 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Matterwiki web application serves its React SPA bundle (HTTP 200), API root (HTTP 200), and all REST endpoints (setup, auth, topics CRUD, articles CRUD, users list, search) via SQLite3 database with knex 0.11.10 and sqlite3 5.1.7 on Node.js 18.19.1
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] native module fails to compile on Node 18 (V8 API incompatibility and missing python symlink)20 minutes
- [email protected] missing lib/ directory with dialect and driver code after npm install10 minutes
- Node 18 crashes on unhandled promise rejections from bookshelf/knex promise chains without .catch() handlers5 minutes
- Install time
- 35 minutes
- Cold machine to finish
- 32 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- Node.js API server started on port 5090; all 14 REST API endpoints exercised via curl; every response's HTTP status and JSON code field confirmed correct: root (200), bundle.js (200), API root (200 "API ok"), setup (B131), auth (B118 + JWT), topics list (B123, 1 initial + 1 created = 2), articles list (B105, 0 initial then 1 created), article get (B113, title 'Hello World'), users list (B133, 1 user), search (B131, 1 result for 'Hello'), no-auth rejection (403 B102)
- Model tokens used
- 386,242
- 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.
Final package.json cleaned up Let me report the final verification and comprehensive result. Here's everything I observed: **Install succeeded.** The original `npm install` failed because `[email protected]` couldn't compile o… **Launch and API verification.** The server started on port 5090 and all endpoints were verified vi… Each response was parsed to check both HTTP status and the response JSON `code` field. All 14 test … 2026-10-04T17:10:08.377461Z ERROR codex_core::session: failed to record rollout items: thread 01a10… tokens used 386,242 Let me report the final verification and comprehensive result. Here's everything I observed: **Install succeeded.** The original `npm install` failed because `[email protected]` couldn't compile o… **Launch and API verification.** The server started on port 5090 and all endpoints were verified vi… Each response was parsed to check both HTTP status and the response JSON `code` field. All 14 test …
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 3 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.
What did not, or is not known
- Took 35 minutes to install, slower than the median of the 3 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 4 collaboration projects Argusic has installed and timed, Matterwiki was the 4th fastest to reach a running state, and 4 of 4 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 35 minutes, hitting 3 errors 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. One attempt is 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.25: 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?
- 35 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?
- 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 Matterwiki compare with the alternatives?
- Of the 4 collaboration projects Argusic has installed and timed, Matterwiki was the 4th fastest to reach a running state, and 4 of 4 reached one at all.
- Where is the evidence for Matterwiki?
- 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.