I don't see how you actually see the web interface for the traffic it is tossing, and that is not explained in your readme so far as I have found.

I have it running in docker with docker run --rm \ --name oproxy \ --ulimit nofile=65535:65535 \ -p 8080:8080 \ -p 1080:1080 \ -e OPROXY_BIND_HOST=0.0.0.0 \ -e OPROXY_MITM_ENABLED=true \ -v oproxy-certs:/app/certs \ -v oproxy-storage:/app/storage \ ghcr.io/sauravrao637/oproxy:latest

and I set the proxy to use it, and it appears to work, but I don't have a way to see what it is doing.

I can understand the motivation for CLI-based clients, but the browser built-in network inspector overlaps a lot.

There is more to Oproxy with traffic shaping but would it be enough to convince ? Spawning a Docker is easy today but it would be less friction with a normal app imho.

If you try it out, I'd appreciate feedback on the assistant. It's still experimental but I am curious about its usability.

How does it compare to mitmproxy?

slop