crowi
Crowi - The Markdown Wiki - Empower the team with sharing your knowledge
Runssource: GitHubhomepageTypeScriptMITcommit c96e47fe76ab
TypeScript, MIT licensed. The project labels itself: crowi, knowledge, markdown wiki, typescript and wiki.
crowi runs. An Argusic agent installed it in 18 minutes and hit 8 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
All 24 workspace packages build successfully, the API test suite passes 232/242 suites (10 smoke tests skipped requiring Redis), and the API TypeScript compilation produces dist/app.js
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.
- mongodb-memory-server per-file startup timeout for 17 test suites (10s timeout exceeded under memory pressure)4 minutes
- pnpm install blocked build scripts for @parcel/watcher, esbuild, lefthook, mongodb-memory-server, unrs-resolver3 minutes
- System Node.js v18.19.1 does not satisfy engines.node (24.x)2 minutes
- API tsc build failed: 40+ TS2307 errors for @crowi/plugin-api, @crowi/collab, @crowi/runner, @crowi/plugin-storage-local etc.2 minutes
- pnpm not found (corepack not available on system Node 18)1 minute
- api-contract DTS build OOM (ERR_WORKER_OUT_OF_MEMORY)1 minute
- Install time
- 18 minutes
- Cold machine to finish
- 19 minutes
- Errors hit and fixed
- 8 hit, 8 fixed with no human help
- How the result was proved
- pnpm --filter @crowi/api test executed with MONGO_URI=mongodb://localhost:27018/crowi?maxPoolSize=10: 232 test suites passed, 10 skipped, 5235 tests passed, 25 skipped, 0 failures across 3 jest projects (server/common/smoke)
- Model tokens used
- 762,524
- Exact commit tested
- c96e47fe76ab
- 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.
All done. The report is above. Let me just underscore the key facts: - **Install succeeded**: pnpm install completed, all 24 workspace packages build - **Test suite passed**: 232/242 test suites passing (5235 tests), 10 skipped (Redis-dependant smok… - **Verified via real MongoDB**: started a standalone `mongod` on port 27018 and ran the full test … - **8 errors encountered and fixed**, including Node version, pnpm install, OOM builds (needed 8-12… tokens used 762,524 All done. The report is above. Let me just underscore the key facts: - **Install succeeded**: pnpm install completed, all 24 workspace packages build - **Test suite passed**: 232/242 test suites passing (5235 tests), 10 skipped (Redis-dependant smok… - **Verified via real MongoDB**: started a standalone `mongod` on port 27018 and ran the full test … - **8 errors encountered and fixed**, including Node version, pnpm install, OOM builds (needed 8-12…
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 18 minutes.
- Recovered from all 8 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
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/crowi)Questions
- Does crowi run?
- Yes. crowi runs. Argusic installed and launched it on a clean machine in 18 minutes, hitting 8 errors on the way, and recorded the session.
- How did Argusic test crowi?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit c96e47fe76ab. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test crowi?
- The run that produced this verdict cost $0.17: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does crowi take to install?
- 18 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 crowi need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing crowi?
- 8 things broke in the recorded run, and 8 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for crowi?
- 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.