Chris Maskey

Work

Proxy View

Year
2026

A terminal-first reverse proxy that captures, inspects, and replays HTTP traffic without a config file or a second app.

Debugging an HTTP API often means reconstructing a request from fragments: a log line here, a browser tab there, a curl command you forgot to save. proxy-view puts the traffic in one place.

Point it at a target URL and it starts forwarding immediately. It captures the method, headers, body, and timing, then surfaces the request in a live terminal table or a browser dashboard.

The happy path is intentionally one line:

proxy-view https://api.example.com

Run, inspect, replay

  • Run: point the proxy at any target URL. No config file, SSL setup, or daemon.
  • Inspect: watch method, status, and latency in the terminal, or open the React dashboard for a closer look.
  • Replay: send a captured request again, optionally with a diff view.
  • Keep: store traffic in SQLite and let the automatic seven-day cleanup handle the backlog.

Small by design

The core uses Python, httpx for proxying, typer and rich for the CLI, and aiosqlite for storage. The standalone React + Vite dashboard connects over WebSockets for live updates.

proxy-view is not trying to be Charles or mitmproxy. It is a small loop — run, inspect, replay — that stays close to the problem and makes HTTP debugging feel less like archaeology.