Claude Studio v1.18.4

When Chrome says "Not secure", nothing else can work

That one fact explains the whole chain: a page the browser distrusts registers no service worker and installs no app, so Add to Home screen can only ever produce a Chrome shortcut. No amount of tapping turns it into an app.

• The certificate is now issued the way a strict validator wants it: keyUsage, a subject key identifier, and a 397-day life instead of 800. The 398-day ceiling is written for publicly trusted certificates and a local root should be exempt — but that is not worth betting on when the failure mode is silent. It is reissued automatically within a month of expiry.
• The setup page stops pretending it can tell. A trusted certificate and one waved through with Proceed anyway both open the connection, and the page could not distinguish them. The certificate download now stays available even on the "trusted" screen.
• It names the trap: Android also offers to install certificates for Wi-Fi, and one filed there is invisible to Chrome. The page says to check Settings → Security → Encryption & credentials → Trusted credentials → User for "Claude Studio Bridge".