awl
Securely connect your devices into a private network. Mesh VPN, socks5 proxy server/client
Runssource: GitHubhomepageGoMPL-2.0commit c731a10f9103
Go, MPL-2.0 licensed. The project labels itself: cross platform, decentralized, golang, hacktoberfest, libp2p, mesh networks, network and p2p.
awl runs. An Argusic agent installed it in 7 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
the Go project compiles without errors, go vet passes, and all 162 tests pass across all packages (config, cli, p2p, socks5, vpn, protocol, ringbuffer, entity, awldns, api, and the root application package covering friend requests, invite links, exit nodes, VPN gateway, DNS, SOCKS5 proxy, CLI commands, tunnel packets, and metrics)
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.
- Go 1.26 not installed in container2 minutes
- Missing 'static' directory for embed.FS1 minute
- Server cannot create TUN device (no root)
- Install time
- 7 minutes
- Cold machine to finish
- 7 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- go test -count=1 -timeout 600s . passed (81 tests), plus 81 subpackage tests. go vet ./... passed. Binary builds and prints version.
- Model tokens used
- 111,165
- Exact commit tested
- c731a10f9103
- 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.
- **Build**: Go 1.26 was installed. Created minimal `static/` placeholder for the embed. Binary bui… - **Binary**: `awl --version` prints: `Anywherelan version dev (go1.26.0 linux-amd64)` - **Server start**: fails as expected (no TUN device / no root) - that's a runtime constraint, not … - **Tests**: all 162 tests across all packages pass. tokens used 111,165 Approximately 7 minutes elapsed. Let me now produce the report. The project builds and all tests pass. Let me summarize: - **Build**: Go 1.26 was installed. Created minimal `static/` placeholder for the embed. Binary bui… - **Binary**: `awl --version` prints: `Anywherelan version dev (go1.26.0 linux-amd64)` - **Server start**: fails as expected (no TUN device / no root) - that's a runtime constraint, not … - **Tests**: all 162 tests across all packages pass.
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, 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 MPL-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
Of the 13 cross-platform projects Argusic has installed and timed, awl was the 5th 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 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
Topics (from GitHub)
cross-platformdecentralizedgolanghacktoberfestlibp2pmesh-networksnetworkp2pproxyproxy-serverself-hostedsocks5socks5-proxyvirtual-networkvpnvpn-clientvpn-servervpn-service
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/awl)Questions
- Does awl run?
- Yes. awl runs. Argusic installed and launched it on a clean machine in 7 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test awl?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit c731a10f9103. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test awl?
- 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 awl 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 awl need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing awl?
- 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 awl compare with the alternatives?
- Of the 13 cross-platform projects Argusic has installed and timed, awl was the 5th fastest to reach a running state, and 10 of 13 reached one at all.
- Where is the evidence for awl?
- 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.