proxy.py
💫 Ngrok FRP Alternative • ⚡ Fast • 🪶 Lightweight • 0️⃣ Dependency • 🔌 Pluggable • 😈 TLS interception • 🔒 DNS-over-HTTPS • 🔥 Poor Man's VPN • ⏪ Reverse & ⏩ Forward • 👮🏿 "Proxy Server" framework • 🌐 "Web Server" framework • ➵ ➶ ➷ ➠ "PubSub" framework • 👷 "Work" acceptor & executor framework
Runssource: GitHubhomepagePythonBSD-3-Clausecommit fec682bc7d70
Python, BSD-3-Clause licensed. The project labels itself: dns over https, gfw, http proxy, http server, https proxy, man in the middle, mitm and mitmproxy.
proxy.py runs. An Argusic agent installed it in 1 minute and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
proxy.py installed and 247 tests pass; proxy server accepts HTTP proxy requests and forwards them successfully.
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.
- test_wait_for_server_raises_timeout_error: OSError [Errno 99] Cannot assign requested address instead of ConnectionRefusedError2 minutes
- Install time
- 1 minutes
- Cold machine to finish
- 12 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- .venv/bin/proxy --version returned 0.1.dev1+gfec682bc7; proxy server started on 127.0.0.1:18900, curl through proxy returned HTTP 200 from httpbin.org; pytest tests/ passed 247/247
- Model tokens used
- 300,454
- Exact commit tested
- fec682bc7d70
- 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.
- `.venv/bin/proxy --version` → `0.1.dev1+gfec682bc7` - `.venv/bin/proxy` started on port 18900, `curl --proxy http://127.0.0.1:18900 http://httpbin.org/… - `pytest tests/` → **247 passed, 0 failed** (includes 15 integration tests) tokens used 300,454 Here's the full report: **Install:** `pip install -e .` succeeded. proxy.py version `0.1.dev1+gfec682bc7`. **Error encountered:** 1 test failure — `test_wait_for_server_raises_timeout_error` raised `OSError… **Verification:** - `.venv/bin/proxy --version` → `0.1.dev1+gfec682bc7` - `.venv/bin/proxy` started on port 18900, `curl --proxy http://127.0.0.1:18900 http://httpbin.org/… - `pytest tests/` → **247 passed, 0 failed** (includes 15 integration tests)
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 1 minute.
- Recovered from all 1 error 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.
- A quick evaluation: it was running 1 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)
dns-over-httpsgfwhttp-proxyhttp-serverhttps-proxyman-in-the-middlemitmmitmproxyngrokngrok-alternativengrok-replacementproxyproxy-serverpython3reverse-proxytls-interceptiontunnelvpnweb-serverwebserver
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/proxy-py)Questions
- Does proxy.py run?
- Yes. proxy.py runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test proxy.py?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit fec682bc7d70. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test proxy.py?
- The run that produced this verdict cost $0.11: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does proxy.py take to install?
- 1 minute in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does proxy.py need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing proxy.py?
- 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 proxy.py?
- 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.