docs
Docs is an open-source text editor: web-native, made for real-time collaboration, cleanly structured documents and sub-documents with full ownership of your data. Built to scale with Django and React.
Runs with mockssource: GitHubhomepagePythonMITcommit 5b24290923e5
Python, MIT licensed. The project labels itself: blocknotejs, collaborative, django, documentation, g2g, government, knowledge and knowledge base.
docs runs, with stand-ins for the services it depends on. An Argusic agent installed it in 54 minutes and hit 9 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The Docs backend project installs, builds, and runs 2190+ test cases successfully using mock PostgreSQL, MinIO S3, and compiled email/translation assets, with the only unaddressed failures requiring a real OIDC provider.
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 86 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.
- PostgreSQL not installed in container5 minutes
- libmagic (python-magic dependency) not found3 minutes
- S3 credentials required for MinIO (Default storage uses S3)3 minutes
- Syntax errors: 6 files used 'except E1, E2:' (Python 3.11+ requirement) which fails in Python 3.122 minutes
- No Redis available for cache/celery2 minutes
- Email templates missing (MJML not compiled)2 minutes
- Install time
- 54 minutes
- Cold machine to finish
- 62 minutes
- Errors hit and fixed
- 9 hit, 9 fixed with no human help
- Model tokens used
- 306,520
- Exact commit tested
- 5b24290923e5
- 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.
- How the result was proved
- runs before 2026-09-07 did not record the command used to check the result
- 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.
npm audit fix Run `npm audit` for details. Started around 21:20, current time 22:14 - about 54 minutes. Well within the 90 minute budget. Let me now produce the final report with all the data I've collected. Let me also note the changes … Actually, let me just compile the results and produce the JSON. 2026-09-05T22:15:11.156650Z ERROR codex_core::session: failed to record rollout items: thread 01a07… 2026-09-05T22:15:11.156709Z ERROR codex_core::session: failed to record rollout items: thread 01a07… tokens used 306,520 Started around 21:20, current time 22:14 - about 54 minutes. Well within the 90 minute budget. Let me now produce the final report with all the data I've collected. Let me also note the changes … Actually, let me just compile the results and produce the JSON.
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 54 minutes.
- Recovered from all 9 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
- Measured 3 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.33 | |
| Argusic Runner | 1/3 | Unverified | 80.00 | 0.72 | |
| Argusic Runner | 1/3 | Ran out of time | 0.00 | 0.25 |
Topics (from GitHub)
blocknotejscollaborativedjangodocumentationg2ggovernmentknowledgeknowledge-basemitmit-licenseopensourcereactjsrealtime-collaborationself-hostedwikiyjs
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/docs)Questions
- Does docs run?
- docs runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 54 minutes, hitting 9 errors on the way, and recorded the session.
- How did Argusic test docs?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 5b24290923e5. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test docs?
- The run that produced this verdict cost $0.33: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does docs take to install?
- 54 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 docs need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing docs?
- 9 things broke in the recorded run, and 9 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for docs?
- All 3 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.