yaak

The most intuitive desktop API client. Organize and execute REST, GraphQL, WebSockets, Server Sent Events, and gRPC 🦬

Runssource: GitHubhomepageRustMITcommit 7f3025361685

Rust, MIT licensed. The project labels itself: bruno alternative, graphql, grpc, http, http client, insomnia alternative, postman alternative and sse.

yaak runs. An Argusic agent installed it in 7 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

npm 551 tests pass, Rust 179 tests pass, yaak-web serve binary and yaak CLI binary both build and run, web app dist builds successfully, Tauri desktop GUI skipped due to missing webkit2gtk-4.0 system package

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.09 (measured)
recorded runs
2
last tested
stars
19,498
forks
859
open issues
23
watchers
41
size
53 MB
created
last push

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.

Time lost to each failure while testing yaak, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • libdbus-sys build failed: missing dbus-1.pc for pkg-config2 minutes
  • Tauri requires webkit2gtk-4.0 system package (no root)2 minutes
  • Node.js version was v18.19.1 but requires v24+1 minute
  • npm v9 couldn't parse npm:@voidzero-dev/vite-plus-core override syntax1 minute
  • cargo/rustc not installed1 minute
Install time
7 minutes
Cold machine to finish
10 minutes
Errors hit and fixed
5 hit, 5 fixed with no human help
How the result was proved
npm test exited 0 (551 tests, 22 workspaces), cargo test across 5 crates (179 tests), yaak-web --version returned 'yaak-web 0.1.0', yaak CLI --help showed all 13 command groups, yaak-playground binary built and prints help
Model tokens used
78,407
Exact commit tested
7f3025361685
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.

| Component | Result |
|---|---|
| npm test (22 workspaces) | 551 passed, 0 failed |
| Rust `yaak-http` tests | 89 passed |
| Rust `yaak` tests | 66 passed |
| Rust `yaak-commands` tests | 5 passed |
| Rust `yaak-git` tests | 18 passed |
| Rust `yaak-sse` tests | 1 passed |
| `yaak-web` binary | builds, `--version` prints "yaak-web 0.1.0" |
| `yaak` CLI binary | builds, `--help` prints all 13 command groups |
| `yaak-playground` binary | builds, `--help` prints usage |
| Web app build (`npm run web:build`) | succeeded in 1.44s |

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 7 minutes.
  • Recovered from all 5 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 7 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

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.09
Argusic Runner1/3Runs100.000.08

Topics (from GitHub)

bruno-alternativegraphqlgrpchttphttp-clientinsomnia-alternativepostman-alternativessetauriwebsocket

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/yaak.svg)](https://argusic.com/subject/yaak)

Questions

Does yaak run?
Yes. yaak runs. Argusic installed and launched it on a clean machine in 7 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test yaak?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 7f3025361685. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test yaak?
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 yaak take to install?
7 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 yaak need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing yaak?
5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for yaak?
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.

Discussion