isahc
The practical HTTP client that is fun to use.
Runssource: GitHubhomepageRustMITcommit e373ae3ae5b8
Rust, MIT licensed. The project labels itself: http, http client, http2, https and rust.
isahc runs. An Argusic agent installed it in 1 minute and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Isahc HTTP client builds from source on Rust 1.85.1, passes 147 of 149 tests (2 IPv6 net tests skipped due to container having IPv6 disabled), and the simple example fetches real HTTPS content from example.org successfully.
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.
- 2 net tests fail: 'any_ip_version_uses_ipv4_or_ipv6' and 'ipv4_only_will_not_connect_to_ipv6' panic with 'Cannot assign requested address' when binding to Ipv6Addr::LOCALHOST5 minutes
- Install time
- 1 minutes
- Cold machine to finish
- 6 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- cargo test: 147 passed, 2 failed (IPv6 disabled env). cargo run --example simple: exited 0, fetched https://example.org, status 200, body contains 'Example Domain'.
- Model tokens used
- 173,641
- Exact commit tested
- e373ae3ae5b8
- 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 result: ok. 13 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.02s test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s test result: ok. 6 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.01s test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.01s test result: FAILED. 4 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s Good. Let me compile the final summary. The project builds and runs tests. 2 tests fail only becaus… Here is the final result: tokens used 173,641 Good. Let me compile the final summary. The project builds and runs tests. 2 tests fail only becaus… Here is the final result:
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 1 minute, faster than the median of the 8 comparable projects Argusic has measured.
- Recovered from all 1 error 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.
- Measured 2 times, so the result is not a one-off.
Of the 9 http projects Argusic has installed and timed, isahc was the 4th fastest to reach a running state, and 9 of 9 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 1 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/isahc)Questions
- Does isahc run?
- Yes. isahc runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test isahc?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit e373ae3ae5b8. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test isahc?
- The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does isahc take to install?
- 1 minute in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does isahc need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing isahc?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does isahc compare with the alternatives?
- Of the 9 http projects Argusic has installed and timed, isahc was the 4th fastest to reach a running state, and 9 of 9 reached one at all.
- Where is the evidence for isahc?
- 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.