CaddyProxyManager
CaddyProxyManager - Manage Caddy via a web interface
Runssource: GitHubGoMITcommit 52cf246adeec
Go, MIT licensed. The project labels itself: caddy, caddyserver, reverse proxy and webinterface.
CaddyProxyManager runs. An Argusic agent installed it in 8 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The Caddy Proxy Manager backend serves the embedded SPA on port 3001, authenticates the seeded admin over the local login API, creates and deletes hosts whose per-host Caddyfiles pass caddy adapt --validate, and lists modules from a real Caddy v2.9.1 binary, with all backend and frontend test suites passing.
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.
- no Go toolchain and go.mod requires go 1.25.02 minutes
- npm install skipped @tailwindcss/oxide native binding; vite build failed with 'Cannot find native binding'2 minutes
- caddy binary missing so GET /api/caddy/modules returned 5002 minutes
- go build failed: embed pattern all:assets/** matched nothing until frontend was built1 minute
- restart attempt failed with bind: address already in use1 minute
- Install time
- 8 minutes
- Cold machine to finish
- 7 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- go test -count=1 ./... exited 0 with all 9 test packages ok; npm test exited 0 (10 passed); curl returned 200 on / and /api/auth/config; POST /api/users/login {email,secret} returned 200 with JWT; POST /api/hosts returned 200 and wrote host_2.conf validated by caddy adapt --validate; DELETE /api/hosts/1 returned 200 and removed host_1.conf; GET /api/caddy/modules returned 200 with real caddy module list
- Model tokens used
- 79,116
- Exact commit tested
- 52cf246adeec
- 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.
- Built `backend/main` and ran it in caddyfile mode on port 3001; the generated binary was moved ou… 2026-10-30T02:22:01.065130Z ERROR codex_core::session: failed to record rollout items: thread 01a18… tokens used 79,116 All verification is complete. Summary of what happened and the fixes: **Findings (all observed)** - Go was absent; downloaded `go1.25.4.linux-amd64.tar.gz` into `/tmp/gotools/go125` and used it via… - `npm install` skipped the platform native binding; `npm run build` failed with `Cannot find nativ… - Frontend build emitted `backend/embed/assets`; without it the Go `embed` packages failed. After t… - Caddy was missing, so `/api/caddy/modules` returned 500; downloaded Caddy `v2.9.1` to `/tmp/caddy… - Exercised the app: SPA root `200`, `POST /api/users/login` (email+secret) returned `200` + JWT, `… - Built `backend/main` and ran it in caddyfile mode on port 3001; the generated binary was moved ou…
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 8 minutes, faster than the median of the 3 comparable projects Argusic has measured.
- Recovered from all 5 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 MIT, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 4 caddy projects Argusic has installed and timed, CaddyProxyManager was the 2nd fastest to reach a running state, and 4 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.
- A quick evaluation: it was running 8 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)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/caddyproxymanager)Questions
- Does CaddyProxyManager run?
- Yes. CaddyProxyManager runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test CaddyProxyManager?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 52cf246adeec. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test CaddyProxyManager?
- The run that produced this verdict cost $0.10: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does CaddyProxyManager take to install?
- 8 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 CaddyProxyManager need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing CaddyProxyManager?
- 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.
- How does CaddyProxyManager compare with the alternatives?
- Of the 4 caddy projects Argusic has installed and timed, CaddyProxyManager was the 2nd fastest to reach a running state, and 4 of 4 reached one at all.
- Where is the evidence for CaddyProxyManager?
- 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.