The Rust-powered HTTP proxy that lets Claude Code inspect, debug, and fix your network traffic. Run hp shell to capture all CLI traffic in one session, then ask Claude to find and fix the broken request — no curl loops, no screenshots, no context-switching.
HTTPeep wins on 12 out of 12 key features
Why HTTPeep
HTTPeep focuses on repeatable debugging: clear rule execution, contained DNS changes, precise interception, HTTPS-ready mocks, reusable URL templates, and workflows that work in both GUI and CLI.
Captured sessions are SQLite databases. Claude Code queries them directly — find the failed POST, compare headers across retries, or trace request chains without exporting CSV files. hp shell captures every command automatically.
HTTPeep generates and installs a local CA certificate automatically. Claude Code can inspect decrypted request/response bodies, headers, and TLS metadata for every captured call.
Claude Code reads the captured request, modifies auth headers, body payloads, or query params, and replays through the live proxy. See the diff between the original and fixed response instantly.
Define rules to intercept, mock, bypass, or redirect traffic. Claude Code can suggest rules, insert them into the running proxy, and verify the result — all from the same conversation.
Rust-native desktop app (Tauri) for macOS, Windows, and Linux. All traffic stays on your machine — no cloud proxy, no telemetry, no data ever leaves localhost.
One command installs the Claude Code skill. Run hp shell to proxy all your CLI tools, then ask Claude in plain language: "check why the POST to /api/orders failed." Claude inspects the captured session, finds the issue, and can replay the fixed request — all in the same conversation.
Traditional network debugging is a multi-tool chore. You curl an endpoint, stare at raw headers, search documentation for the status code, guess at the fix, edit code, run again, and hope. Every iteration costs minutes. Over a workday, that is hours lost to tool-switching and manual correlation.
HTTPeep + Claude Code changes the loop. Run hp shell — it transparently proxies every CLI command under a single session. Then ask Claude: "why did the POST to /api/orders return 401?" Claude reads the captured request directly from the session, sees the missing Authorization header, explains what happened, and can replay the fix. Done. No curl, no screenshots, no context switch.
Step 1 — Capture: Run hp shell. HTTPeep launches a subshell that transparently proxies every command's HTTP(S) traffic into a SQLite session. curl, npm, pip, your test suite — all captured.
Step 2 — Analyze: Ask Claude Code: "analyze the failed requests in this session." Claude reads the session directly from SQLite, finds errors, explains status codes, traces redirect chains, and surfaces anomalies.
Step 3 — Fix & Replay: Claude suggests a fix — update a header, correct a payload. It replays the modified request through HTTPeep and shows you the before/after, all in the same conversation.
"Why is my API returning 500?" — Ask Claude with a captured request. It reads the response body, checks for backend error messages, cross-references headers, and explains the likely cause.
"Where is this duplicate request coming from?" — Claude traces the initiator chain across the session, finds the source page or script, and suggests a fix.
"Test this endpoint without curl." — Describe the request in plain language. Claude builds it, replays it through HTTPeep, and shows the parsed response.
"Debug mobile app traffic with AI." — Point your phone at HTTPeep as the proxy. Claude reads and analyzes the captured mobile API calls just like browser traffic.
Download HTTPeep, install the Claude Code skill, run hp shell, and let Claude read, debug, and fix your HTTP traffic. Free to start, Pro for unlimited sessions.