hugo
The world’s fastest framework for building websites.
Runssource: GitHubhomepageGoApache-2.0commit 079c76f0104d
Go, Apache-2.0 licensed. The project labels itself: blog engine, cms, content management system, documentation tool, go, hugo and static site generator.
hugo runs. An Argusic agent installed it in 0.3 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Hugo v0.167.0-DEV builds from source, all 143 test packages pass, binary produces sites and serves them via the built-in web server.
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.
- codegen test TestMethods/MethodsFromTypes panicked: dir must be set to the Hugo root8 minutes
- Install time
- under a minute
- Cold machine to finish
- 47 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- go test -p 2 ./... with HUGO_BUILD_TAGS=extended,withdeploy returned 143 ok, 0 FAIL; hugo new site created a project and hugo server on port 19996 started and responded
- Model tokens used
- 163,375
- Exact commit tested
- 079c76f0104d
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- `go test -p 2 ./...` with `HUGO_BUILD_TAGS=extended,withdeploy`: **143 ok, 0 FAIL, 49 ? (no test …
- `hugo new site` created a project
- `hugo` built a site from content
- `hugo server --port 19996` started and served HTTP (got 404 for a home page without matching temp…
No third-party API keys required, no mocks needed.
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 0…
succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 0.3, "errors": [{"msg": "c…
2026-10-31T14:05:45.183670Z ERROR codex_core::session: failed to record rollout items: thread 01a19…
tokens used
163,375Replay 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 0.3 minutes, faster than the median of the 4 comparable projects Argusic has measured.
- Recovered from all 1 error 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.
- Measured 2 times, so the result is not a one-off.
Of the 5 blog-engine projects Argusic has installed and timed, hugo was the 1st fastest to reach a running state, and 5 of 5 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.
- A quick evaluation: it was running 0.3 minutes after the clone.
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)
blog-enginecmscontent-management-systemdocumentation-toolgohugostatic-site-generator
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/hugo)Questions
- Does hugo run?
- Yes. hugo runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test hugo?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 079c76f0104d. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test hugo?
- The run that produced this verdict cost $0.38: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does hugo take to install?
- 0.3 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 hugo need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing hugo?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does hugo compare with the alternatives?
- Of the 5 blog-engine projects Argusic has installed and timed, hugo was the 1st fastest to reach a running state, and 5 of 5 reached one at all.
- Where is the evidence for hugo?
- 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.