bridgetown
A next-generation progressive site generator & fullstack framework, powered by Ruby
Runssource: GitHubhomepageRubyMITcommit 250d6efe2b01
Ruby, MIT licensed. The project labels itself: blog engine, bridgetown, documentation tool, esbuild, jamstack, ruby and static site generator.
bridgetown runs. An Argusic agent installed it in 15.1 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Bridgetown 2.2.2 monorepo builds and passes its full test suite (bridgetown-core: 1000 tests, bridgetown-foundation: 41 tests, bridgetown-builder: 39 tests, bridgetown-routes: 13 tests, all 0 failures and 0 errors) with Ruby 3.3.11 built from source, using locally-built zlib and libyaml libraries.
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.
- Ruby not found in container (no ruby binary available)
- zlib extension missing in ruby build (libz dev headers not installed)
- psych extension missing (libyaml not available)
- bundle install failed because psych 5.2.6 gem native extension build failed
- Install time
- 15 minutes
- Cold machine to finish
- 16 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- bundle exec rake ran full test suite: bridgetown-core 1000 tests passed (49+15+936), bridgetown-foundation 41 passed, bridgetown-builder 39 passed, bridgetown-routes 13 passed, all 0 failures, 0 errors
- Model tokens used
- 67,465
- Exact commit tested
- 250d6efe2b01
- 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.
export PATH="/home/runner/ruby-install/bin:$PATH" && export LD_LIBRARY_PATH="/home/runner/zlib/lib:… exec /bin/sh -lc 'echo "Start time: $(date -d '"'2026-10-08T10:19:00Z' +%s)\" echo \"End time: "'$(date -d '"'2026-10-08T10:34:03Z' +%s)\" echo \"Diff: "'$(( $(date -d '"'2026-10-08T10:34:03Z' +%s) - "'$(date -d '"'2026-10-08T10:19:00Z' +… succeeded in 0ms: Start time: 1791454740 End time: 1791455643 Diff: 903 seconds 2026-10-08T10:35:27.933169Z ERROR codex_core::session: failed to record rollout items: thread 01a11… tokens used 67,465
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 15.1 minutes.
- Recovered from all 4 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.
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-enginebridgetowndocumentation-toolesbuildjamstackrubystatic-site-generator
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/bridgetown)Questions
- Does bridgetown run?
- Yes. bridgetown runs. Argusic installed and launched it on a clean machine in 15 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test bridgetown?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 250d6efe2b01. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test bridgetown?
- The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does bridgetown take to install?
- 15.1 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 bridgetown need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing bridgetown?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for bridgetown?
- 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.