warewoolf
A minimalist novel-writing system/rich text editor designed to be usable without a mouse. For desktop and standalone word processors/digital typewriters/writerDecks.
Runs with mockssource: GitHubhomepageJavaScriptMITcommit 5821afcf9c9b
JavaScript, MIT licensed. The project labels itself: docx, editor, fiction, markdown, novel writing, quill, rich text editor and screenwriting.
warewoolf runs, with stand-ins for the services it depends on. An Argusic agent installed it in 28 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
npm install completes, esbuild bundles compile, 1318/1318 tests pass, and the Electron app window creates and stays alive on Xvfb display :99 until killed by timeout
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.
- epub.js uses bare crypto global which is undefined in Node 18 test runner3 minutes
- hardenDownloadedUpdate sets chmod 0500 on directory preventing test cleanup3 minutes
- Test runner glob pattern not expanded in Node 182 minutes
- MockTimers API expects array, not object, in Node 182 minutes
- jsdom 29.x requires ESM-only dependency @exodus/bytes incompatible with Node 182 minutes
- Electron 44 binary download fails in Node 18 (ESM @electron/get)2 minutes
- Install time
- 28 minutes
- Cold machine to finish
- 38 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- node --test test/*.test.js exited with 0, 1318 passed, 0 failed; npm run build compiles renderer and preload bundles without errors; npx electron --no-sandbox --in-process-gpu --disable-gpu-sandbox --version prints v28.3.3; npx electron . stays alive for 20s timeout (killed by SIGTERM, not a crash), confirming the main process loop and window creation succeed
- Model tokens used
- 459,752
- Exact commit tested
- 5821afcf9c9b
- 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.
# duration_ms 28646.272394 exec /bin/sh -lc 'cd /work/repo && timeout 20 npx electron --no-sandbox --in-process-gpu --disable-gpu-s… succeeded in 19889ms: [19151:0920/015341.165975:ERROR:command_buffer_proxy_impl.cc(127)] ContextResult::kTransientFailure… [19160:0920/015341.224922:ERROR:command_buffer_proxy_impl.cc(127)] ContextResult::kTransientFailure… /work/repo/node_modules/electron/dist/electron exited with signal SIGTERM EXIT: 0 All 1318 tests pass, the bundles build, and the app launches. Let me generate the final summary. tokens used 459,752 All 1318 tests pass, the bundles build, and the app launches. Let me generate the final summary.
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 28 minutes.
- Recovered from all 6 errors without a human stepping in, which says the failures are documented well enough to solve.
- 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
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
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.17 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.14 |
Topics (from GitHub)
docxeditorfictionmarkdownnovel-writingquillrich-text-editorscreenwritingscreenwriting-apptext-editorword-processorwriterdeckwriting-software
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/warewoolf)Questions
- Does warewoolf run?
- warewoolf runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 28 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test warewoolf?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 5821afcf9c9b. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test warewoolf?
- 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 warewoolf take to install?
- 28 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 warewoolf need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing warewoolf?
- 6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for warewoolf?
- 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.