HTTP Toolkit Intercept

Use this skill when you need authoritative evidence of what your program sent to a remote API and what it received back while verifying a code change. Works across any runtime — Node.js, Bun, Deno, Python, Go, Ruby, Java/JVM, .NET, PHP, Rust, shell scripts, etc. — as long as the process respects a proxy.

The reliable pattern is:

1. Start HTTP Toolkit correctly.
2. Run the program through the proxy in a mode that produces a machine-readable log (e.g. --output-format json, debug logging, or structured stdout).
3. Export outbound HTTP requests from HTTP Toolkit.
4. Pair the outbound HTTP export with the inbound program session log.

Do not rely on TUI screenshots alone when the question is about request payloads, auth headers, or wire-level behavior.

Prerequisites / Known-Good Launch

Start HTTP Toolkit

On Linux/headless environments, plain httptoolkit often fails due to sandbox/X11 issues. Prefer: