Product updates

​

Voice input in chat

​

Files from Microsoft Teams group chats

​

Connector secret locations hidden from editors

​

Claude Fable 5.1 model

• Choose the HTTP method for Test Connection — A connector’s Test Connection request can now use a specific HTTP method — GET, POST, PUT, PATCH, DELETE, or HEAD — chosen next to the test URL, instead of always sending GET. An API whose verification endpoint expects something other than GET can now be tested from the connector form. A configured request body is only sent with methods that carry one.
• Faster Ontology version history and folder listings — Listing a folder, reading data app manifests, and loading version history in the Ontology no longer read the contents of every file to do it. Libraries with thousands of files load and save noticeably faster.
• Connector editors manage connector access — Anyone who can edit a connector can now manage who has access to it, including assigning roles, groups, and members, without holding the role write permission. Selecting a role in the share dialog still requires role read, which the default member role includes.
• Signed asset links follow enforced authentication — On deployments with enforced authentication, signed asset links for dashboard snapshots, chat artifacts, and app files now require a session, so they render only for signed-in users and no longer appear in Slack or email previews. Signed library file links keep working without a session, because the file handler verifies the signature itself.
• Data app refresh schedules replace the draft state (Beta) — A data app no longer has a draft state: every save is live for everyone it is shared with. Its Refresh menu now shows when the data was last refreshed, lets anyone with edit access set a refresh schedule (stored in UTC), and marks a scheduled refresh that failed, with the app’s creator notified in-app and by email.
• Faster Ontology git operations — Saving a file or creating a folder in the Ontology no longer walks the entire library. Git add and status operations look only at the location being changed, which is considerably faster on libraries with thousands of files.
• Tidier data app toolbar — Bookmark and full screen move into the data app overflow menu, leaving fewer controls in the toolbar itself.
• Duplicate roles and create roles in bulk — A role can now be duplicated. The copy starts with the original’s permissions, model access, and, optionally, its shared resources, then opens in the permissions editor so setting up a team of near-identical roles no longer means rebuilding each one by hand. Pasting one name per line into the duplicate dialog creates all of those roles at once from the same template.
• Dropbox connector — Dropbox is now a built-in API connector. Connect it with an API key or through OAuth, at the organization level or per member, and Ana can read files and folders from the connected account.
• Design system permission for designers (Beta) — Creating and editing design systems is now its own role permission, so designers can manage an organization’s app themes without full administrator access. Setting the organization-wide default stays with administrators, design-system actions only appear for members who can use them, and design systems are now managed in one place: the apps library.
• Ontology files in data app compute functions (Beta) — A data app’s compute functions can now read files from the Ontology with ana.file(path), which resolves a path or alias to a readable location. Access follows the same permissions the app’s creator already has.
• Higher data limits for data apps — A published data app can now hold more than twice as much data: the embedded snapshot limit is raised from 50 MB to 128 MB, and snapshots are stored in a denser columnar format that roughly halves their size for the same rows. Existing published apps keep working unchanged, and app code reads data exactly as before.
• Published apps and dashboards serve a fixed Ontology version — Publishing a data app or dashboard now records the Ontology version it was published against, and every copy of the published object serves that version. Previously two copies of the same object could disagree depending on when each one started.
• Ontology sync retries after remote changes — When a push to the Ontology’s git remote is rejected because the remote moved ahead, TextQL now pulls and retries automatically instead of failing the sync. Git errors in the sync history are shorter and name the actual cause, such as a merge conflict.
• Auto-attached Ontology files in Thread Insights — The Ontology tab in Thread Insights now lists the Ontology files that were attached to a conversation automatically, alongside the ones Ana opened on its own.
• The CLI is now called refinery — The ana command-line tool is now refinery: the binary, the Python package, the configuration directory, and the instructions it installs for coding tools all carry the new name. Upgrading is a one-time reinstall with the install command in the docs; the first refinery command moves your existing configuration and credentials across, so there is no need to sign in again. Every command keeps its name under the new binary, for example refinery init and refinery doctor.
• Verify a data app from the CLI before sharing it — refinery app verify renders the current version of a data app and exits with an error on any browser, HTTP, renderer, or screenshot failure, so a URL is only handed out once the app is known to load. Coding tools set up through the CLI verify automatically after creating, updating, or refreshing an app.
• Data app library home and sorting (Beta) — The data app library opens on an All Apps view, sorts apps deterministically, and clicking All Apps clears the active filters. Filters no longer persist across a refresh, and the app toolbar has fewer controls in the way.

​

Design systems for data apps

​

Organization-wide notification overrides

​

Subagents

• Clearer querying when raw SQL is off — When raw SQL is turned off for an organization, the interface now makes clear that querying through TQL and the Ontology is still available, instead of reading as though querying is disabled entirely.
• Faster dashboard schedule changes — Saving only a dashboard’s schedule no longer rebuilds the dashboard’s underlying artifact, so schedule and delivery changes save right away instead of triggering unnecessary work.
• Faster data app library — The data app library’s file tree loads faster, because listing a folder no longer reads and decodes the full contents of every file inside it.
• Ontology review counts include drafts — The Reviews badge in the Ontology sidebar now counts draft patches alongside open ones, so its number matches the list of reviews it opens.
• Pending Ontology sync badge — The Ontology now shows a pending-sync indicator before its first sync finishes, so a library that has not synced yet is distinguishable from one that is fully up to date.
• Plain-language check messages — Messages from config validation checks now say plainly what is wrong, in permissions vocabulary where access is the problem, with plain ids instead of internal syntax. Check titles state the guarantee being checked so they read correctly on passing rows too.
• Microphone recovery guidance — When the browser has blocked microphone access, the voice button now opens a recovery dialog with steps for your browser and starts recording as soon as access is restored, instead of showing a toast that pointed nowhere.
• Typed model fields in the public API — Model settings in the public API now use named model values instead of numeric identifiers. An organization’s default model, its enabled and restricted model lists, and a role’s allowed models all accept and return the same names shown in the model picker, and a request naming a model that does not exist is rejected instead of being stored. A new endpoint updates an organization’s model settings directly, enabled and restricted lists can be cleared through the API rather than only from Settings, and a change that would leave the organization with no usable model is refused.
• Automatic deletion of inactive data apps (Beta) — Organizations can now set a retention window after which unused data apps are deleted automatically, the same way inactive threads already are. Apps untouched past the window are removed and permanently deleted after a grace period, and deleting an app — by hand or automatically — now also clears its published copies and the data snapshots embedded in them. It is off by default; enable it under Settings → Security → Advanced.
• Zoom data apps — A data app can now be zoomed the way a browser page is: pick a level from the app toolbar or pinch on a trackpad, and the app reflows to fill the pane instead of scaling a shrunken picture. Comments stay anchored to the right spot at any zoom level.
• Dedicated audit log read permission — Reading the audit log is now governed by its own permission instead of organization write access, so a read-only auditor role can be given log access without also gaining the ability to redirect exports, change single sign-on, or delete the organization. Configuring audit log export still requires organization write.
• Dedicated permission for Ontology rules and owners — Managing approval rules, auto-approval shortcuts, and code owners is now its own permission rather than part of organization administration, so it can be granted to people who are not administrators and withheld from those who are. Existing administrators keep it.
• Explicit save for playbook edits — Editing a playbook no longer saves as you type. Changes — including schedule, delivery, and thread permissions — collect behind a single Save changes button in the header, and you are warned before leaving the page or closing the tab with unsaved work.
• Emoji in replies as an organization setting — Whether Ana uses emoji in replies is now a setting under Settings → Capabilities. Emoji stay suppressed by default, and an administrator can switch them on for the organization.
• Richer tables and links in chat — Tables in Ana’s replies now render with proper borders, column alignment, sticky headers, and horizontal scrolling, and numeric columns use tabular figures so digits line up down the column. In dark mode the table surface and its row separators now follow the theme instead of showing a white panel with a bright line under the first row. Links to objects inside TextQL now show an icon for what they point at and navigate in place instead of reloading the app.
• Tabular files up to 500 MB — Tabular files up to 500 MB can now be loaded for analysis, and large uploads are more reliable on Azure-hosted deployments.
• Open access for Ontology directories — Clearing every owner from an Ontology directory now opens it to everyone, instead of being rejected. An empty owner list is the supported way to lift a directory’s restrictions.
• Faster data app loads for viewers — Opening a data app no longer downloads the app’s source code — that happens only when you open the code editor — so viewers load apps considerably faster. Apps that embed their own fonts now render in them instead of falling back to a default typeface.
• Faster Ontology graph — The Ontology graph view loads faster, especially for large libraries, because a single request no longer loads the same library several times over.
• Clearer API connector test failures — When an API connector’s Test Connection fails, the form now shows a readable error message instead of a wall of raw server output. The Grain connector also moves to Grain’s v2 API, so testing it works again now that their v1 API has been discontinued.

​

Usage and billing as a connector

​

Share data app and dashboard folders

​

Connector credentials from AWS Secrets Manager

• Raw SQL from the CLI and OAuth tokens — Raw SQL can now be run against a connector with a CLI or OAuth access token. The capability has to be granted by name when the token is approved, and it still only works for members whose organization role already permits raw SQL.
• Clearer CLI permission errors — Signing in to the CLI now requests its full set of capabilities up front, with the approval page listing exactly what is being granted — organization roles continue to govern what each call may actually do. When a command is refused by an organization role rather than by the token itself, the error names the missing permission, and the new ana doctor command prints a ready-to-send request for your administrator.
• OAuth client credentials for MCP servers — HTTP and SSE MCP servers can now be configured with an explicit OAuth client ID and secret instead of relying on dynamic client registration, so you can connect servers behind identity providers such as Okta that require a pre-registered application. Saved secrets are stored encrypted and displayed redacted.
• Link to a dashboard from a data app (Beta) — A data app can now send the viewer to a dashboard with ana.navigate({ kind: 'dashboard', id }), routed within the app instead of opening a new browser tab.
• Library folder tree behaves like a file tree (Beta) — The data app library’s folder tree now follows the same interaction model as the Ontology file tree: the chevron and folder name act as one control, folder counts include items held in subfolders, and refreshing while inside a folder keeps you there.
• Settings navigation grouped by scope — Settings navigation is now grouped by scope, separating your personal account settings from organization-wide settings.

​

Embed dashboards in other applications

​

Run analyses from the command line

​

Automatic deletion of inactive threads

​

Per-member OAuth for BigQuery

​

Member-level Ontology permissions

• Connect an MCP server without leaving the chat — When Ana calls a tool on an MCP server you have not authorized yet, the chat now pauses on that step and offers to connect you right there. Sign in through the popup and the chat picks up where it left off, instead of failing the step and sending you to Settings to authorize first.
• Upload macro-enabled Excel workbooks — Macro-enabled Excel workbooks (.xlsm) can now be uploaded into a chat and are read as ordinary Excel workbooks, alongside the .xlsx files already supported.
• Fork a chat with new connectors, model, and methodology — Forking a chat now lets you change the connectors, model, analysis methodology, and thinking effort for the new branch, so you can take a conversation in a different direction without starting over.
• GPT-5.6 xhigh thinking effort — GPT-5.6 models now support the xhigh thinking effort, giving them more reasoning budget for the hardest problems.
• Report objectionable content in Microsoft Teams — People using Ana through Microsoft Teams can now report a bot message as objectionable content, and the Teams integration now correctly handles users who belong to more than one organization.
• Email tool no longer capped per run or per day — Ana’s opt-in email tool no longer enforces per-run or per-organization-per-day send caps, so an approved recipient list receives every message a run produces.
• FSx ONTAP scratch failover for sandbox workers — Self-hosted deployments on FSx for NetApp ONTAP now fail sandbox worker storage over to a scratch volume when ONTAP capacity is exhausted, so workers keep starting instead of failing to respawn.
• Chat stays pinned to the newest message — Chat now keeps the newest message in view as Ana streams her response, until you scroll up, so you no longer have to chase the latest output.
• Higher sandbox egress rate limit — The sandbox per-host network egress rate limit is now 5,000 requests per minute, giving data-fetching code more headroom before it is throttled.
• Command-line API key authorization — Command-line tools can now obtain an API key through a browser-approved device authorization flow: the tool shows a code, you approve it on a dedicated page in the app, and the key is issued and recorded in the audit log on approval.
• Governance controls for raw SQL — Administrators can now turn off raw SQL for an entire organization and gate it behind a dedicated raw-SQL permission that is revocable independently of read and write access, with every raw-SQL run recorded in the audit trail.
• Reset system roles to default permissions — The Settings roles page now includes a one-click action to reset a system role’s permissions back to their defaults.
• Upload BI workbooks into the sandbox — Power BI, Tableau, and ThoughtSpot workbook files (.pbix, .pbit, .twb, .twbx, .tml) can now be uploaded straight into a chat’s sandbox, where Ana can work with them alongside your other files.
• Word and PowerPoint files in Slack and Teams — Word and PowerPoint files sent to Ana through Slack or Microsoft Teams are now attached and read the same way they are in the web app, instead of being dropped as unsupported.
• Custom node affinity for deployments — Self-hosted deployments can now assign a Kubernetes node affinity to every service deployment and to sandbox workers — a chart-wide global.nodeAffinity default with per-service overrides — to pin workloads to specific nodes.
• Service replicas spread across dedicated nodes — For self-hosted deployments, global.serviceMaxReplicasPerNode now also sets minDomains to each service’s replica count, so a multi-replica service is required to spread across that many distinct nodes rather than only capping how many replicas share one node.
• Keep models available in VPC deployments — VPC deployments no longer retire models on the managed retirement schedule, so a self-hosted deployment keeps access to a model until its administrators choose to remove it.
• Developer toolchains in the sandbox bash tool (Beta) — The sandbox bash tool now includes common developer toolchains — Go, Node, and compilers — so Ana can build and run code in more languages directly from the shell.
• Comment on data apps for Ana to revise (Beta) — You can now leave comments on a data app, and Ana revises the app to address your feedback.

​

Per-member SSO for SAP HANA

• Steer the live turn with Cmd/Ctrl+Enter — Pressing Cmd/Ctrl+Enter while Ana is working now steers the current turn with your new message immediately, instead of queuing it to send after the turn finishes.
• View Ontology source in the app — You can now open the raw source of an Ontology file directly in the app, and the desktop app adds back and forward navigation for moving through recently viewed pages.
• Ontology entity count in the tree — The Ontology file tree footer now shows the total number of entities in the Ontology.
• Faster Ontology file browser — The Ontology file browser loads faster by evaluating folder access permissions lazily instead of up front.
• Version history shows who published — Version history now records and displays which member published each version.
• Automatic default connector for new chats — An organization’s first real connector is now set automatically as the default connector for new chats, so people can start asking questions without picking a source first.
• Sidebar quick actions on hover — Hovering an item in the sidebar now reveals a quick actions menu.
• Separate compute class for dashboard workers — Self-hosted deployments on GKE can now assign dashboard sandbox workers their own compute class, independent of the regular sandbox compute class, via sandbox.computeClassDashboards.
• Compute class and machine family for every deployment — Self-hosted deployments on GKE can now set a compute class and machine family for every service deployment — including valkey, oathkeeper, and in-cluster Postgres — not just web and compute.
• Spread service replicas across nodes — Self-hosted deployments can spread each service’s replicas across separate nodes via global.serviceMaxReplicasPerNode, so multiple web or compute replicas no longer all land on a single node.
• Restrict ingress to sandbox pods — Sandbox worker pods now ship with a NetworkPolicy that restricts inbound traffic to the compute engine, tightening the sandbox network boundary on self-hosted clusters.
• Override the system default model — Self-hosted deployments can set SYSTEM_DEFAULT_MODEL to control which model new organizations default to.
• Larger uploads on Azure Blob storage — Object storage on Azure Blob now uses chunked uploads, so self-hosted Azure deployments can store larger files.
• DeepSeek V4 Flash 0731 model — DeepSeek’s V4 Flash 0731 is now available as a model option in chat through Fireworks, joining the existing Claude, GPT, and Kimi families in the model picker.
• Attach a HAR file to feedback reports — The in-app feedback form can now attach a HAR network trace alongside a description and screenshot, so connectivity and loading issues come with the request detail needed to diagnose them. Image attachments now accept up to 15MB (up from 5MB) and HAR files up to 30MB, and submitting feedback no longer creates a duplicate report on a slow connection or repeat click.
• Build dashboards from any chat — Ana can now build and update dashboards from any chat, not only chats created specifically as a dashboard. Administrators can still turn dashboards off entirely from Settings > Features.
• Compact data app view switcher — The data app view switcher is now a compact, icon-only control, freeing up space in the data app toolbar.
• Sidebar bookmarks no longer bleed across organizations or members — Bookmarked threads and their sidebar order are now persisted server-side per organization and member, instead of a browser-local cache that could keep showing another organization’s or another person’s bookmarks on a shared profile.
• More accurate BigQuery dataset scope checks — A BigQuery connector scoped to a dataset no longer rejects queries against an in-scope view just because the view internally reads a table outside that dataset; only tables referenced directly by name are still enforced against the boundary.
• More reliable MCP credential updates — Updating an MCP server’s credentials, completing OAuth re-authentication, or turning a server off now drops its cached connection immediately, instead of continuing to use the old connection until it naturally expired.
• Report delivery no longer forced on app follow-ups — A follow-up message in an app-mode chat that began from Slack, Teams, or a playbook run no longer gets forced into producing a report — only research runs are pinned to report delivery.

​

Data apps

​

First-class authentication for Azure API connectors

​

Propose Ontology changes as GitHub pull requests

​

TQL-only connectors

​

Dark mode

​

TQL queries against Tableau

​

Claude Opus 5 model

​

Bash tool

• Use an existing SecretStore for external secrets — Self-hosted deployments using External Secrets can now point the chart at a SecretStore resource that already exists in the cluster, instead of having the chart create and manage one.
• Per-pod credentials for sandbox egress — Sandbox egress traffic is now authenticated with a per-pod credential instead of the pod’s source IP address, so outbound requests are always attributed to the correct sandbox even when the cluster network rewrites source addresses. Each sandbox pod runs a small proxy sidecar container that attaches the credential to outbound requests.
• Skill panel and improved code rendering — Invoking a skill in chat now opens a side panel showing its content, and code blocks in chat render with improved syntax highlighting.
• Custom Anthropic gateway per-model overrides — Self-hosted deployments using a custom Anthropic gateway can now override the wire-format model name for individual models via a values file mapping.
• Dashboard and data app heartbeats pause when hidden — Dashboard and data app views no longer count against your usage cap while their browser tab is in the background.
• Fewer false stream stalls in chat — Chat no longer reports a stream stall while Ana is reasoning silently.
• More reliable Fireworks tool calls — Report and Ontology tool calls against Fireworks-hosted models no longer fail with a 400 error.
• Schema tab fix for MySQL and ClickHouse — The Schema tab on MySQL and ClickHouse connector pages no longer appears empty.
• Clearer disabled MCP server status — A disabled MCP server now shows as Disabled instead of a misleading connection failure.
• More reliable MCP OAuth sign-in — MCP OAuth sign-in popups no longer silently fail in browsers that block cross-window messaging.
• Sidebar collapse fixes — Collapsed Bookmarks and Recent Threads sidebar sections now render fully collapsed, without a stray item count.
• Data app thread dropdown fix — Fixed the threads dropdown in the Data App workspace not responding to clicks.
• Cleaner Ontology file browser — Internal git and worker-state files no longer appear in the Ontology’s file browser.
• Tableau datasource targeting for TQL queries — Ontology TQL queries against a Tableau connector can now name the exact datasource to run against, via default_connector: <connectorID>::<datasourceLuid> in the file’s frontmatter or a datasource_luid parameter at query time, instead of failing when the connector has more than one.
• Identify the calling credential via the public API — A new WhoAmI endpoint on the public API returns the authenticated caller’s identity, roles, permissions, and which LLM models it can use, so integrations can introspect their own access programmatically.
• OAuth access tokens on the public API — The v2 REST API now accepts OAuth 2.0 access tokens for authentication, so integrations can call the API with a token from your identity provider instead of only an API key.
• Okta authentication for the LLM gateway — Custom LLM gateways can now authenticate with Okta using client_secret_basic and configurable scopes, in addition to the existing client-credentials support.
• Recover from sandbox failures instead of erroring — When a sandbox fails mid-conversation, chats now recover and continue automatically instead of surfacing an error.
• Login page ordered by recent organization — The organization list on the sign-in page is now ordered by the workspace you used most recently, so your active organization comes first.
• Clearer sandbox egress blocking messages — When sandbox code is blocked from reaching an external host, it now receives a clear explanation of why the request was denied.
• Slack cancellation attribution — Cancelling a run from Slack now shows who stopped it, in both the original message and the thread.
• Teams AI-generated content labeling — Messages the bot posts to Microsoft Teams are now labeled as AI-generated content.
• Kimi K3 model — Kimi K3 is now available as a model option in chat through Fireworks, joining the existing Claude, GPT, and Kimi families in the model picker.
• Increased permission granularity for Observability access — Access to Observability dashboards can now be granted to non-admin members who hold the required permissions.
• Folder deep links for dashboards — Dashboard folders now have their own URLs, so you can link straight to a folder and the breadcrumb reflects where you are.
• Zoom controls in the image viewer — The artifact image viewer now has zoom controls for inspecting charts and images closely.
• Settings management in the SDK — The SDK adds settings and organization management, so organization settings can be read and updated programmatically.
• Sidebar bookmarks — A new Bookmarks section in the sidebar lets you pin chats and other items you return to often; bookmarks are saved with your account.
• Admin-only Ontology folders — Ontology folders can now be marked admin-only, restricting their contents to administrators.
• Organization-wide sharing controls — Administrators can now disable sharing functionality across their organization.
• Failover on stalled model responses — Stalled model responses are now detected mid-stream and retried against the backup provider, so chats recover instead of hanging.
• Table previews for all SQL connectors — The table preview on connector pages now works across every SQL connector type.
• Usage heatmap in Observability — The Observability overview adds a weekday-by-hour heatmap showing when your organization uses TextQL most.
• Sandbox egress rate limiting — Sandbox network egress is now rate-limited per destination host, containing runaway code that floods external services.
• Faster Tableau introspection — Tableau introspection now runs in parallel and reuses cached images, so large Tableau sites sync faster.
• Custom API connector connection testing — The custom API connector form now runs a prerequisite-aware Test Connection and shows the result before you save.
• UI refinements — Various UI refinements across the app, including font sizes, chat rendering, and the sidebar.
• Values file generator for self-hosted installs — The Helm chart now ships a gen-values.sh helper that generates a starter values file for a new deployment.
• Cluster-scoped resource opt-outs — Self-hosted deployments can now disable the chart’s cluster-scoped PriorityClasses from the values file — or point placeholder capacity pods at an existing priority class — and the VPC CNI ConfigMap toggle is now honored on EKS Auto Mode clusters.
• Sandbox storage improvements for FSx ONTAP deployments — Self-hosted deployments using FSx for NetApp ONTAP get faster and more reliable sandbox storage provisioning.

​

BigQuery Workload Identity Federation

​

Thread costs on the billed basis

​

Required connector credential encryption

• Access control for Tableau datasets — Datasets created from a Tableau connector now enforce object-level access control from the moment they are created, and each grant is recorded in the audit log, bringing them in line with the access control already applied to other datasets.
• Improved sandbox DNS egress — Self-hosted deployments get more reliable sandbox DNS resolution, including a new option to route sandbox DNS egress through the in-cluster DNS service for clusters where a fixed DNS service IP does not work.

​

Scoped API access keys

​

Power BI row-level security for end users

​

Expanded audit logging

​

Merge conflict resolution for Ontology changes

• Tableau embeds attach the Ontology automatically — Tableau embed URLs can now enable the Ontology for all connector datasources.
• Org settings changes recorded as diffs — Audit entries for organization settings changes now record the exact before-and-after value of each changed field and render them as a from → to diff.
• Configurable service account annotations — Self-hosted deployments can now set annotations on the Kubernetes service accounts the chart creates and override each service account’s name or disable its creation, so cluster identities such as IRSA or Workload Identity can be bound to TextQL’s workloads.
• Custom sidecar and init containers — Self-hosted deployments can now append custom sidecar and init containers to TextQL’s pods through per-service extraContainers and extraInitContainers values, for log shippers, metrics exporters, credential bootstrappers, and similar.
• Sonnet 4.6 deprecation — Claude Sonnet 4.6 has been removed from the selectable model catalog and marked deprecated. Chats and defaults still on Sonnet 4.6 should move to a current model such as Claude Sonnet 5.
• Custom Tableau connector resources — Self-hosted deployments can now override the CPU and memory requests and limits for the Tableau connector from the values file.
• Chargeback for usage costs (Beta) — Administrators can now split an organization’s usage bill across internal teams with configurable bill lines. Team rosters update automatically as people are hired, offboarded, or change roles; past billing periods stay frozen and reproducible; and anyone who matches more than one line is flagged for one-click resolution rather than guessed. Includes what-if previews and CSV export.
• Revert approved Ontology changes — Approved changes in Ontology Reviews now have a Revert button that opens the inverse change as a new review.
• Progressive results in batch chat cells — When a chat runs cells in parallel, each result now streams in as it completes instead of appearing all at once.
• Streamed cell events in the chat API — The v2 chat streaming API now emits executable cell events, and generated assets are linked to the message and cell that produced them.
• Built-in skills — Organizations now get built-in skills — including a built-in documentation skill — alongside the skills they create themselves. When a built-in and an org-created skill share a trigger, the org-created skill takes precedence.
• Configurable Python execution timeout — Self-hosted deployments can cap how long a single sandbox Python execution may run; executions that exceed the limit are stopped with a clear timeout error.
• Helm chart version in settings — The Security settings page now shows the deployed Helm chart version, so administrators can confirm which platform release their deployment is running.
• Lower storage use for chat working files — Chats now use roughly half as much working storage: per-chat file storage is provisioned only when a chat actually needs it, rather than up front for every chat.
• Role management in the v2 REST API — The v2 REST API adds endpoints to create and update roles, along with a granular role-permission resource for reading and setting the individual permissions on a role, so roles can be provisioned and adjusted programmatically.
• Ontology library files in the v2 files API — The v2 files API now lists and downloads files from the Ontology library, matching the in-app file browser, with the same access-control and ownership gating applied.
• AWS CodeCommit git sync for Ontology — Ontology git sync now connects to AWS CodeCommit natively using an IAM role, so deployments on AWS can keep their Ontology in CodeCommit without managing separate git credentials.
• Research reports honor the requested document format — When you ask for a research report in a specific document format, Ana now delivers it in that format instead of always producing a PDF.
• Configurable sandbox worker directory retention — Self-hosted deployments can now configure how long sandbox worker directories are retained, giving operators control over scratch-space cleanup timing.

​

GPT-5.6 model family

​

Desktop app tabs and multi-window

​

Connection diagnostics for restrictive networks

• Connector access management in the v2 REST API — The v2 REST API adds endpoints to read and replace which members and roles can access a connector, so connector permissions can be managed programmatically alongside the rest of the API.
• Postgres password from AWS Secrets Manager — PostgreSQL connectors can now source their password from AWS Secrets Manager, so the credential is resolved from your secrets store at connection time instead of being stored on the connector.
• Playbook output gated on connector access — Playbook reports are now visible only to members who have access to the connectors behind them, so sharing a playbook no longer exposes output built on connectors the viewer cannot reach.
• Persistent Power BI and Tableau selections — The Power BI workspace and reports and the Tableau dataset you attach to a chat now persist by default, carrying across turns and into playbooks created from the chat instead of needing to be reselected.
• Concurrent multi-organization sessions — Members who belong to more than one organization can now stay signed into several at once, with each browser tab pinned to its own organization instead of one active org shared across every tab.
• Encrypted OIDC and OAuth secrets at rest — OIDC and API OAuth client secrets are now encrypted at rest and transparently decrypted on read, with a one-time automatic backfill that encrypts any existing secrets on upgrade.
• Chat drafts — Unsent chat messages are now saved as drafts and restored when you return to a conversation, so switching between chats no longer loses what you were typing.
• People analytics in observability — Observability adds a People view with active-people trends, an engagement spectrum, and access-method breakdowns, plus custom start and end date-range filtering across the observability dashboards.
• Dashboard list-view actions — The dashboard list view gains a More actions menu — open in a new tab, duplicate, and move to a folder — with each option shown based on your permissions.
• Ontology Owners subtab — Code owners move into Ontology as a dedicated Owners subtab, and changes that touch owned files now notify the relevant owners for review.
• Workspace and asset endpoints in the v2 REST API — The v2 REST API adds endpoints to manage workspace members, roles, and API keys, plus chat asset and cell endpoints for parity with the app.
• Faster dashboard source execution — Dashboard Python data sources now run in parallel according to their dependencies, so dashboards with independent sources refresh faster.
• Dynamic slow-query warnings — Slow-query warnings now use a dynamic p90 threshold based on each connector’s recent query timings, so the warning reflects what is actually slow for your data sources.
• Compute functions return tabular data — Compute functions that return dataframes now surface as rows in chat instead of raw text representations, and the per-chat compute function limit was raised to 1,000.

​

Claude Sonnet 5 model

​

MongoDB connector

• Bedrock console proxy for Anthropic models — Self-hosted deployments can now route Anthropic model traffic through the TextQL console proxy over Bedrock, including as an automatic backup provider that takes over when the primary Anthropic endpoint is unavailable.
• Packages settings gated on read permission — The organization packages settings are now gated behind the packages:read permission, hiding package management from members who lack access.
• Monthly billing aligned to the first of the month — Usage billing periods now start on the first of each calendar month, giving every organization a consistent monthly billing cycle.
• Opus 4.7 and Kimi K2.5 deprecation — Claude Opus 4.7 and Kimi K2.5 are now deprecated and reach end-of-life on July 23, 2026. Playbooks, organization defaults, and active chats still on these models migrate automatically to Opus 4.8 and Kimi K2.6, and administrators receive advance warning emails before the models are removed.
• Sandbox scratch volume failover — Self-hosted deployments can now fail sandbox scratch storage over to a dedicated scratch volume when the primary volume runs out of space, replacing the previous snapshot-copy approach for more reliable out-of-volume recovery.

​

Support of custom gateway when using Anthropic models

​

Per-member Microsoft Entra ID OAuth for SQL Server and Synapse

​

Google Vertex AI model provider

• Self-managed Kubernetes secrets mode — A new secretsMode: "none" lets operators manage the chart’s Kubernetes Secrets entirely themselves, instead of having the chart render them.
• New chart flags to disable k8s CRDs and use Ingress in GKE — New chart options let self-hosted deployments fully disable Istio, skip Gateway API CRDs when the gateway is turned off, and use legacy Ingress on GKE.
• Configurable asset URL expiry — Administrators can now configure how long generated asset URLs — such as shared images and previews — stay valid, defaulting to one day.
• Ontology change review in the v2 REST API — The v2 REST API adds endpoints to list, get, approve, deny, and restore Ontology changes. The previous “patches” terminology is now “changes” across these endpoints.
• Importable library subdirectory modules — Python modules stored in subdirectories of the Ontology library can now be imported from the sandbox.
• Hide the desktop app page for branded deployments — When organization branding is enabled, the desktop app download page is hidden so white-labeled deployments stay on-brand.
• Per-member default model and fast mode — Each member can now set their own default model and turn on fast mode for new chats, layered on top of the existing role, org, and system defaults.
• Model selection in the v2 chat API — The v2 chat API now accepts an explicit model parameter, so programmatic chats can choose which model to run.
• Ontology building methodology — Organizations and individual members can now choose how Ana builds ontology, with a configurable default methodology and a chat-mode summary of the approach in use.
• Token usage for bring-your-own-key models — Chats running on a bring-your-own-key model now show token usage, so you can track consumption against your own provider account.

​

Citation lineage

​

Connector explore page

​

Dataset access control

• Chat citations — Inline source citations appear alongside Ana’s answers, linking each statement back to the underlying data and documents.
• Refreshed tables across the app — Tables and lists throughout the product share a redesigned experience with inline filtering, sorting, pagination, resizable columns, and saved views — applied consistently across members, models, packages, playbooks, and more.
• MCP server management — Settings now has a redesigned page for connecting and managing external MCP servers, with a clearer add/edit form and validation.
• Connector discovery over MCP — Ana’s MCP server adds a list_connectors tool, so connected clients can discover which connectors a deployment has available.
• Save playbooks as configuration files — An existing playbook can now be saved as a configuration file in the Ontology library, bringing it under version control alongside config-defined playbooks.
• HubSpot connector — A new first-party HubSpot API connector lets Ana pull CRM data — contacts, companies, and deals — into the Python sandbox with guided authentication.
• pip extras in custom package installs — Custom Python package installs now accept pip extras such as sqlglot[rs], so packages that ship optional feature sets install correctly.

​

Ramp, ElevenLabs, Apollo, Pylon, and Mercury API connectors

​

Claude Fable 5 model

​

Cloudflare and SendGrid API connectors

​

Configurable SQL query timeouts

​

Hide non-ZDR models when data retention is disabled

​

HEIC image support

​

Connector management in the v2 REST API

​

Multi-approval for Ontology patches

​

New API connectors

​

Audio and video file previews

• FSx snapshot storage routing — On FSx ONTAP deployments, new Helm values can route scheduled workloads (such as playbook schedules) to snapshot copies instead of FlexClones and mount dashboards on read-only snapshots, preserving clone capacity for interactive chats.
• Istio toggle for Helm deployments — A new global.istio.enabled value (default true) controls whether Istio resources such as authorization policies are rendered, for clusters that don’t run Istio or manage their mesh externally.
• Clickable links in CSV previews — HTTP and HTTPS values in CSV previews now render as clickable links that open in a new tab.
• Desktop app automatic updates — The TextQL desktop app now checks for updates automatically and adds a Check for Updates menu item, with update artifacts served from your deployment.
• Live dashboard content updates — Dashboard content edits now push to anyone currently viewing the dashboard, so live viewers see changes without reloading.
• Per-connector database session identity — Database connectors can now pass the authenticated user’s identity into the database session, so queries are attributed to the acting user in your warehouse’s session metadata and audit logs.
• Cell response ratings — Thumbs-up and thumbs-down controls on chat cells let you rate Ana’s responses, capturing feedback for quality tracking.

​

Mid-conversation steering

​

Edit dashboard code and sources inline

​

Capabilities settings redesign

​

Distributed compute engine

​

Ana Claude Code plugin

• Resumable chat streaming — Live chat updates now resume from a saved cursor with periodic heartbeats and automatic reconnect, keeping streams reliable across compute replicas.
• Distributed sandbox pool — Sandbox workers are now coordinated through a shared distributed pool, with improved worker lifecycle handling and orphan cleanup for multi-replica deployments.
• Library skills via slash command — Skills stored in the org Library can now be invoked by typing /<name> directly in the chat composer.
• Word document uploads — .docx and .docm files can now be uploaded in chat and playbooks for analysis.
• PowerPoint uploads — .pptx and .pptm files can now be uploaded and manipulated in chat via python-pptx.
• Snowflake optional database — Snowflake connectors now support account-wide object discovery when no database is specified.
• Ontology patch revision history — A revisions dropdown lets reviewers browse and compare historical versions of a context patch.
• Bedrock per-user audit attribution — Each AWS Bedrock call is now tagged with the actor’s email, so AI usage audit logs attribute activity at the user level.
• Email tool access control — Admins can now enable or disable the Email tool org-wide from Tool Access Control settings.

​

TQL frontmatter in tql files

​

PowerBI preconfiguration via embed URL

​

Ana as an MCP server

​

MCP streaming responses and inline previews

​

Interactive ECharts visualizations

​

Library TQL data source for dashboards

​

Ontology auto-approve rules

​

OIDC identity provider

​

TextQL Doctor diagnostics

​

Language adherence

​

Unified Ontology surface

​

Ontology relationship graph redesign

​

Microsoft Teams integration

​

Power BI per-member OAuth

​

Firebolt connector

​

Observability export to S3

​

Cerebras LLM provider

• Chat input and conversation polish — The chat input box gets aesthetic refinements, messages from other users now show attribution with name and avatar, and consecutive turns from the same author are visually stacked.
• Auto-attach select all — A “Select all visible” checkbox is now available in the Auto Attach file picker.
• Paginated patch reviews — Patch reviews are now paginated per status tab (Open, Draft, Approved, Denied), with server-provided counts shown as badges.
• Cross-domain email allowlist toggle — A new Helm toggle lets administrators restrict cross-domain email allowlisting in OIDC authentication.
• Library plan-first git sync — Git sync now shows a merge plan up front, covering additions, conflicts, and unrelated-history warnings, so admins can preview changes before they land.
• Ontology settings section — A dedicated Ontology section in Settings adds a Context Patch Auto-Approve tab alongside per-org configuration options.
• Ontology sync run tracking — Git sync events are now tracked as discrete objects, enabling precise notification routing and easier conflict resolution.
• Ontology PDF and image migration — Legacy document and image datasets can now be migrated into Ontology directly from the UI.
• Ontology GitHub App connect flow — GitHub App installation now uses an OAuth-first PKCE redirect flow, and install results are preserved across redirects.
• Ontology reviews split view — The Reviews tab now separates patches into Open and Closed (Approved or Denied) with a refinement filter, and closed patches sort by review time.
• Ontology new file highlighting — Newly added files are now visually highlighted in the file tree.
• Playbook connector inheritance — Playbooks now inherit the active connectors, Power BI workspace, and Tableau dataset selections from the chat they were created in.
• Plain-English role editor — Permission labels in the role editor are rewritten in plain English with clear access boundaries, billing:read and usage:read are now visually distinct, and the Bulk Role Assignment modal is unfrozen.
• Email domain enforcement — Member invite and notification emails are now validated against the organization’s allowed domain list.
• Editable Python package versions — Org-installed packages no longer conflict with default sandbox packages, and affected deployments can edit package versions directly.
• SCIM and OIDC identity merge — OAuth login now detects email collisions and attempts reconciliation, while SCIM provisioning heals email mismatches and migrates associated identity and membership data.
• Safe iframe embedding — Pages can now be embedded in iframes safely, without redirect interference.
• Custom documentation URL — Organizations can set a custom documentation URL in their theme settings, replacing the default docs link throughout the product.

​

Asset origin restrictions and Content Security Policies

​

Rich-text editing for Ontology markdown

​

Insert connectors and files as chat chips

​

Expanded Ontology git providers

​

REST API v2 endpoints

​

Per-member OAuth for Snowflake and Databricks ontology

​

Opt-in email tool with recipient lists

​

Sandboxed PDF processing

• Context page refresh on role changes — The context page now refetches library files, permission gates, and review state whenever you assume or clear a role, preventing stale listings and outdated write buttons.
• Paginated chat listing endpoint — A new GET /v2/chats endpoint lists chats with pagination, search, sorting, and an is_running status field.
• Per-viewer dashboard breakdown popover — The views and viewers stat in the dashboard header is now clickable, opening a popover with a per-viewer breakdown.
• Org defaults for dashboard output and private playbooks — New org-level settings let you make dashboard mode the default output format in chat and set playbooks to private by default from the Security tab.
• Ontology enabled by default with seeded connectors — Ontology is now on by default for new orgs, which are also seeded with example connectors to get started faster.
• Fast mode for Anthropic Opus 4.7 — Fast mode is now available for Anthropic Opus 4.7, speeding up inference on that model.
• Delete playbook from detail page — You can now delete a playbook directly from the … dropdown on the playbook detail page, with a confirmation modal to prevent accidental removal.
• Per-source dashboard cache invalidation — Dashboards now invalidate query caches on a per-source basis, so refreshing one data source no longer clears the rest.
• Bedrock STS role assumption — Bedrock now supports STS role assumption with a configurable role ARN and external ID, enabling cross-account Bedrock access.
• Configurable proxy trusted-host allowlist — A configurable trusted-host allowlist lets private resolved IPs for designated hosts pass outbound request validation.
• Unified default model resolution — Chats now resolve their default model in a consistent order: role default, then org default, then system default.
• Patch cell UX refinements — Patch cells now clamp long descriptions with Show more and Show less, scope markdown heading sizes, add a thin custom scrollbar to file lists, and include an Open in Reviews footer link.

​

File uploads in chat and stream APIs

• Redesigned share modal with airlock preview — The share modal is rebuilt with an airlock-style preview and hardened permission controls for safer sharing.
• Automatic ontology migration — Legacy contexts now migrate automatically to the current Ontology, with git sync improvements, owners validation with clear error messages, and auto-attach refinements.

​

GPT-5.5 and Kimi K2.6 models

​

SAP HANA support

​

Expanded connector authentication

​

Ontology git sync

• Fast mode inference — Fast mode inference is now supported for faster responses.
• SCIM group linking to system roles — SCIM now fixes Okta group push and lets you link SCIM groups directly to system roles.
• OIDC single-tenant role sync — OIDC now correctly syncs roles in single-tenant deployments, with an improved environment configuration UI.
• Self-healing dashboard workers — Dashboards now auto-respawn unhealthy workers, drop the automatic LIMIT from queries, run Python data sources in parallel, persist sandbox state with configurable retention, and flush globals atomically on hot refresh.
• Playbook owner failure alerts — Playbooks now notify their owner when a connector fails, with bounded retries before alerting.
• Tool-level RBAC enforcement — RBAC is now enforced at the tool level, with fixed assume-roles enforcement and locked models shown in the picker with a role-restriction tooltip.

​

Dashboards engine rebuild

​

Ontology library redesign

​

Per-user MCP OAuth tokens

• Redesigned assume-roles experience — Assuming a role now uses a redesigned sidebar UI and modal, making it clearer which role you are acting as and how to switch.
• Mark threads as unread — The thread action menu in the sidebar now includes a “Mark as unread” option so you can flag conversations to revisit later.
• Markdown previews in the artifact drawer — The artifact drawer now renders Markdown previews, so you can read formatted content without leaving the drawer.
• Connector UI gated on connector write permission — The connector management UI is now gated behind the connector:write permission, hiding edit controls from members who lack access.
• Observability billing granularity — Observability now reports billing data at a finer granularity for more precise usage tracking.
• TLS 1.2 and 1.3 enforcement — Connections are now restricted to TLS 1.2 and 1.3 only, and several core libraries have been upgraded to strengthen security.
• Automated Helm chart releases — The Helm chart now ships with an automated changelog and Semver release conventions, streamlining the upgrade process for each new release.
• Slack sender names and View in App — Ana now receives sender names in Slack messages for clearer attribution, and the “View in App” button has been restored and fixed across all channel types.
• Granular per-thread sharing controls — Thread sharing now offers granular per-thread controls, letting you decide exactly who can access each conversation.
• Tool restriction controls and admin override — Tool restrictions gain improved controls with an admin override, and tool-level access is now enforced through RBAC.
• Pause playbooks from the editor — Playbooks can now be paused via the editor tool, and playbooks created in chat are now visible to their creator.
• Copy artifact filenames — A copy button has been added to artifact filenames for quick reuse.
• Ontology file API — Ontology now exposes a file-level CRUD API for programmatic create, read, update, and delete of individual files.
• Usage and billing sidebar permission gating — The usage and billing sidebar entries are now hidden for members who lack the required permissions.
• Org logo removal and theme editor polish — Settings now support removing the org logo, alongside theme editor refinements and context list cleanup.