You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Cloud SessionsArea: what it touches
ImprovementsKind: in v2.1.311,
ImprovementsSection of the release
What
The agent proxy sits between Claude Code's tools and the network. It uses its own CA (certificate authority, the certificate that tells programs to trust its secure connections), and it installs that CA through an install hook. When the hook in question is the Java one, the proxy now first tries to add the CA directly to Java's cacerts store (the list of certificates Java programs trust).
If the direct install works, the hook is not run. Before, the hook always ran.
The result is returned as javaStore.
The proxy's report on how trust was set up now includes java_store and second_anchor_java_store when a Java trust store was involved. Before, it held only whether a CA was reused and which method was used.
Why
This changes how secure connections get trusted for Java tools that run through the proxy. If Java tools had trouble trusting the proxy, the CA may now be in the Java store without the hook running.