Follow Discord
Sweep 27 Oct 2026 · 19:04Z Build v2.1.312 531 read Stable v2.1.308 Latest v2.1.312 Next v2.1.312 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.311 ·

Agent proxy can add its certificate directly to the Java trust store

When setting up trust for Java, the agent proxy now adds its CA straight into the Java cacerts store and skips the hook if that works

Group of 2 You'll notice Improvements
JSON All of v2.1.311
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.

See this entry in the whole of v2.1.311 →

Feedback