nanoc
A powerful web publishing system
Runssource: GitHubhomepageRubyMITcommit 10191952d081
Ruby, MIT licensed. The project labels itself: nanoc, ruby and static site generator.
nanoc runs. An Argusic agent installed it in 41 minutes and hit 9 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Nanoc 4.14.8 loads and its core test suite (59 tests across base/ and orig_cli/) passes with 0 failures and 0 errors after installing Ruby 3.2 via extracted Ubuntu debs, setting up dev headers and linker symlinks, providing a libyaml shared library, and creating an assert shim for the rbtree native extension.
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.
- Several plugin native extensions fail to compile (psych, eventmachine, mini_racer)10 minutes
- No Ruby runtime in container5 minutes
- Ruby headers not found (mkmf.rb can't find ruby.h)4 minutes
- rbtree native extension has undefined assert symbol4 minutes
- RubyGems not in LOAD_PATH by default3 minutes
- Bundle install with full Gemfile fails on native ext compilation3 minutes
- Install time
- 41 minutes
- Cold machine to finish
- 44 minutes
- Errors hit and fixed
- 9 hit, 9 fixed with no human help
- How the result was proved
- BUNDLE_GEMFILE=Gemfile.minimal2 ruby -I test -e ... Dir['test/base/**/test_*.rb', 'test/orig_cli/**/test_*.rb'] => 59 runs, 153 assertions, 0 failures, 0 errors, 0 skips
- Model tokens used
- 251,984
- Exact commit tested
- 10191952d081
- 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.
Dir['test/base/**/test_*.rb'].each { |f| require File.expand_path(f) }
Dir['test/orig_cli/**/test_*.rb'].each { |f| require File.expand_path(f) }
\" --verbose 2>&1 | grep -E \"Finished|runs,.*assertions\"" in /work/repo
succeeded in 3597ms:
Finished in 2.592373s, 22.7591 runs/s, 59.0193 assertions/s.
59 runs, 153 assertions, 0 failures, 0 errors, 0 skips
All systems verified. Here's the final report:
2026-10-04T14:00:06.941215Z ERROR codex_core::session: failed to record rollout items: thread 01a10…
2026-10-04T14:00:06.941431Z ERROR codex_core::session: failed to record rollout items: thread 01a10…
tokens used
251,984
All systems verified. Here's 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.
- Installed in 41 minutes.
- Recovered from all 9 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.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
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/nanoc)Questions
- Does nanoc run?
- Yes. nanoc runs. Argusic installed and launched it on a clean machine in 41 minutes, hitting 9 errors on the way, and recorded the session.
- How did Argusic test nanoc?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 10191952d081. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test nanoc?
- The run that produced this verdict cost $0.56: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does nanoc take to install?
- 41 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 nanoc need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing nanoc?
- 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 nanoc?
- 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.