Unclear Whether the runtime bundled with this build actually offers the reusable session is unknown; if it does not, the old path is always used.
When Claude Code runs as the standalone native executable, and the built-in runtime offers it, API requests can now go through one shared, reusable connection session instead of setting up each request separately. That session is created with your current TLS settings (the certificate and encryption options, including any custom certificate authority). If those settings change, the old session is closed and a new one is made.
If a proxy or a Unix socket is configured, those options are still passed along. Otherwise the per-request TLS option is dropped and the session's own settings are used. In every other situation, including non-native installs, requests go the old way.
Reusing connections changes how the native install talks to the network. It may affect speed, and it is worth keeping an eye on if you rely on a custom certificate authority or a proxy.
Whether the runtime bundled with this build actually offers the reusable session is unknown; if it does not, the old path is always used.