wireguard-gui
A wireguard client GUI for Linux made with nextauri
Runssource: GitHubTypeScriptApache-2.0commit 43073da32ea2
TypeScript, Apache-2.0 licensed. The project labels itself: linux, security, vpn, vpn client and wireguard.
wireguard-gui runs. An Argusic agent installed it in 30 minutes and hit 8 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The WireGuard GUI app (Tauri + Next.js) builds and launches on Xvfb; both E2E tests pass: encryption flow (create, encrypt, lock, unlock, edit, delete, reset) and auto-lock flow (inactivity lock, blocked profile read), 2/2 tests passing via WebKit WebDriver on the X display
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.
- Missing system -dev packages (libglib2.0-dev, libgtk-3-dev, libwebkit2gtk-4.1-dev, etc.) — no root for apt-get install10 minutes
- WebKit child processes (WebKitNetworkProcess, injected-bundle) hardcoded to /usr/lib/x86_64-linux-gnu/webkit2gtk-4.1/ — cannot create directory without root5 minutes
- Transitive pkg-config dependencies (xproto, kbproto, libffi, dbus-1, etc.) still missing from extracted .pc files3 minutes
- Linker picked up static .a archives (libgio-2.0.a, etc.) from dev packages instead of shared .so, causing missing symbols (mnt_*, dbus_*)3 minutes
- Missing runtime libraries: libxslt, libgst*, libayatana-indicator, libdbusmenu, libdw, liborc3 minutes
- Node.js v18.19.1 is too old for Next.js 16 (requires >=20.9.0); next-build immediately failed2 minutes
- Install time
- 30 minutes
- Cold machine to finish
- 33 minutes
- Errors hit and fixed
- 8 hit, 8 fixed with no human help
- How the result was proved
- npm run e2e:test exited 0; wdio reported '2 passing' for e2e/specs/security-flow.spec.ts, profile creation, encryption enable, lock, unlock, profile update, profile delete, reset, and inactivity auto-lock all exercised and passed
- Model tokens used
- 1,172,801
- Exact commit tested
- 43073da32ea2
- 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.
[WebKitGTK 605.1.15 linux #0-0] 2 passing (1m 27.1s) Spec Files: 1 passed, 1 total (100% completed) in 00:01:44 Both e2e tests passed. Let me calculate the elapsed time: exec /bin/sh -lc 'echo "Start time: $(stat -c '"'%Y' /proc/1/cmdline 2>/dev/null || echo 'N/A')\" ; echo… succeeded in 0ms: Start time: 1792849739 Current time: 1792849739 All systems operational. Here is the final report. tokens used 1,172,801 All systems operational. Here is the final report.
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 8 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 30 minutes to install, slower than the median of the 3 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 4 linux projects Argusic has installed and timed, wireguard-gui was the 4th fastest to reach a running state, and 2 of 4 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)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/wireguard-gui)Questions
- Does wireguard-gui run?
- Yes. wireguard-gui runs. Argusic installed and launched it on a clean machine in 30 minutes, hitting 8 errors on the way, and recorded the session.
- How did Argusic test wireguard-gui?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 43073da32ea2. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test wireguard-gui?
- The run that produced this verdict cost $0.26: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does wireguard-gui take to install?
- 30 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 wireguard-gui need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing wireguard-gui?
- 8 things broke in the recorded run, and 8 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does wireguard-gui compare with the alternatives?
- Of the 4 linux projects Argusic has installed and timed, wireguard-gui was the 4th fastest to reach a running state, and 2 of 4 reached one at all.
- Where is the evidence for wireguard-gui?
- 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.