cloudflared
Cloudflare Tunnel client
Runs with mockssource: GitHubGoApache-2.0commit f9676c585623
Go, Apache-2.0 licensed. The project labels itself: cloudflare, cloudflare tunnel, reverse proxy and zero trust network access.
cloudflared runs, with stand-ins for the services it depends on. An Argusic agent installed it in 43 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
cloudflared builds from source with Go 1.27.1, the binary reports version f9676c5, and 36 of 38 test packages pass (6 ICMP tests skipped due to container ping permissions, quic passes individually but can timeout under combined CPU load).
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 92 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page. 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.
- TestSupportedCurvesNegotiation fails on Go 1.27: P256Kyber768Draft00 no longer advertised in TLS handshakes5 minutes
- Go 1.27+ not found in PATH3 minutes
- golangci-lint v1.62 built with Go 1.23 cannot parse Go 1.26 config3 minutes
- ICMP/ping tests fail: GID 1001 outside ping_group_range
- quic TestDatagram times out at 30s when run with resource-heavy packages (sshgen, token)
- Install time
- 43 minutes
- Cold machine to finish
- 44 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- ./cloudflared version returned 'cloudflared version f9676c5 (built 2026-09-28-07:15 UTC)'; go test -count=1 -timeout=30s ./crypto/ + 35 other packages passed (36/36); go build ./... exited 0
- Model tokens used
- 248,749
- Exact commit tested
- f9676c585623
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
? github.com/cloudflare/cloudflared/cmd/cloudflared [no test files] FAIL Now I have all the data. Let me summarize. exec /bin/sh -lc 'echo "Start: $(date -u -d@$(git -C /work/repo log -1 --format=%ct) '"'+%Y-%m-%d %H:%M … succeeded in 0ms: Start: 2026-09-24 16:19 UTC Now: Mon Sep 28 07:59:21 UTC 2026 Here's my complete assessment: tokens used 248,749 Here's my complete assessment:
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
- Installed in 43 minutes.
- Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.14 |
Topics (from GitHub)
cloudflarecloudflare-tunnelreverse-proxyzero-trust-network-access
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/cloudflared)Questions
- Does cloudflared run?
- cloudflared runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 43 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test cloudflared?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit f9676c585623. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test cloudflared?
- The run that produced this verdict cost $0.14: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does cloudflared take to install?
- 43 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 cloudflared need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing cloudflared?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for cloudflared?
- 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.