Skip to content
Console

Release Notes

Use this page to track notable documentation, support, and community changes.

Major product or docs changes should appear here and be mirrored in Discord #announcements. Operational details, moderation notes, AutoMod alerts, and private follow-up belong in staff-only Discord channels.

  • Every SDK can now sign in through your browser: the SDK prints a short code, you approve the request at https://dash.thalovant.com/activate, and the SDK receives a scoped, revocable API token instead of handling your password. Requires Python 0.4.22, Node.js 0.2.25, Go v0.3.3, Rust v0.2.20, or Kotlin, Swift, and .NET 0.1.1.
  • Added the API Tokens page: create scoped, expiring tokens for scripts, CI, and AI agents, copy the one-time secret, watch last use, and revoke. Creating and approving tokens needs a paid workspace plan.
  • Every SDK also documents direct API token auth through its control-plane constructor. See Sign In Without A Password.
  • MCP server 0.1.9 recommends a scoped THALOVANT_API_TOKEN for AI and CI configs, and its config status tool reports the declared auth mode. See MCP Server.

Unrestricted Source Scout Knowledge with Optional Age Protection

Section titled “Unrestricted Source Scout Knowledge with Optional Age Protection”
  • Source Scout no longer limits adult hubs to a topic allowlist. It accepts any nonempty question as the final source-backed fallback after more specific skills have had a chance to answer.
  • Runtime owners can explicitly protect audiences under 13, 16, 18, or 21. The setting checks both questions and answers and fails closed when a protected classification cannot complete.
  • The unrestricted default does not invoke age classification. Protected and unrestricted responses use separate cache identities.
  • Source Scout preserves OVOS language, script, and region tags and is not limited to English and French.
  • See Skills and Configure Runtime for the owner workflow.
  • Hub creation and editing now offer Standard or Autoscaling capacity without exposing Kubernetes settings.
  • Team includes one Autoscaling hub with two warm workers and a maximum of eight. Enterprise capacity is contract-defined up to 32 workers per hub.
  • Billing reports autoscaling slot usage and each hub’s saved worker ceiling.
  • Existing hubs remain Standard. Autoscaling uses a deterministic skill-only runtime and keeps each listener with its authoritative skill runtime while it scales.
  • See Create a Hub, Hubs, and Billing and Plans for the user workflow.
  • Thalovant Voice now reconnects automatically after a normal hub restart, a failed connection attempt, or a network ping timeout.
  • Every reconnect creates a fresh encrypted session and continues to enforce the pinned protocol-v3 server identity.
  • The macOS, Windows, and Linux downloads use the same reviewed client behavior as the production voice listener.
  • Existing paired clients can install the update without creating a new connection. If the app reports that the server identity changed, stop and confirm the change through support instead of bypassing the warning.
  • you want to know what changed in the docs;
  • you need a public summary to mirror into Discord;
  • you are checking whether support routes, limits, or troubleshooting pages changed;
  • you need a lightweight change log before opening a support request.
  • Go SDK v0.3.0 updates golang.org/x/net to its remediated release and therefore requires Go 1.25 or newer. It includes the v0.2.17 binary-frame allocation hardening and explicit read-only CI permissions.
  • Rust SDK v0.2.17 removes the vulnerable rustls-webpki 0.102 dependency path by using the operating system’s native TLS backend for MQTT. HTTPS and WSS remain on the fixed Rustls dependency line.
  • Both immutable registry releases passed their complete test and release pipelines plus clean public-registry consumer verification. A pinned critical/high dependency scan reports no remaining findings in either SDK.
  • Added the Private Beta Guide covering consent expectations, the first useful path, privacy-safe measurement, support, withdrawal, account export and deletion, and the warning to use test payment details only.
  • Private-beta release evidence uses random participant IDs and aggregate milestones; names, email addresses, prompts, replies, credentials, and payment details do not belong in repository evidence.
  • Go SDK v0.2.16 is available as a public Go module. Clean consumers can install it through the public Go module proxy without GitHub credentials or private-module configuration.
  • Updated the Go SDK guide with the immutable verified release command.
  • Added privacy-safe setup milestones for aggregate onboarding and time-to-first-value measurement. Prompts, replies, memory content, email addresses, tokens, credentials, and secret material are excluded from activation metadata.
  • Account deletion now erases linked product telemetry, activation milestones, analytics summaries and exports, and identity-linked audit traces before removing the account.
  • Added repeatable performance evidence for API reads and writes, public preview, direct SDK WSS, frontend bundle budgets, and MCP startup/tool discovery.
  • Updated Analytics and Audit with the user-visible privacy and deletion behavior.
  • Added Status Stream guidance for versioned condition events, PostgreSQL-backed sequence cursors, bounded replay, duplicate suppression, and snapshot recovery after an explicit cursor reset.
  • Clarified that the official SDKs do not yet wrap the control-plane status SSE endpoint.
  • Clarified that the public preview bridge releases independently, is compatibility-checked by the hub controller, and degrades browser preview without changing private/public visibility or normal hub reconciliation.
  • Added SDK Origins for browser origin requests, reviewer notifications, email handoff, and non-credentialed CORS behavior.
  • Updated SDK, endpoint, identity, and dashboard guidance so browser apps use reviewed origins while long-lived secrets stay server-side.

Public updates

Put user-facing docs changes, support process changes, and known limit changes in this page.

Discord mirror

Summarize major updates in Discord #announcements so community members can find them without reading every page.

Staff details

Keep operational notes, AutoMod alerts, and incident follow-up in staff-only Discord channels.

  • Simplified the docs home page so new readers see the smallest useful path first: learn the basics, build one setup, connect a client, or fix a visible problem.
  • Tightened first-read and high-friction pages so locked actions, limits, setup links, and first-heartbeat checks are easier to route.
  • Updated the docs style guide and page template to favor one clear promise, one clear first action, and fewer competing links.
  • Added Connect a Client for the current Connections flow.
  • Updated client guidance for one-time setup links, Thalovant Voice, Linux setup commands, and first-heartbeat checks.
  • Refreshed Quick Start, First Successful Setup, troubleshooting, limits, and security pages so setup links appear before manual file handling.
  • Added Manage Updates as the plain-language owner for skill updates, runtime updates, hub updates, release policy targets, and Billing gates.
  • Refreshed Runtime, Skills, Hubs, Dashboard, Billing, and Known Limits so users can tell whether an update belongs to a skill package, runtime container target, hub container target, or plan check.
  • Updated plan-limit language so Billing remains the source of truth for exact workspace allowances.
  • Added the Analytics page for usage analytics, demand signals, geography, client posture, and hub/client detail filtering.
  • Updated Dashboard guidance for the current Fleet overview, Fleet snapshot, Client activity, attention, and update panels.
  • Added the Audit page for account trail, session history, visible actions, and support-safe history packets.
  • Clarified that paid Skill Store access is plan-reported rather than hardcoded in docs.
  • Refreshed Runtime guidance for primary and secondary languages, and Live Map guidance for delayed status catch-up after broad service trouble.
  • Added the status page to help, limits, troubleshooting, support-request, and Discord setup guidance.
  • Updated support templates so readers capture whether the status page was checked before filing broad service issues.
  • Added the public Get Support page with support, bug report, and feature request templates.
  • Added Known Limits with a plan-first limit check.
  • Added Troubleshooting Index so readers can route from a visible symptom to the owner page.
  • Added Discord support channels, staff-only channels, pinned starter messages, forum tags, AutoMod rules, and the welcome screen.
  • Documented that major docs and support changes should be mirrored in Discord #announcements.
  • Added support handoff language that warns readers not to share tokens, passwords, API keys, client secrets, connection files, private customer data, or sensitive screenshots.

A release note is ready when it explains:

  • what changed;
  • who should care;
  • which docs page owns the next action;
  • whether Discord should receive a public announcement;
  • whether any private follow-up belongs in staff-only channels.
Open get support