vscode-restclient
REST Client Extension for Visual Studio Code
Could not verifysource: GitHubhomepageTypeScriptMITcommit 0773d56b65d9
TypeScript, MIT licensed. The project labels itself: graphql, http, http client, rest, rest api, rest client, typescript and visual studio code.
Argusic could not get vscode-restclient running. An Argusic agent installed it in 10 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
REST Client VSCode extension installs dependencies, type-checks via tslint with zero errors, and builds successfully in both development (14.6 MiB) and production (4.57 MiB, minified) webpack configurations; the extension requires VSCode to activate and run.
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 65 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.
- npx webpack --mode production (vscode:prepublish) repeatedly timed out after 30s due to TerserPlugin minification on large bundle5 minutes
- Install time
- 10 minutes
- Cold machine to finish
- 12 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- npm run vscode:prepublish exited 0 (production bundle at dist/extension.js, 4.57 MiB, minified); npm run tslint exited 0 (0 lint errors); npm run webpack (dev) also exited 0
- Model tokens used
- 56,042
- Exact commit tested
- 0773d56b65d9
- 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
- Whether it works at all
- this run verified nothing, so this page makes no claim either way
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
succeeded in 0ms: -rw-rw-r-- 1 runner runner 4.6M Sep 29 05:03 /work/repo/dist/extension.js exec /bin/sh -lc 'npm run tslint 2>&1; echo "EXIT: $?"' in /work/repo succeeded in 1942ms: > [email protected] tslint > tslint --project tsconfig.json EXIT: 0 All done. Let me compile the final result. tokens used 56,042 All done. Let me compile 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
- Installed in 10 minutes.
- Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
- 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
- An agent with no time limit did not get it running.
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 | 2/3 | Unverified | 80.00 | 0.05 | |
| Argusic Runner | 1/3 | Did not run | 50.00 | 0.04 |
Topics (from GitHub)
graphqlhttphttp-clientrestrest-apirest-clienttypescriptvisual-studio-codevscodevscode-extension
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/vscode-restclient)Questions
- Does vscode-restclient run?
- Argusic could not verify that vscode-restclient runs. Argusic installed and launched it on a clean machine in 10 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test vscode-restclient?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 0773d56b65d9. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test vscode-restclient?
- The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does vscode-restclient 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 vscode-restclient need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing vscode-restclient?
- 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.
- Where is the evidence for vscode-restclient?
- 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.