Sort of: it generates a certificate, and you _can_ add it to the keychain just like mitmproxy etc, but by default it avoids doing that, because you don't need t

Sort of: it generates a certificate, and you _can_ add it to the keychain just like mitmproxy etc, but by default it avoids doing that, because you don't need to globally trust the CA cert for most use cases, and avoiding doing so if you can is nice for security (more details: https://httptoolkit.tech/blog/debugging-https-without-global-root-ca-certs/ https://httptoolkit.tech/blog/debugging-https-without-global...). Instead, it injects the certificate & proxy settings manually into intercepted targets as it launches them. So you can intercept a single Chrome window or all processes launched from a single terminal window without affecting any of the rest of your system.