v3.9.1

Released September 22, 2026

A hotfix release that resolves a Claude Code gateway error and a Sign in with Ask Sage sign‑in error.

Forward‑only upgrade. This release includes a database change and cannot be rolled back to the previous version once applied. Self‑hosted and Ask Sage Edge deployments should plan accordingly; managed (SaaS) tenants are upgraded by Ask Sage.

🔧 Improvements & fixes

• Claude Code requests go through reliably. Resolved a gateway error (502) that could occur when using Claude Code, by correcting how requests are passed to the provider.
• Sign in with Ask Sage is more resilient. Fixed a sign‑in error (500) by ensuring required authentication settings are applied automatically during updates, so single sign‑on keeps working smoothly across deployments.

🔒 Security & platform

Ask Sage services are delivered as FIPS‑hardened, digest‑pinned, and cosign‑signed images within the FedRAMP Class D authorization boundary, and are continuously rebuilt against the latest patched base images as part of Ask Sage’s continuous‑monitoring commitment.