curlie
The power of curl, the ease of use of httpie.
Runssource: GitHubhomepageGoMITcommit 5dfcbb17ea67
Go, MIT licensed. The project labels itself: api client, cli, curl, developer tools, go, http client, httpie and terminal.
curlie runs. An Argusic agent installed it in 11 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Curlie builds with Go 1.24.0, passes all 3 unit tests, and successfully makes HTTP requests (GET, POST) to mock servers with formatted JSON output and curl command generation.
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.
- The project uses Go, not V language. Installed V compiler first by mistake.9 minutes
- Install time
- 11 minutes
- Cold machine to finish
- 12 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- go test ./... passed 3 tests (PASS, 0.016s); curlie version printed 'curlie v0.0.0-LOCAL (0000-00-00T00:00:00Z)'; GET to local mock HTTP server returned formatted JSON; POST with key=value returned echo; --curl flag printed equivalent curl command
- Model tokens used
- 265,967
- Exact commit tested
- 5dfcbb17ea67
- 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
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.
Let me produce the final result: tokens used 265,967 Everything is working. Let me compile the JSON result: - **install_succeeded**: true - Go was installed, dependencies downloaded, project built - **launch_succeeded**: true - binary runs and responds to `version` command - **errors**: Only the confusion with V language. Let me include the key moments. - **test_depth**: tier1_real - I tested with a real mock HTTP server and verified JSON output - **verified_how**: See below - **final_state**: The curlie binary builds, its tests pass (PASS, 0.016s), and the binary makes HT… Let me compute the time. I started at approximately 04:17 (based on file timestamps) and it's now 0… Let me produce 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.
- 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.
What did not, or is not known
- Took 11 minutes to install, slower than the median of the 38 comparable projects Argusic has measured.
Of the 39 api-client projects Argusic has installed and timed, curlie was the 29th fastest to reach a running state, and 24 of 39 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)
api-clientclicurldeveloper-toolsgohttp-clienthttpieterminalwebdevelopment
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/curlie)Questions
- Does curlie run?
- Yes. curlie runs. Argusic installed and launched it on a clean machine in 11 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test curlie?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 5dfcbb17ea67. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test curlie?
- The run that produced this verdict cost $0.34: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does curlie take to install?
- 11 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 curlie need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing curlie?
- 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 curlie compare with the alternatives?
- Of the 39 api-client projects Argusic has installed and timed, curlie was the 29th fastest to reach a running state, and 24 of 39 reached one at all.
- Where is the evidence for curlie?
- 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.