wstunnel
Tunnel all your traffic over Websocket or HTTP2 - Bypass firewalls/DPI - Static binary available
Runssource: GitHubhomepageRustBSD-3-Clausecommit 5b17615dda10
Rust, BSD-3-Clause licensed. The project labels itself: http2, reverse tunnel, socks, socks5, socks5 proxy, tcp tunnel, transparent proxy and tunneling.
wstunnel runs. An Argusic agent installed it in 19 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The wstunnel binary builds and all 39 library tests pass, including TCP tunnel, UDP tunnel, socks5, WebTransport, reverse tunnel, and restriction integration tests. The server responds with proper error codes to HTTP requests.
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.
- IPv6 is disabled at kernel level (read-only sysctl), UDP server tests bind to ::1 (IPv6 localhost) and panic8 minutes
- Docker is not available in the container, TCP test test_proxy_connection panics on testcontainers Docker init5 minutes
- Install time
- 19 minutes
- Cold machine to finish
- 20 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- cargo test --package wstunnel --lib exited 0, 39 passed
- Model tokens used
- 176,262
- Exact commit tested
- 5b17615dda10
- 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.
echo \"=== Test result ===\" . \""'$HOME/.cargo/env" && cargo test --package wstunnel --lib 2>&1 | tail -5' in /work/repo succeeded in 10121ms: Errors encountered and fixes applied: 1. NO_COLOR env var was set to 1, causing '--no-color' flag parsing error - not a code issue, just … === Test result === test test_integrations::test_udp_tunnel ... ok test test_integrations::test_udp_tunnel_webtransport ... ok test result: ok. 39 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 10.13s 2026-11-06T02:12:25.008527Z ERROR codex_core::session: failed to record rollout items: thread 01a1a… tokens used 176,262
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 19 minutes.
- Recovered from all 2 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 BSD-3-Clause, 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.
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)
http2reverse-tunnelsockssocks5socks5-proxytcp-tunneltransparent-proxytunnelingudp-tunnelwebsocketwireguardwireguard-tunnel
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/wstunnel)Questions
- Does wstunnel run?
- Yes. wstunnel runs. Argusic installed and launched it on a clean machine in 19 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test wstunnel?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 5b17615dda10. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test wstunnel?
- The run that produced this verdict cost $0.50: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does wstunnel take to install?
- 19 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 wstunnel need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing wstunnel?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for wstunnel?
- 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.