{"version":"2.1.200","anchor":"mtls-certificate-hot-reload","canonical_anchor":"mtls-certificate-hot-reload","heading":"mTLS Certificate Hot-Reload","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.200\/e\/mtls-certificate-hot-reload","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.200","markdown":"### mTLS Certificate Hot-Reload\n\nThe mTLS client certificate implementation was refactored to support hot-reloading. Previously, certificates were loaded once at startup (via a singleton). Now:\n\n- Certificates are re-read from disk whenever `CLAUDE_CODE_CLIENT_CERT` or `CLAUDE_CODE_CLIENT_KEY` changes\n- An async reload function queues sequential refreshes (no concurrent reloads)\n- The HTTPS agent is rebuilt only when the certificate content actually changes\n- Path and content are both tracked to detect file replacement vs. content changes\n\nError messages are now more descriptive, reporting the certificate role (e.g., \"client certificate from CLAUDE_CODE_CLIENT_CERT\") rather than the file path.\n\n**Evidence**\n\nRefactored mTLS module (search for `\"mTLS: Loaded client certificate from CLAUDE_CODE_CLIENT_CERT\"`, `\"mTLS: Creating HTTPS agent with custom certificates\"`)"}