tsdproxy
Automatic Tailscale reverse proxy for Docker containers. Zero sidecars. Label-based config. Automatic HTTPS.
Runs with mockssource: GitHubhomepageGoMITcommit 75bd326c0915
Go, MIT licensed. The project labels itself: automatic, containers, docker, docker compose, go, homelab, https and networking.
tsdproxy runs, with stand-ins for the services it depends on. An Argusic agent installed it in 7 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Binary at tmp/tsdproxy builds, all 1900 unit tests pass, the server serves HTTP 200 on localhost:8080 for both the dashboard root and health/ready endpoints, and Tailscale proxy creation awaits real OAuth/AuthKey credentials.
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, 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.
- goleak_test.go missing ignore for http2 readLoop goroutine in tailscale package2 minutes
- Install time
- 7 minutes
- Cold machine to finish
- 7 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- curl -s -o /dev/null -w %{http_code} http://127.0.0.1:8080/ returned 200; curl -s -o /dev/null -w %{http_code} http://127.0.0.1:8080/health/ready/ returned 200; gotestsum -- -race -buildvcs ./... exited 0 with 1900 tests passing
- Model tokens used
- 79,657
- Exact commit tested
- 75bd326c0915
- 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.
2026-10-06T10:23:00.098789Z ERROR codex_core::session: failed to record rollout items: thread 01a11… tokens used 79,657 The server started, both the dashboard (`/`) and health endpoint (`/health/ready/`) returned HTTP 2… **Summary of what was done:** 1. **Installed toolchain**: `mise` installed Go 1.27.1, bun 1.4.2, Node 22, gotestsum 1.13.0, templ… 2. **Built frontend**: `bun run build` in `web/` — succeeded, produced dist with htmx and PWA asset… 3. **Ran `templ generate`** — generated server-side templates. 4. **Built the Go binary**: `go build -ldflags ...` — produced a 63MB `tmp/tsdproxy` binary. 5. **Fixed a test failure**: Added `goleak.IgnoreAnyFunction` for an http2 readLoop goroutine in `i… 6. **Ran full test suite**: 1900 tests, all pass. 7. **Verified server launches and serves HTTP**: Both `curl http://127.0.0.1:8080/` and `curl http:…
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 7 minutes.
- Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, 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.
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
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.03 |
Topics (from GitHub)
automaticcontainersdockerdocker-composegohomelabhttpsnetworkingproxyreverse-proxyself-hostedsidecarssltailscaletraefik-alternativetsnetvpnwireguard
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/tsdproxy)Questions
- Does tsdproxy run?
- tsdproxy runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 7 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test tsdproxy?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 75bd326c0915. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test tsdproxy?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does tsdproxy 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 tsdproxy need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing tsdproxy?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for tsdproxy?
- 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.