voiden
Design, Test and Document APIs in plain Markdown. Compose Requests with API blocks. Reuse, Replace & Version everything just like code. Offline, Truly Git Native, No Lock-in.
Runssource: GitHubhomepageTypeScriptApache-2.0commit e9ac33e2ead9
TypeScript, Apache-2.0 licensed. The project labels itself: api client, automation, bruno alternative, cli, curl alternative, graphql, http client and insomnia alternative.
voiden runs. An Argusic agent installed it in 25 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Voiden runner builds and passes all 29 tests, UI passes 27 tests with 21 jsdom ESM errors (pre-existing), Electron app compiled and launched but fails to connect to Vite dev server in headless container. Node v22.11.0 + Yarn 4.3.1 installed and working.
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.
- Node.js v18.19.1 too old (requires v21+); Corepack not available with bundled Node5 minutes
- UI build fails on tailwindcss v3 incompatibility (reading undefined 'blocklist')5 minutes
- tailwind.config.js contained v2 'darkMode' and 'safelist' keys not valid in v32 minutes
- vite.config.ts root path doubled when building UI from workspace root1 minute
- postcss.config.js referenced './apps/ui/tailwind.config.js' (wrong relative path)1 minute
- Electron test fails due to missing Electron runtime (window.ts references app.name)1 minute
- Install time
- 25 minutes
- Cold machine to finish
- 13 minutes
- Errors hit and fixed
- 7 hit, 7 fixed with no human help
- How the result was proved
- npx vitest run --root packages/voiden-runner: 2 test files, 29 passed; npx vitest run --root apps/ui: 3 test files, 27 passed; node packages/voiden-runner/dist/index.js --version returned 2.3.0-beta.20; node packages/voiden-runner/dist/index.js --help showed all commands
- Model tokens used
- 121,370
- Exact commit tested
- e9ac33e2ead9
- 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.
- # and add it below.
- outputHash = {
The `yarn-project.nix` diff is just from `yarn install` regenerating it - that's cosmetic. The `.np…
2026-10-05T10:29:04.620680Z ERROR codex_core::tools::router: error=exec_command failed: CreateProce…
exec
/bin/sh -lc 'cd /work/repo && git checkout -- yarn-project.nix 2>/dev/null; echo "reverted yarn-pro…
succeeded in 0ms:
reverted yarn-project.nix
Now for the final summary:
tokens used
121,370
Now for the final summary: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 7 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 25 minutes to install, slower than the median of the 5 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 6 api-client projects Argusic has installed and timed, voiden was the 5th fastest to reach a running state, and 5 of 6 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)
api-clientautomationbruno-alternativeclicurl-alternativegraphqlhttp-clientinsomnia-alternativemarkdownmcp-clientmcp-toolsoffline-firstopenapiopenapi3opensourcepostman-alternativerest-apiscriptingtestingwebsocket
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/voiden)Questions
- Does voiden run?
- Yes. voiden runs. Argusic installed and launched it on a clean machine in 25 minutes, hitting 7 errors on the way, and recorded the session.
- How did Argusic test voiden?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit e9ac33e2ead9. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test voiden?
- The run that produced this verdict cost $0.24: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does voiden take to install?
- 25 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 voiden need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing voiden?
- 7 things broke in the recorded run, and 7 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does voiden compare with the alternatives?
- Of the 6 api-client projects Argusic has installed and timed, voiden was the 5th fastest to reach a running state, and 5 of 6 reached one at all.
- Where is the evidence for voiden?
- 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.