async-http-client
Asynchronous, non-blocking HTTP & WebSocket client for the JVM
Runssource: GitHubJavaApache-2.0commit b95ca65cc97b
Java, Apache-2.0 licensed. The project labels itself: ahc, async, asynchttpclient, http client, java and netty.
async-http-client runs. An Argusic agent installed it in 10 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
On JDK 11 (Temurin 11.0.33), `./mvnw clean verify` builds and passes 1791 tests with 0 failures, and a Java program compiled against the built jar successfully fetched a page from a local HTTP server, printing STATUS=200 and BODY=hello from local 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.
- maven-gpg-plugin failed in verify phase: Cannot run program "gpg" (No such file or directory), no signer available5 minutes
- No JDK installed (java: not found); mvnw could not run4 minutes
- Install time
- 10 minutes
- Cold machine to finish
- 11 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- ./mvnw -B -ntp clean verify exited 0 with BUILD SUCCESS, 1791 tests, 0 failures, 0 errors, 22 skipped; java demo compiled against async-http-client-3.0.15-SNAPSHOT.jar and Maven classpath fetched http://127.0.0.1:18081/test and printed STATUS=200, BODY=hello from local server
- Model tokens used
- 254,207
- Exact commit tested
- b95ca65cc97b
- 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.
All verification complete. The end-to-end test passed: the demo client compiled against the built j… Summary of what happened in this container: - **Error 1 (fixed):** no JDK present (`java: not found`). Fixed by downloading Temurin JDK 11.0.33… - **Error 2 (fixed):** `./mvnw clean verify` failed on the `maven-gpg-plugin` because the `gpg` bin… - **Verification:** `./mvnw -B -ntp clean verify` on JDK 11 finished `BUILD SUCCESS` in ~5:38; sure… tokens used 254,207 All verification complete. The end-to-end test passed: the demo client compiled against the built j… Summary of what happened in this container: - **Error 1 (fixed):** no JDK present (`java: not found`). Fixed by downloading Temurin JDK 11.0.33… - **Error 2 (fixed):** `./mvnw clean verify` failed on the `maven-gpg-plugin` because the `gpg` bin… - **Verification:** `./mvnw -B -ntp clean verify` on JDK 11 finished `BUILD SUCCESS` in ~5:38; sure…
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 10 minutes.
- Recovered from all 2 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.
- Measured 2 times, so the result is not a one-off.
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 10 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)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/async-http-client)Questions
- Does async-http-client run?
- Yes. async-http-client runs. Argusic installed and launched it on a clean machine in 10 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test async-http-client?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit b95ca65cc97b. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test async-http-client?
- 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 async-http-client take to install?
- 10 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 async-http-client need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing async-http-client?
- 2 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.
- Where is the evidence for async-http-client?
- 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.