v4.1.1

Released November 13, 2026

Adds Gemini 4 Hydrogen, makes Agent Builder available to paid accounts, and changes how superadmin password resets and dedicated sub‑organization purchases work.

Forward‑only upgrade. This release includes database changes 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.

Action required for some deployments. Superadmin password resets now go to the user by email, and several superadmin API responses have changed. See Administration, For API users, and Before you upgrade below.

Confirming this release. Check the in‑app What’s New panel. Gemini 4 Hydrogen appears in the model picker where it’s enabled, and a superadmin password reset now reports that the reset was sent to the user (or shows a one‑time temporary password on deployments without email). Confirm your deployment’s version with your Ask Sage administrator.

🚀 New model

Google Gemini 4 Hydrogen. Google’s Gemini 4 Hydrogen, the smallest and fastest Gemini 4 model, is now available to eligible customers via Google Vertex AI, with a 1M‑token context window shared by input, reasoning, and output, and configurable reasoning effort. It’s flagged for CUI / ITAR / EAR data controls.

New models appear only where they’re enabled for your deployment, within your compliance boundary, and for your organization. If you don’t see one, contact your Ask Sage administrator.

🛠️ Administration

Agent Builder is available to paid accounts. Users on accounts that aren’t paid no longer see Agent Builder, and its API endpoints return “Not found” for them. They can still delete workflows and agents they own. Paid accounts are unaffected.
Dedicated sub‑organization purchases are managed by superadmins. Only a superadmin can record or edit a dedicated purchase for a sub‑organization. Organization administrators still see each sub‑organization’s funding, and can still edit, delete, and manage members of sub‑organizations.
Superadmin password resets go to the user. When a superadmin resets a user’s password, the user receives a password reset email, and no password is shown to the superadmin. On deployments without email, the superadmin is shown a one‑time temporary password to pass on instead. Either way, the user must set a new password at their next sign‑in. Password resets aren’t available for accounts that sign in only with single sign‑on (SSO).

🔌 For API users

Superadmin password reset. /superadmin-reset-pw responses include a delivery field: link (the user receives a password reset email and no password is returned) or temp_password (a temporary password is returned once, on deployments without email). If email is configured but can’t be sent, the request returns HTTP 503 and nothing changes.
Superadmin API key endpoints. /superadmin-get-user-api-keys lists each key’s details without the key itself. /superadmin-user-api-key is retired and returns 404; users create their own keys.
Superadmin user lists. /superadmin-get-users returns 100 users by default (email searches return up to 1,000) and at most 1,000 per request; its truncated field says when more users match. Page through larger lists with start and limit. /superadmin-export-users-csv exports up to 10,000 users per request; page through larger exports with offset and limit, using the response headers that give the next page’s offset.
Credentials during a required password change. Until a user completes a required password change, requests to create an API key or register a sign‑in method return HTTP 403 with the code password_change_required.
Text‑to‑speech. /get-text-to-speech accepts up to 20,000 characters of text by default. Empty text or text over the limit gets a response with status: 400 and a message that explains the problem; a malformed request returns HTTP 400. Bot accounts can’t use this endpoint.

Before you upgrade (self‑hosted and Ask Sage Edge)

Password reset delivery. By default, superadmin password resets use email when a mail server is configured, and use a temporary password when one isn’t. A deployment setting can choose either mode explicitly. With a mail server configured, a failed send returns an error and never falls back to a password.
Adjustable limits. The 20,000‑character text‑to‑speech limit and the 10,000‑user export page size can be changed per deployment.

🔒 Security & platform

This release also includes additional security hardening across the platform.

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