mm-wiki
MM-Wiki 一个轻量级的企业知识分享与团队协同软件，可用于快速构建企业 Wiki 和团队知识分享平台。部署方便，使用简单，帮助团队构建一个信息共享、文档管理的协作环境。
Runs with mockssource: GitHubGoMITcommit d976d0c60484
Go, MIT licensed. The project labels itself: api docs, confluence, docs, document management, documentation, documents, documentserver and dokuwiki.
mm-wiki runs, with stand-ins for the services it depends on. An Argusic agent installed it in 15 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
MM-Wiki v0.2.2 is running at http://0.0.0.0:8081 with MariaDB 10.11 backend, accepting login as admin/123456 and serving the authenticated dashboard.
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 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.
- MariaDB not installed in container5 minutes
- Database schema not set up3 minutes
- Go not installed in container2 minutes
- 2 pre-existing test failures in app/utils (zipx_test.go use hardcoded developer paths)
- Install time
- 15 minutes
- Cold machine to finish
- 46 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- curl http://127.0.0.1:8081/author/index returned HTTP 200 with full login HTML page; curl -X POST -d 'username=admin&password=123456' http://127.0.0.1:8081/author/login returned {"code":1,"message":"登录成功！"} with Set-Cookie; curl -b cookies http://127.0.0.1:8081/main/index returned HTTP 200 with authenticated dashboard HTML
- Model tokens used
- 4,531,743
- Exact commit tested
- d976d0c60484
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
? github.com/phachon/mm-wiki/tools [no test files] FAIL exec /bin/sh -lc 'ps aux | grep mm-wiki | grep -v grep | head -5' in /work/repo succeeded in 0ms: runner 6879 0.2 0.0 1834584 36264 ? Ssl 20:00 0:00 ./mm-wiki --conf conf/mm-wiki.co… I have everything I need for the final report. 2026-09-30T20:01:26.355332Z ERROR codex_core::session: failed to record rollout items: thread 01a0f… 2026-09-30T20:01:26.355383Z ERROR codex_core::session: failed to record rollout items: thread 01a0f… tokens used 4,531,743 I have everything I need for the final report.
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
- Installed in 15 minutes.
- Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
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 | 1/3 | Runs with mocks | 92.00 | 0.48 |
Topics (from GitHub)
api-docsconfluencedocsdocument-managementdocumentationdocumentsdocumentserverdokuwikiwiki
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/mm-wiki)Questions
- Does mm-wiki run?
- mm-wiki runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 15 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test mm-wiki?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit d976d0c60484. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test mm-wiki?
- The run that produced this verdict cost $0.48: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does mm-wiki take to install?
- 15 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 mm-wiki need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing mm-wiki?
- 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 mm-wiki?
- 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.