{"version":"2.1.265","anchor":"jvm-truststore-build-for-agent-proxy-now-reuses-an-existing","canonical_anchor":"jvm-truststore-build-for-agent-proxy-now-reuses-an-existing","heading":"Agent-proxy CA install now skips redundant work","tier":"internal","area":"Agent Proxy","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/jvm-truststore-build-for-agent-proxy-now-reuses-an-existing","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Agent-proxy CA install now skips redundant work\n\nClaude Code no longer reinstalls a certificate authority into the JVM or system trust store when it's already there\n\n**What**\n\nWhen Claude Code's agent-proxy sets up a certificate authority (CA) so network tools can trust its traffic, it now checks first whether the work is already done:\n\n- For the JVM truststore (Java's certificate store), it checks a small tracking file to see if the current CA is already recorded and the truststore file still exists. If so, it skips rebuilding the truststore and logs \"reusing JVM truststore at...\".\n\n- For the system trust store, it checks whether the CA is already recorded as installed for the current system CA. If so, it skips rerunning the operating-system-specific install step and logs \"CA already in the system trust store; install skipped\".\n\nBoth cases now record `reused: true` in their telemetry.\n\n**Why**\n\nThis avoids unnecessary, repeated CA installation work every time the checks run, which previously happened even when nothing had changed.\n\n- Area: Agent Proxy\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}