lithium
Easy to use C++17 HTTP Server with no compromise on performances. https://matt-42.github.io/lithium
Runs with mockssource: GitHubhomepageC++MITcommit ac3fe63721b3
C++, MIT licensed. The project labels itself: api server, asynchronous, cpp, cpp library, cpp17, http client, http server and json.
lithium runs, with stand-ins for the services it depends on. An Argusic agent installed it in 18 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The project compiles from source via cmake, the li_symbol_generator binary is built and functional, all 9 single-header test binaries compile and run, and ctest passes 25 of 30 tests covering metamap, JSON, symbol, HTTP server, HTTP client, and URL handling components.
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 92 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.
- Missing development headers: curl/curl.h, boost/context/continuation.hpp, boost/convert/lexical_cast.hpp, libpq-fe.h, mysql.h, sqlite3.h5 minutes
- vcpkg bootstrap fails without zip/unzip tools (not root, cannot install)4 minutes
- Shared library symlinks for SONAMEs (libpq.so.5, libcurl.so.4, libmariadb.so.3, libsqlite3.so.0) missing from extracted .dev debs3 minutes
- Cmake FindCURL and FindPostgreSQL not setting IMPORTED_LOCATION when library paths pre-set via -D flags2 minutes
- 5 tests (crud, sql_authentication, mysql_test, pgsql_test, orm_test) fail - need running MySQL and PostgreSQL database servers1 minute
- Install time
- 18 minutes
- Cold machine to finish
- 14 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- cd /work/repo/build_boost && LD_LIBRARY_PATH=/tmp/headers_extracted/usr/lib/x86_64-linux-gnu ctest --output-on-failure returned 83% tests passed, 25/30 passed
- Model tokens used
- 210,289
- Exact commit tested
- ac3fe63721b3
- 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
- Behaviour against real services
- this run was verified against stand-in services only
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.
echo "install.sh (li_symbol_generator + headers): runs via git clone + compile" echo "CMake + build + test: ~2 min for full cycle"' in /work/repo succeeded in 0ms: Install times: install.sh (li_symbol_generator + headers): runs via git clone + compile CMake + build + test: ~2 min for full cycle Now I have everything needed. Let me produce the final report. 2026-11-15T13:30:36.707791Z ERROR codex_core::session: failed to record rollout items: thread 01a1d… 2026-11-15T13:30:36.707823Z ERROR codex_core::session: failed to record rollout items: thread 01a1d… tokens used 210,289 Now I have everything needed. Let me produce 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
- Installed in 18 minutes.
- Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.21 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.16 |
Topics (from GitHub)
api-serverasynchronouscppcpp-librarycpp17http-clienthttp-serverjsonmysqlmysql-serverobject-relational-mapperormpostgresqlsql-driversqlite3webframeworkwebprogramming
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/lithium)Questions
- Does lithium run?
- lithium runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 18 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test lithium?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit ac3fe63721b3. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test lithium?
- The run that produced this verdict cost $0.21: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does lithium take to install?
- 18 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 lithium need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing lithium?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for lithium?
- 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.