wretch
A tiny wrapper built around fetch with an intuitive syntax. :candy:
Runssource: GitHubTypeScriptMITcommit 32d5f68badf7
TypeScript, MIT licensed. The project labels itself: ajax, fetch, formdata, http, http client, http request, javascript and json.
wretch runs. An Argusic agent installed it in 5 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
npm install and build succeed with Node 22, the mock test server starts and responds to HTTP requests, the full Node.js test suite (79/79) and browser suite (58/58 on Chromium and Firefox) pass cleanly.
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.
- Playwright browsers missing on first browser test run3 minutes
- Node.js v18 (bundled) doesn't meet the >=22 engine requirement — rolldown uses node:util.styleText which is Node 21+ only2 minutes
- Install time
- 5 minutes
- Cold machine to finish
- 5 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- npm run test:node exited 0 with 79/79 pass; npm run test:browser exited 0 with 58/58 pass on both Chromium and Firefox; npm run test:snippets exited 0 with 67/67 pass; npm run test:types exited 0 (tsc -b)
- Model tokens used
- 60,132
- Exact commit tested
- 32d5f68badf7
- 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.
=== Snippet tests === # tests 87 # pass 67 # fail 0 # skipped 20 === Type tests === > [email protected] test:types > tsc -b tsconfig.type-tests.json All tests pass comprehensively. Here's the report: tokens used 60,132 All tests pass comprehensively. Here's the report:
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 5 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 MIT, 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 5 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)
ajaxfetchformdatahttphttp-clienthttp-requestjavascriptjsonnodejspromiserequesttypescript
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/wretch)Questions
- Does wretch run?
- Yes. wretch runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test wretch?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 32d5f68badf7. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test wretch?
- The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does wretch take to install?
- 5 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 wretch need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing wretch?
- 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 wretch?
- 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.