ladybird
Truly independent web browser
Runssource: GitHubC++BSD-2-Clausecommit a71cffae5ad9
C++, BSD-2-Clause licensed. The project labels itself: browser and browser engine.
ladybird runs. An Argusic agent installed it in 6 minutes and hit 3 errors on a clean machine with no GPU, and the whole session was recorded.
Rust workspace builds and all 1731 tests pass across 24 crates; 59 Python meta tests pass; C++ browser cannot be built due to missing system prerequisites (CMake 3.30+, Qt 6.10+, libedit).
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 93.3 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page. 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.
- Full C++/CMake build requires CMake 3.30+, Qt 6.10+, libedit, ninja, and other dependencies not available without root2 minutes
- Rust toolchain not installed1 minute
- Python meta tests required LADYBIRD_SOURCE_DIR env var
- Install time
- 6 minutes
- Cold machine to finish
- 8 minutes
- Errors hit and fixed
- 3 hit, 2 fixed with no human help
- How the result was proved
- cargo test --workspace: 1731 passed, 0 failed; python3 Tests/Meta/test-*.py: 59 tests total, all OK
- Model tokens used
- 48,891
- Exact commit tested
- a71cffae5ad9
- 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.
- test-css-grammar-parser: 31 OK - test-ipc-generator: 9 OK - test-lint-environment: 5 OK - test-js-runner: 12 OK - test-xctrace-time-profile: 2 OK - test_capture (StyleUpdateCapture): 12 OK **What didn't work (no fix possible without root):** - Full C++/CMake build: CMake 3.28 < required 3.30, Qt 6.4 < required 6.10, missing libedit, missin… - The Ladybird desktop application could not be built or launched **Errors fixed:** 1. Rust not installed → installed via rustup 2. Python tests failing with `LADYBIRD_SOURCE_DIR` missing → set env var to `/work/repo`
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 6 minutes, faster than the median of the 5 comparable projects Argusic has measured.
- Ran without a GPU, so it does not need one to start.
- Licensed BSD-2-Clause, as reported by its host.
What did not, or is not known
- Hit 3 errors during setup, 1 of which were not solved.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 6 browser projects Argusic has installed and timed, ladybird was the 3rd 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.
- A quick evaluation: it was running 6 minutes after the clone.
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/ladybird)Questions
- Does ladybird run?
- Yes. ladybird runs. Argusic installed and launched it on a clean machine in 6 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test ladybird?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit a71cffae5ad9. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test ladybird?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does ladybird take to install?
- 6 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 ladybird need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing ladybird?
- 3 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does ladybird compare with the alternatives?
- Of the 6 browser projects Argusic has installed and timed, ladybird was the 3rd fastest to reach a running state, and 5 of 6 reached one at all.
- Where is the evidence for ladybird?
- 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.