znai

Build functional, maintainable, beautiful User Guides with markdown and Znai plugins. Instant pages navigation. Local search. Multiple integrations to work with Python, Java, C++, OpenAPI, etc. Transform "getting started" sections into slideshow for your workshops. Manage multiple documentations with self-deployed znai hub.

Runssource: GitHubhomepageJavaApache-2.0commit c37ae2e53eae

Java, Apache-2.0 licensed. The project labels itself: documentation, github pages, java, markdown, openapi, openapi3, python and rest api.

znai runs. An Argusic agent installed it in 37 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Znai 1.94-SNAPSHOT builds with Maven, all unit and WebTau integration tests pass (49/49 in znai-tests, 5/5 in znai-testing-examples), CLI scaffolds docs and generates HTML output, and the server serves documentation over HTTP.

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.17 (measured)
recorded runs
1
last tested
stars
280
forks
21
open issues
28
watchers
8
size
64 MB
created
last push

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.

Time lost to each failure while testing znai, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Graphviz dot not found for diagram tests5 minutes
  • Firefox not found for WebTau Selenium tests3 minutes
  • Java not found in container2 minutes
  • Maven not found in container2 minutes
  • unzip not installed and no root to install it1 minute
  • znai-tests webtau integration tests failed (Firefox missing)
Install time
37 minutes
Cold machine to finish
40 minutes
Errors hit and fixed
7 hit, 7 fixed with no human help
How the result was proved
mvn test returned BUILD SUCCESS across all modules; CLI --version printed 'version: 1.94-SNAPSHOT (2026-10-26)'; znai serve mode started and returned HTTP 200 on localhost; scaffold --new created a complete doc skeleton; build mode generated HTML pages including index.html
Model tokens used
557,203
Exact commit tested
c37ae2e53eae
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.

/bin/sh -lc 'kill %1 2>/dev/null; true
echo "=== Unit tests ==="
export JAVA_HOME=/tmp/jdk17 && PATH=/tmp/jdk17/bin:/tmp/maven/bin:/tmp/firefox:/tmp/conda/bin:$PATH…
exec
/bin/sh -lc "pkill -f 'ZnaiCliApp' 2>/dev/null; true
echo \"Final state collected.\"" in /work/repo
 exited 143 in 0ms:
All collected. Here is the final report:
2026-10-26T20:14:49.992130Z ERROR codex_core::session: failed to record rollout items: thread 01a17…
tokens used
557,203
All collected. Here is 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

  • Reached a running state on a clean machine, with the session recorded.
  • Recovered from all 7 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 Apache-2.0, as reported by its host.

What did not, or is not known

  • Took 37 minutes to install, slower than the median of the 5 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 6 documentation projects Argusic has installed and timed, znai was the 6th fastest to reach a running state, and 5 of 6 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

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.17

Topics (from GitHub)

documentationgithub-pagesjavamarkdownopenapiopenapi3pythonrest-apistatic-site-generatoruserguide

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/znai.svg)](https://argusic.com/subject/znai)

Questions

Does znai run?
Yes. znai runs. Argusic installed and launched it on a clean machine in 37 minutes, hitting 7 errors on the way, and recorded the session.
How did Argusic test znai?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit c37ae2e53eae. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test znai?
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 znai take to install?
37 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 znai need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing znai?
7 things broke in the recorded run, and 7 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does znai compare with the alternatives?
Of the 6 documentation projects Argusic has installed and timed, znai was the 6th fastest to reach a running state, and 5 of 6 reached one at all.
Where is the evidence for znai?
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.

Discussion