noodle
A REST Client where the Repository is the Workspace
Runssource: GitHubhomepageTypeScriptApache-2.0commit 384caefa8ea3
TypeScript, Apache-2.0 licensed. The project labels itself: ai agents, ai skills, ai tools, api client, cli, developer tools, devtools and http.
noodle runs. An Argusic agent installed it in 29 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Bun 1.4.3 is installed, all 137 dependencies resolved, the full test suite (3617 pass, 3 skip, 0 fail), typecheck, and lint all pass, and real HTTP requests via the CLI produce 200 responses with full bodies against external APIs.
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.
- test CollectionRunnerView > completes home and collection data paths: completion never appears because collapseUserPath returns absolute path unchanged when repo is outside $HOME3 minutes
- bun: not found — bun binary not pre-installed2 minutes
- unzip: not found — official bun.sh install script failed1 minute
- Install time
- 29 minutes
- Cold machine to finish
- 9 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- bun test exited 0, 3617 passed; bun run src/app/cli.ts request run headers-inspect --collection ./collections --env staging --json returned status 200 with full httpbin response; bun run src/app/cli.ts collection run ./collections posts/get-posts --env staging --json returned status 200
- Model tokens used
- 286,908
- Exact commit tested
- 384caefa8ea3
- 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.
**Install**: Bun 1.4.3 manually installed (official bun.sh installer was unavailable since `unzip` … **Test suite**: `bun test` → 3617 passed, 3 skipped (macOS signing), 0 failed. One test `Collection… **CLI verification**: Help printed correctly. `collection list --json` returned full tree. `request… **Typecheck & lint**: Both clean. tokens used 286,908 All good. Clean lint output (no errors). Now let me compose the final report. Here's the summary of what was done and observed: **Install**: Bun 1.4.3 manually installed (official bun.sh installer was unavailable since `unzip` … **Test suite**: `bun test` → 3617 passed, 3 skipped (macOS signing), 0 failed. One test `Collection… **CLI verification**: Help printed correctly. `collection list --json` returned full tree. `request… **Typecheck & lint**: Both clean.
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 3 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 Apache-2.0, as reported by its host.
What did not, or is not known
- Took 29 minutes to install, slower than the median of the 123 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 124 ai-agents projects Argusic has installed and timed, noodle was the 114th fastest to reach a running state, and 96 of 124 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)
ai-agentsai-skillsai-toolsapi-clientclideveloper-toolsdevtoolshttprestrest-apirest-clientskillsterminalterminal-uitui
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/noodle)Questions
- Does noodle run?
- Yes. noodle runs. Argusic installed and launched it on a clean machine in 29 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test noodle?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 384caefa8ea3. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test noodle?
- The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does noodle take to install?
- 29 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 noodle need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing noodle?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does noodle compare with the alternatives?
- Of the 124 ai-agents projects Argusic has installed and timed, noodle was the 114th fastest to reach a running state, and 96 of 124 reached one at all.
- Where is the evidence for noodle?
- 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.