http-kit
Simple, high-performance event-driven HTTP client+server for Clojure
Runssource: GitHubhomepageJavaApache-2.0commit 7f8c70159ca1
Java, Apache-2.0 licensed. The project labels itself: async, clojure, http client, http server and websockets.
http-kit runs. An Argusic agent installed it in 28 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
http-kit 2.9.0-beta4 compiles Java sources (141 files), resolves all Clojure dependencies, and passes 138/139 tests (the sole excluded test (test-ipv6) fails only because IPv6 is unavailable in this container).
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.
- project.clj plugins (lein-pprint, lein-ancient, lein-codox) and nrepl profile plugins (cider-nrepl, enrich-classpath) could not be resolved from any Maven repository10 minutes
- Java cacerts symlink pointed to missing /etc/ssl/certs/java/cacerts; Java.security file symlinks pointed to missing /etc/java-17-openjdk/8 minutes
- No Java JDK or JRE installed in container6 minutes
- Leiningen not installed2 minutes
- IPv6 test fails (test-ipv6): protocol family unavailable in container2 minutes
- Install time
- 28 minutes
- Cold machine to finish
- 24 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- lein with-profile +dev test :ci exited 0, Ran 138 tests containing 7238 assertions, zero failures
- Model tokens used
- 193,508
- Exact commit tested
- 7f8c70159ca1
- 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.
- Fixed broken Java security config (dangling symlinks for `java.security`, `cacerts`, etc.) - Created a proper JKS trust store with all 121 system CA certificates imported - Installed Leiningen 2.12.0 **Build fixes (`project.clj`)** - Removed unresolvable lein plugins (`lein-pprint`, `lein-ancient`, `lein-codox`) from `:dev` profi… - Removed unresolvable nrepl plugins (`cider-nrepl`, `enrich-classpath`) and the `:nrepl` profile - Updated `start-dev` alias to drop the `+nrepl` profile reference **Verification** - Java compiled: 141 source files in `src/java/` → `target/classes/` - CI test suite: `lein with-profile +dev test :ci` → 138 tests, 7238 assertions, 0 failures - Only excluded test: `test-ipv6` (IPv6 unavailable in container — `:ci` selector correctly omits i… </details>
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.
- Recovered from all 5 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 Apache-2.0, as reported by its host.
What did not, or is not known
- Took 28 minutes to install, slower than the median of the 3 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 4 async projects Argusic has installed and timed, http-kit was the 4th fastest to reach a running state, and 4 of 4 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.
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)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/http-kit)Questions
- Does http-kit run?
- Yes. http-kit runs. Argusic installed and launched it on a clean machine in 28 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test http-kit?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 7f8c70159ca1. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test http-kit?
- The run that produced this verdict cost $0.16: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does http-kit take to install?
- 28 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 http-kit need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing http-kit?
- 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.
- How does http-kit compare with the alternatives?
- Of the 4 async projects Argusic has installed and timed, http-kit was the 4th fastest to reach a running state, and 4 of 4 reached one at all.
- Where is the evidence for http-kit?
- 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.