Skip to content

Open Terminal

Open Terminal starts a new shell whose environment already points at Probe, so curl, git, npm, pip and other command-line tools appear in the log without changing your system proxy. Only that shell is affected. Probe keeps its setup files in ~/.probe/ (the setup script, and on macOS a copy of its CA and a Node wrapper); closing the shell undoes nothing there.

Open it from Tools → Open Terminal and pick a terminal app. The new shell shows a Probe banner and a (probe) prompt. Depending on the app it opens as a new window or as a new tab.

The shell gets the proxy variables HTTP_PROXY, HTTPS_PROXY and NO_PROXY (and their lowercase forms), pointing at Probe's running port, plus the GLOBAL_AGENT_* variables Node proxy libraries read.

Choose Terminal.app or iTerm. Terminal.app opens a new window. iTerm opens a new window, or a new tab if one is already open.

On top of the proxy variables, the shell gets:

  • CA trust variables (NODE_EXTRA_CA_CERTS, SSL_CERT_FILE, REQUESTS_CA_BUNDLE, CURL_CA_BUNDLE and PIP_CERT) pointing at a copy of Probe's CA, so HTTPS tools trust it;
  • a small Node.js wrapper, so Node libraries and the built-in fetch() that ignore proxy variables are captured too.

macOS may ask for permission to control the terminal app (an Automation prompt); allow it. Tools → Open Terminal → Manual Setup Guide shows copy-paste snippets if you'd rather set up a shell you already have open.

A shell keeps the port it was opened with. If you change the proxy port, open a new terminal.