# One-click HTTP debugging for any CLI tool

DevFeed: [One-click HTTP debugging for any CLI tool](<https://devfeed.tech/articles/one-click-http-debugging-for-any-cli-tool-19040.md>)

Original publisher: [Read original article](<https://httptoolkit.com/blog/announcing-terminal-interception/>)

Author: HTTP Toolkit; Tim Perry

Published: 2019-01-22T14:50:00Z

Content type: release

Language: en

Sources: [HTTP Toolkit](<https://devfeed.tech/sources/http-toolkit.md>)

Topics: [Command-line interface](<https://devfeed.tech/topics/cli.md>), [HTTP](<https://devfeed.tech/topics/http.md>), [debugging](<https://devfeed.tech/topics/debugging.md>), [cURL](<https://devfeed.tech/topics/curl.md>)

Tags: [cli](<https://devfeed.tech/tags/cli.md>), [command-line](<https://devfeed.tech/tags/command-line.md>), [curl](<https://devfeed.tech/tags/curl.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [github](<https://devfeed.tech/tags/github.md>), [http](<https://devfeed.tech/tags/http.md>), [interception](<https://devfeed.tech/tags/interception.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [tool](<https://devfeed.tech/tags/tool.md>)

## AI overview

HTTP Toolkit introduces one-click terminal interception for HTTP and HTTPS traffic from command-line tools. The feature helps developers inspect requests and responses to debug failing applications, understand tool behavior, and identify data sent to analytics or tracking services.

## Source excerpt

Debug HTTP(S) from git, npm, apt-get, or any other CLI tool. The command line is powerful, but can be hard to understand, and extremely hard to debug. Ever run a command, see it fail with a cryptic error, and have no idea why? Better tools can help you understand what's really going on. They can let you see inside the command you're running to understand how it's communicating, see what data it's working with, and debug it in depth. Excitingly I've just shipped one-click terminal interception to do exactly this with HTTP Toolkit, for HTTP and HTTPS, to show you everything your CLI is sending and help you work out what the hell is going on. HTTP Toolkit is free & open-source, so if you want to try this yourself, go download it now and dive right in. How do I try it? Install HTTP Toolkit (if you haven't already). On the Intercept page, click the 'Terminal' button. In the terminal that opens, make some HTTP requests (try curl example.com, sudo apt-get update, git clone https://..., or anything!) Open the View page in HTTP Toolkit, and take a look through the full details of every request sent. What can I do with this? Debug failing applications Let's imagine you're using a CLI tool, and it hates you. For whatever reason, it refuses to do the perfectly reasonable thing you ask for. It exits with some cryptic error, or just fails silently, and you're stuck. Maybe you just downloaded it, or maybe it's your code and you've just forgotten how it works (we've all been there). Internally perhaps this script is talking to an HTTP service somewhere, and failing later on. Unfortunately, you have no idea what it's asking for, what it gets in response, or why the result doesn't work. Most applications aren't designed to be debugged, and can be painfully opaque. If you can intercept all HTTP from the app then you see everything that's being sent, spot the error, and fix the root cause directly. Is your script requesting a file from github and then crashing trying to use it? When yo