Show HN: Oproxy – inspect and modify network traffic from the browser

A new traffic spy tool drops, and the comments instantly turn into a "why not just use this instead?" fight

TLDR: Oproxy is a new local tool that lets developers watch and alter app and browser internet activity from one place. Commenters weren’t instantly sold: some compared it to existing favorites, some said browsers already do enough, and one user immediately got stuck finding the interface.

A new project called Oproxy just strutted onto Show HN promising to be a one-stop local tool for watching, replaying, and even changing internet requests coming from your browser, apps, command line tools, and more. In plain English: it lets developers peek behind the curtain when software talks to websites and services. It can slow things down, fake responses, rewrite requests, and export what it sees into handy snippets. The creator also tossed in an experimental assistant and openly asked people to poke at it and report back. Brave move, because the comments arrived with knives out and curiosity fully activated.

The biggest reaction was basically: "Cool… but why would I use this over the stuff I already have?" One commenter immediately fired the classic comparison shot: how does it stack up against mitmproxy? Another said the browser already has built-in tools that cover a lot of this, so Oproxy needs to prove it’s more than “yet another dashboard.” That turned into the thread’s main drama: is this a genuinely useful all-in-one workshop, or just extra steps in a Docker container?

Then came the wonderfully messy real-world feedback. One user basically posted, "I have it running and still can’t figure out where the interface is," which is the kind of comment every software launch fears. Another commenter casually wandered in with "I’m building something similar", giving the whole thread a surprise rival-energy subplot. So yes, the app is about controlling traffic, but the real traffic jam was in the comments: skepticism, comparison-shopping, mild confusion, and that irresistible startup-for-geeks vibe of "nice tool, now survive the gauntlet."

Key Points

  • Oproxy is a local proxy for capturing, inspecting, replaying, and modifying HTTP, HTTPS, and SOCKS5 traffic.
  • The tool provides a browser-based management UI and API for viewing requests, responses, headers, bodies, timing, and inspector data.
  • It supports request replay, manual request composition, export to HAR/cURL/Fetch/Python, and import from HAR or oproxy JSON session data.
  • Traffic modification features include rule sets, throttling, breakpoints, mock responses, DNS overrides, Lua scripts, and upstream proxy chaining.
  • The article includes Docker, Docker Compose, and source-based setup instructions, plus examples for first HTTP and HTTPS captures using a local trusted CA.

Hottest takes

"How does it compare to mitmproxy?" — eloh
"the browser built-in network inspector overlaps a lot" — simon84
"I don't see how you actually see the web interface" — beernutz
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.