jquick-curl
jquick‑curl: Java library to run raw curl commands, support copy‑paste curl from Postman/Apifox/Browser DevTools, no need to write HTTP client code.
Runs with mockssource: GitHubJavaApache-2.0commit 35f8d038bf17
Java, Apache-2.0 licensed. The project labels itself: antlr4, copy paste, curl, curl parser, dromara, http client, java and okhttp.
jquick-curl runs, with stand-ins for the services it depends on. An Argusic agent installed it in 9 minutes and hit 8 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
A clean Maven install succeeds, all 33 tests pass with the in-test mock, and a separate consumer using the installed jquick-curl 2.8.0 jar receives HTTP 200 with the expected Ada Lovelace JSON.
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. 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.
- Initial mvn test ran 33 tests with 22 errors: 21 null responses from the missing localhost:8080 API and one 'Expected URL scheme ... userId' parser failure.4 minutes
- No java, javac, or mvn was installed, so the documented Maven build could not start.3 minutes
- Multipart upload tests failed because fixtures used nonexistent Windows paths D:\test, and downloads wrote to d:/test.3 minutes
- JCurlCommandProcessorTest failed with 'java.lang.IllegalArgumentException: timeout too large' in OkHttp.3 minutes
- Processor and direct visitor tests threw ClassCastException casting JQuickCurlResponseBody to JResult.2 minutes
- mvn clean install failed at maven-gpg-plugin because gpg was not installed.2 minutes
- Install time
- 9 minutes
- Cold machine to finish
- 8 minutes
- Errors hit and fixed
- 8 hit, 8 fixed with no human help
- How the result was proved
- After confirming port 8080 was closed, mvn clean test exited 0 with 33 tests, 0 failures, 0 errors, 0 skipped; mvn clean install exited 0 and installed jquick-curl 2.8.0; a separate consumer compiled against that installed artifact and exited 0, printing DIRECT_STATUS_BODY={"id": 1, "name": "Ada Lovelace", "email": "[email protected]"}.
- Model tokens used
- 454,048
- Exact commit tested
- 35f8d038bf17
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
?? src/test/java/com/github/paohaijiao/test/MockApiServer.java ?? src/test/resources/ ?? target/ -- fixture contents -- src/test/resources/fixtures/test.txt: jquick-curl upload fixture src/test/resources/fixtures/test1.txt: jquick-curl second upload fixture exec /usr/bin/bash -c "rg -n 'target/|\\.m2|toolchains' .gitignore; du -sh target 2>/dev/null; ls -lh ta… succeeded in 0ms: 1.4M target tokens used 454,048
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 9 minutes.
- Recovered from all 8 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, as reported by its host.
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.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
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 | 1/3 | Runs with mocks | 92.00 | 0.26 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/jquick-curl)Questions
- Does jquick-curl run?
- jquick-curl runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 9 minutes, hitting 8 errors on the way, and recorded the session.
- How did Argusic test jquick-curl?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 35f8d038bf17. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test jquick-curl?
- The run that produced this verdict cost $0.26: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does jquick-curl take to install?
- 9 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 jquick-curl need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing jquick-curl?
- 8 things broke in the recorded run, and 8 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for jquick-curl?
- 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.