Kivo

A minimal, fast, and modern desktop HTTP client built with Rust and Tauri

Runssource: GitHubJavaScriptMITcommit 5a6efe4189ce

JavaScript, MIT licensed. The project labels itself: cross platform, http client, lightweight, rust and tauri.

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

89 frontend unit tests pass and vite build succeeds on Node 18 with vite 5; the Tauri/Rust desktop backend cannot be tested without a Rust toolchain in this container

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.08 (measured)
recorded runs
1
last tested
stars
370
forks
20
open issues
1
watchers
0
size
3 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 Kivo, 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.

  • contract-validation.js uses crypto.randomUUID() without importing node:crypto on Node 181 minute
  • workspace-store.js uses crypto.randomUUID() without importing node:crypto on Node 181 minute
  • Vite 7 requires Node 22+ (crypto.hash) but container has Node 181 minute
Install time
5 minutes
Cold machine to finish
5 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
node --test --test-reporter tap test/*.test.mjs exited 0, 89 passed, 0 failed
Model tokens used
118,017
Exact commit tested
5a6efe4189ce
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.

I started at ~08:09, the session began. Let me calculate elapsed time in minutes.
The start was ~08:09 UTC and now it's ~08:14 UTC, so about 5 minutes. But the `pnpm install` and Vi…
Actually the start was: `Session start: 2026-10-23 08:09 UTC` and now it's `08:14:03` — about 5 min…
2026-10-23T08:14:47.474672Z ERROR codex_core::session: failed to record rollout items: thread 01a16…
2026-10-23T08:14:47.474708Z ERROR codex_core::session: failed to record rollout items: thread 01a16…
2026-10-23T08:14:47.474717Z ERROR codex_core::session: failed to record rollout items: thread 01a16…
tokens used
118,017
All 89 tests from 22 test files passed. Here's the final report:
I started at ~08:09, the session began. Let me calculate elapsed time in minutes.
The start was ~08:09 UTC and now it's ~08:14 UTC, so about 5 minutes. But the `pnpm install` and Vi…
Actually the start was: `Session start: 2026-10-23 08:09 UTC` and now it's `08:14:03` — about 5 min…

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, faster than the median of the 12 comparable projects Argusic has measured.
  • 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 MIT, as reported by its host.

What did not, or is not known

  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 13 cross-platform projects Argusic has installed and timed, Kivo was the 2nd fastest to reach a running state, and 10 of 13 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.
  • 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

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.08

Topics (from GitHub)

cross-platformhttp-clientlightweightrusttauri

Embed the badge

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

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

Questions

Does Kivo run?
Yes. Kivo runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test Kivo?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 5a6efe4189ce. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test Kivo?
The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does Kivo 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 Kivo need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing Kivo?
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 Kivo compare with the alternatives?
Of the 13 cross-platform projects Argusic has installed and timed, Kivo was the 2nd fastest to reach a running state, and 10 of 13 reached one at all.
Where is the evidence for Kivo?
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.

Discussion