• Retool 4.0.9
• Retool 3.334.27

Update your Retool instance to apply the latest bug fixes and security patches.

Organization admins can now add shared building context that applies to all apps built with the new app builder. Building context is applied as custom instructions in the system prompt when the user makes any changes via prompting in the Chat tab, similar to the way AGENTS.md files work. Building context is valuable for defining design practices, coding conventions, data usage recommendations, and other guidelines across your organization.

To add shared context, navigate to Settings > Building context. Add your instructions in Markdown format, and click Publish to apply your changes to all apps.

Building context applies to all apps in your organization. If you have Spaces enabled, it applies to all apps in your space.

Admins on the Enterprise plan can now complete each step in the Get started section of the Overview page using guided step-by-step wizards instead of navigating through separate Settings pages to complete configuration.

You can now directly configure from the Overview page:

• SSO
• Resources
• Source control
• Spaces
• Permissions

The Get started section is aimed at providing a better onboarding experience for admins of new organizations, and will help identify what configurations still need to be set up for admins or existing organizations. For example, setting up spaces walks you through choosing custom spaces or a Dev/Staging/Prod environment split, naming and configuring each space, and optionally copying over your existing SSO settings, before creating every space at once.

The Overview page also includes an Action center that contains important notifications and pending join requests, suggested users, and seat upgrade requests, so admins can act on what needs attention, as well an at-a-glance overview of your organization stats, such as total users, apps, workflows, and AI credit usage.

Retool introduced several features to help Enterprise organizations manage AI token spend when using their own API key for AI resources.

Use the new Get BYOK AI token usage endpoint to measure the number of tokens consumed for each AI resource that uses your own key. You can view the number of tokens consumed by resource, user, and surface area.

In addition, you can also view BYOK AI token usage in Settings. Navigate to the Usage Analytics page, and click the AI tab. You can filter AI usage by model, user, and feature.

Learn more about credit and token monitoring.

The app builder now supports multiple chat conversations (threads) working on the same branch rather than a single thread per branch.

A thread is a single chat conversation with the agent in the Chat tab. Threads are intended to help you keep your work organized by task or theme. For example, use one thread for updating your app theme, and another thread for editing a chart on that page. Manage threads from the Chat tab.

A branch is a set of changes to your app, associated with an app preview, and with its own version history. A branch is the unit of work that you publish, and you create a new branch to begin a distinct line of work. For example, create a new branch when you want to change the resources that your app uses, or when you want to overhaul a page. Manage branches from the Version history tab in the navbar.

When using Source Control, branches in the protected app builder map to branches in your external git repository.

This deprecation will first take effect on cloud instances on August 24, 2026. It will then take effect in the next edge and stable releases that follow.

Version 3.0 has been available since February 2, 2026 for cloud instances and the 3.334 stable release. If you haven't intentionally created a resource on an older integration version, your resource is likely already on version 3.0 and requires no changes.

To upgrade an existing resource, open its settings from the Resources page, change Connector version to Version 3.0, and save your changes.

Versions 1.0 and 2.0 will be removed entirely from cloud instances in Q4 2026, followed by the subsequent edge and stable releases. After that, apps, workflows, and queries that depend on Microsoft SQL resources still using version 1.0 or 2.0 will stop working.

For Enterprise organizations that use Source Control to protect apps, you can now use the app builder to check out a branch that you created outside of Retool. This enables you to transition your changes from a local development environment to the app builder. This can be useful for visually validating your changes in the preview canvas.

When prompting in the Chat tab of the app builder, the agent asks clarifying questions to better understand your intent and create your desired outcome. The agent can ask multiple-choice or open-ended questions.

You can now build apps with more AI models: Claude Sonnet 5, the GPT-5.6 models (Sol, Terra, and Luna), and Claude Fable 5. Choose a model for each thread in the app builder's Chat tab. Admins can set the organization's default app building provider and model in the AI settings.

Claude Sonnet 5 can be used on paid plans with a Retool-managed key or your own key. The GPT-5.6 models and Claude Fable 5 require you to bring your own key, which is available on the Enterprise plan.

• Retool 4.0.7
• Retool 3.334.25
• Retool 3.334.24
• Retool 3.300.34

Update your Retool instance to apply the latest bug fixes and security patches.

You can now upload files to be used as assets in your app through the Chat tab in the app builder. Previously, uploaded files could only be used as context for the agent.

Common use cases for uploaded files as assets include:

• Embedding PDFs.
• Adding a company logo to the app header.
• Presenting images within the app.

• Retool 4.0.6
• Retool 3.334.23

Update your Retool instance to apply the latest bug fixes and security patches.

• Retool 4.0.5
• Retool 3.334.22
• Retool 3.300.33

Update your Retool instance to apply the latest bug fixes and security patches.

Retool now supports object roles—a new role type that grants groups Use, Edit, or Own access to specific apps, workflows, resources, and agents. Object roles are separate from organization roles, which control access to admin settings like billing and SSO.

When you create an object role, you set an access level for each object type and choose how the role applies:

• Universal access—The role applies to all current and future objects of that type across the organization.
• Individual access—Access is scoped to specific objects or folders, which you define when assigning the role to a group.

Object roles are assigned to groups from the Groups page. Once assigned, all members of the group inherit the role's permissions. You can view a group's or user's full object-level access from the Object permissions tab on their detail page in Settings.

Updates to organization roles​

As part of this launch, organization roles have been updated to cleanly separate admin settings access from object-level access. The Create Role button on the Roles & Permissions page is now a dropdown where you choose between creating an object role or an organization role. A filter control on the roles list lets you view all roles, object roles only, or organization roles only.

To get started:

• Object roles—Understand how object roles work, including universal vs. individual access and folder inheritance.
• Create an object role—Step-by-step instructions for creating and managing object roles.
• Organization roles—Updated UI for managing organization roles, including a new role type selector and filter controls on the Roles & Permissions page.
• Assign roles to groups—Assign object or organization roles to groups.

Claude Sonnet 5 is now available on paid plans through Anthropic and Amazon Bedrock. It can be used with AI resource queries and Retool Agents.

You can now trigger workflows from functions in the new app builder. Converting classic apps that trigger workflows is now supported as a result.

To trigger a workflow from your app, open the Chat tab and prompt your agent with the workflow's name.

The triggered workflow is run on behalf of the app's authenticated user.

Claude Fable 5 is now available through Anthropic. It can be used with AI resource queries when you connect Anthropic with your own API key.

Who is affected​

Self-hosted deployments using Microsoft SQL Server resources with Connect using Windows Auth enabled and one or more custom entries in Connection options (or equivalent resource JSON) whose keys are not on the allowlist. Windows Authentication is not available on Retool Cloud.

How to check if you are affected before upgrading​

Search your Retool deployment logs (dbconnector / backend) for this exact string from the prior log-only release:

MSSQL Windows Auth ODBC connection string parameter not on allowlist

Each matching log line includes the parameter key (parameterKey in structured logs). Resources that logged this message will fail to connect or save after upgrading until those parameters are removed or replaced.

What you will see after upgrading​

Resource setup or test connection fails with an error like:

Unsupported MSSQL ODBC connection string parameter "<key>". Only a fixed set of ODBC attributes may be supplied via connection params.

Remediation​

1. Open each affected MSSQL Windows Auth resource.
2. Remove unsupported keys from paramsFromConnectionString.
3. Use Retool's built-in resource fields where possible. For example, use SSL/TLS for encryption and certificate verification.
4. If you need an ODBC attribute that is not listed below, contact Retool Support before upgrading.

Allowed paramsFromConnectionString keys​

Security-sensitive attributes (Driver, Encrypt, Trusted_Connection, credentials, Server, Database, and similar) are set by Retool and cannot be supplied via connection params.

Common parameters that are blocked​

• Encryption and certificate trust settings such as Encrypt and TrustServerCertificate — use the resource SSL/TLS settings instead.
• LoginRetryCount / LoginRetryInterval — use ConnectRetryCount / ConnectRetryInterval.
• Credential keys such as Uid, Pwd, User, or Password.
• Keys containing ; or crafted to inject additional ODBC attributes.

• Retool 4.0.4
• Retool 3.334.21

Update your Retool instance to apply the latest bug fixes and security patches.

Classic apps that include custom components and organization-level themes can now be converted to the new app building experience.

To support custom components, the agent investigates the custom component and recreates it in the converted app with as few changes as possible.

To support classic organization-level themes, the agent applies the same style, color, and typography to the app as were represented in the organization-level theme. The agent does not create a new organization-level theme that applies to apps created with the new app builder.

Retool now provides a native integration for Microsoft Graph, the unified API for Microsoft 365 services. You can create a Microsoft Graph resource with OAuth 2.0 or Microsoft Azure Identity authentication to read and manage Entra ID users, mail, calendars, OneDrive and SharePoint files, and Teams messages—all from Retool apps and automations.

Presto resources are now supported by Retool Agents. You can @ tag a Presto resource when building a custom tool to give an agent typed, structured access to your Presto queries alongside your other SQL resources.

Retool now provides a native integration for Snowflake Postgres, Snowflake's PostgreSQL-compatible interface for querying your Snowflake data. You can create a Snowflake Postgres resource to connect over SSL with a CA certificate and run SQL queries to create, read, update, and delete data—all from Retool apps and automations.

Retool now supports publishing apps on custom domains. If you self-host Retool (which inherently uses a custom domain) or use a custom domain on a cloud instance, your apps are published to the domain you define in the following format: https://example.retool.com/rr/app/<appName>.

If your organization uses custom domains, previously-published apps should be republished in order to serve them from the appropriate domain.

Apps published on custom domains are subject to an additional set of limitations that are applied because Retool runs your app inside a sandboxed iframe with allow-same-origin disabled.

• Retool 4.0.3
• Retool 3.334.20

Update your Retool instance to apply the latest bug fixes and security patches.

Admins can now customize the Content Security Policy (CSP) that Retool enforces on apps. Retool applies a strict default policy that restricts which origins an app can load scripts, fonts, images, and other resources from. You can now extend that policy org-wide to allow the additional origins your apps need, or tighten the defaults further.

For example, if custom JavaScript in an app loads a charting library from a CDN such as https://cdn.example.com, the default script-src 'self' policy blocks the script and the app fails to render it. You can now add that origin to script-src so the app can load it without loosening the policy for any other resource.

Configure rules in Settings > App security > Content Security Policy. Changes apply to every app in your organization and are recorded in your audit logs.

For more information, refer to Customize the Content Security Policy for apps.

While prompting from the Chat tab in the new app builder, you can now restore the app to a previous state. Each time the agent finishes making changes, it presents a summary of the changes and a Restore button. Click this button to return your app to the state it was in when the agent finished those changes.

• Retool 4.0.2

Update your Retool instance to apply the latest bug fixes and security patches.

Organization admins on Team and Business plans can now purchase additional AI credit packs directly by clicking on Buy credits from Settings > Plans & Billing > under the new AI Credits tab.

Credit packs are sold in increments of 1,000 credits at $100 per pack. Purchased credits are added to your organization's shared pool and are consumed after your monthly allotment runs out, with the oldest (soonest-expiring) pack used first. Credit packs expire at the end of your next monthly billing cycle (between 30–60 days after purchase), depending on where you are in your billing cycle when you buy them.

• If you are billed monthly, your next billing cycle end date is your expiration date.
• If you are billed annually, your monthly billing date is the same day of the month you originally purchased your plan (e.g., if you purchased an annual plan on April 12, credits expire on the 12th of the following month).

When your organization's credits run out, admins will see a banner prompting them to purchase additional credits or upgrade their plan. Users who are not admins will be directed to contact their admin.

Credit pack purchasing is available on cloud plans using Retool-managed keys. Free plan organizations must upgrade to Team or Business to purchase credit packs. Enterprise customers should contact their account executive.

For more information, refer to the AI credits documentation.

Retool now supports audio and visual browser notifications for app building. If you prompt Retool to build an app and navigate away from the tab, a ping sounds and a red dot appears on the favicon of the tab when you need to return to it. Now, you can multitask and return to the app builder only when your input is required.

This notification occurs at the following key points in the building process:

• The agent needs you to provide input or make a choice (such as selecting a resource).
• The agent needs your approval to run a function.
• The agent is finished building.

To turn off the notification sound, click the Model options selector in the prompting box and toggle off the Sound notifications setting.

What happens when you upgrade​

When you deploy Retool 4.0 stable, the migration runs automatically in the background. In most cases, no action is required.

If the migration fails—even for a single space within your instance—all organization admins will see a notification banner across all settings pages to indicate that the database is in an inconsistent state. This notification includes a link for an admin to trigger the migration again.

The database integrity check can take approximately three hours from upgrade completion. If the check fails, the notification banner is displayed. For larger instances, this check can take up to 15 hours.

If the migration fails​

Should the migration fail, no existing functionality is impacted. In most cases, an admin can trigger the migration again. The option to trigger a migration again is disabled if it is already in progress so it cannot be triggered multiple times.

If re-running does not resolve the issue, contact our support team as soon as possible.

I have a deployment that is not Kubernetes-based (e.g., ECS). Can I upgrade in place?​

Kubernetes with Helm is the only supported deployment path for Retool 4.0 and later. Amazon ECS (Fargate or EC2), bare EC2, Azure VM, Google Compute Engine, and other non-Kubernetes compute are not supported. Retool doesn't test or guarantee upgrade compatibility on these paths.

Migrate to a Kubernetes deployment before upgrading. Retool's Terraform blueprints are the officially supported path for new Kubernetes deployments. Contact your Retool account team to plan the migration. If you're moving from Amazon ECS specifically, refer to Migrate from ECS to Kubernetes for step-by-step instructions.

I'm running Kubernetes with raw manifests. Can I upgrade in place?​

No. Raw Kubernetes manifests are not a supported deployment configuration, and services introduced in Retool 4.0 are shipped and configured through the Retool Helm chart. There is no in-place upgrade path for raw manifest deployments.

You must migrate to a Helm-based deployment before upgrading to Retool 4.0. Retool's Terraform blueprints are the recommended path. If you have an existing Helm deployment, the Helm upgrade guide covers how to add the new services.

Contact your Retool account team if you need migration assistance.

I'm running Docker Compose in production. What should I do?​

Retool does not support Docker Compose for production deployments. The agent sandbox service requires resource isolation and pod-level scheduling that a single-VM stack cannot reliably provide.

If you are using Docker Compose in production, migrate to Kubernetes before upgrading. Refer to Migrate from Docker Compose to Kubernetes for step-by-step instructions.

If you are using Docker Compose for non-production or development purposes, you can upgrade in place. Refer to Upgrade your Docker Compose deployment.

Can I upgrade to Retool 4.0 without enabling the new services?​

Yes. All new services introduced in Retool 4.0 (the agent sandbox, JS executor, MCP server, r2 agent, and git server) are disabled by default in Helm chart version 6.11.4. Upgrading the chart without enabling them is safe and fully backward compatible.

You can enable individual services at any time after upgrading. Refer to the Helm upgrade guide for instructions on enabling each service.

What seccomp profiles do the agent sandbox and js-executor require? Is this more or less secure than privileged mode?​

Both the agent sandbox and js-executor require a custom seccomp profile on each cluster node. The profiles grant only the specific system calls each service needs and do not require CAP_SYS_ADMIN. The agent sandbox does not support privileged mode. The js-executor supports privileged mode as an alternative to the custom seccomp profile, but the custom seccomp profile is recommended.

This is significantly more secure than privileged mode. Customers who previously ran code-executor without privileged mode can apply the same approach for these services.

For the full seccomp profile breakdown and a comparison with code-executor, see Custom code execution security.

My ENCRYPTION_KEY contains non-ASCII characters. Do I need to change it before upgrading?​

Yes. From version 3.332.4, ENCRYPTION_KEY must contain only ASCII characters. If your key contains non-ASCII characters, upgrading without rotating it first will cause decryption failures — look for ERR_OSSL_BAD_DECRYPT in your logs.

Rotate your encryption key before upgrading. Contact your Retool account team if you need assistance with the rotation process.

I use SAML SSO. Are there any new requirements?​

Yes, if your users sign in via SP-initiated SAML (starting the login flow from Retool rather than your IdP dashboard). Retool now binds each login to the AuthnRequest that started it using a short-lived, HTTPS-only cookie. Two requirements apply:

• Retool must be served over HTTPS. Do not enable COOKIE_INSECURE. The cookie is set SameSite=None; Secure, which browsers only return over HTTPS. SP-initiated logins will fail on plain HTTP.
• Use a single consistent hostname. The Assertion Consumer Service (ACS) URL registered in your IdP must match the hostname your users start login from. Standard single-hostname deployments need no change.

Standard IdPs (Okta, Entra ID, OneLogin, ADFS, Ping, Google Workspace) return the required InResponseTo value automatically.

IdP-initiated logins — launching Retool directly from your IdP dashboard — are unaffected. Users must complete a login within 10 minutes of starting it.

To disable this validation: set DISABLE_SAML_INRESPONSETO_VALIDATION=true and restart.

I use Temporal-in-Helm. What do I need to do?​

Temporal-in-Helm has been removed in Retool 4.0. Retool no longer ships a Temporal cluster as part of the Helm chart. You must migrate to an external Temporal provider before or during your upgrade.

Retool supports two options:

• Temporal Cloud (recommended): a fully managed Temporal service. Requires outbound network access to Temporal Cloud egress endpoints on ports 443 and 7233.
• Self-hosted Temporal: an externally managed Temporal cluster you operate. Retool does not provide support for the Temporal cluster itself.

After upgrading to Retool 4.0, an admin user must complete Temporal setup from within Retool: click the Workflows nav item and follow the in-product setup steps. A valid license key is required.

If you have Temporal-in-Helm data (workflow history) you want to preserve, contact your Retool account team before upgrading.

You can now use Retool's MCP server to import React apps directly from your agentic coding environment.

Open a React app, and ask Retool to import the app. Retool guides you through the process of selecting the appropriate resources, and sends you a link to the newly imported app in the app builder. From there, you can make tweaks to the generated app, and securely publish the app using the MCP server or from the app builder.

For new deployments: Retool now provides Terraform blueprints that automatically provision all required AWS infrastructure (VPC, EKS cluster, RDS, S3, load balancer, ACM certificate) and deploy Retool via Helm. This is the recommended path for production.

For existing deployments: The upgrade path depends on how you're currently deployed. New services are disabled by default so you can upgrade the chart first and enable them when ready. Some deployment configurations require migration before upgrading.

In addition, a database migration is performed to prepare for upcoming improvements to organization permissions. This migration does not affect any functionality within this release but any migration issues must be resolved before attempting to upgrade to a future release.

• Retool 4.0 upgrade FAQ
• Permissions database migration in self-hosted Retool 4.0

Retool 4.0 upgrade FAQ​

If you have an existing Retool deployment instance, this FAQ can provide guidance as you prepare an upgrade plan.

I have a deployment that is not Kubernetes-based (e.g., ECS). Can I upgrade in place?​

Kubernetes with Helm is the only supported deployment path for Retool 4.0 and later. Amazon ECS (Fargate or EC2), bare EC2, Azure VM, Google Compute Engine, and other non-Kubernetes compute are not supported. Retool doesn't test or guarantee upgrade compatibility on these paths.

Migrate to a Kubernetes deployment before upgrading. Retool's Terraform blueprints are the officially supported path for new Kubernetes deployments. Contact your Retool account team to plan the migration. If you're moving from Amazon ECS specifically, refer to Migrate from ECS to Kubernetes for step-by-step instructions.

I'm running Kubernetes with raw manifests. Can I upgrade in place?​

No. Raw Kubernetes manifests are not a supported deployment configuration, and services introduced in Retool 4.0 are shipped and configured through the Retool Helm chart. There is no in-place upgrade path for raw manifest deployments.

You must migrate to a Helm-based deployment before upgrading to Retool 4.0. Retool's Terraform blueprints are the recommended path. If you have an existing Helm deployment, the Helm upgrade guide covers how to add the new services.

Contact your Retool account team if you need migration assistance.

I'm running Docker Compose in production. What should I do?​

Retool does not support Docker Compose for production deployments. The agent sandbox service requires resource isolation and pod-level scheduling that a single-VM stack cannot reliably provide.

If you are using Docker Compose in production, migrate to Kubernetes before upgrading. Refer to Migrate from Docker Compose to Kubernetes for step-by-step instructions.

If you are using Docker Compose for non-production or development purposes, you can upgrade in place. Refer to Upgrade your Docker Compose deployment.

Can I upgrade to Retool 4.0 without enabling the new services?​

Yes. All new services introduced in Retool 4.0 (the agent sandbox, JS executor, MCP server, r2 agent, and git server) are disabled by default in Helm chart version 6.11.4. Upgrading the chart without enabling them is safe and fully backward compatible.

You can enable individual services at any time after upgrading. Refer to the Helm upgrade guide for instructions on enabling each service.

What seccomp profiles do the agent sandbox and js-executor require? Is this more or less secure than privileged mode?​

Both the agent sandbox and js-executor require a custom seccomp profile on each cluster node. The profiles grant only the specific system calls each service needs and do not require CAP_SYS_ADMIN. The agent sandbox does not support privileged mode. The js-executor supports privileged mode as an alternative to the custom seccomp profile, but the custom seccomp profile is recommended.

This is significantly more secure than privileged mode. Customers who previously ran code-executor without privileged mode can apply the same approach for these services.

For the full seccomp profile breakdown and a comparison with code-executor, see Custom code execution security.

My ENCRYPTION_KEY contains non-ASCII characters. Do I need to change it before upgrading?​

Yes. From version 3.332.4, ENCRYPTION_KEY must contain only ASCII characters. If your key contains non-ASCII characters, upgrading without rotating it first will cause decryption failures — look for ERR_OSSL_BAD_DECRYPT in your logs.

Rotate your encryption key before upgrading. Contact your Retool account team if you need assistance with the rotation process.

I use SAML SSO. Are there any new requirements?​

Yes, if your users sign in via SP-initiated SAML (starting the login flow from Retool rather than your IdP dashboard). Retool now binds each login to the AuthnRequest that started it using a short-lived, HTTPS-only cookie. Two requirements apply:

• Retool must be served over HTTPS. Do not enable COOKIE_INSECURE. The cookie is set SameSite=None; Secure, which browsers only return over HTTPS. SP-initiated logins will fail on plain HTTP.
• Use a single consistent hostname. The Assertion Consumer Service (ACS) URL registered in your IdP must match the hostname your users start login from. Standard single-hostname deployments need no change.

Standard IdPs (Okta, Entra ID, OneLogin, ADFS, Ping, Google Workspace) return the required InResponseTo value automatically.

IdP-initiated logins — launching Retool directly from your IdP dashboard — are unaffected. Users must complete a login within 10 minutes of starting it.

To disable this validation: set DISABLE_SAML_INRESPONSETO_VALIDATION=true and restart.

I use Temporal-in-Helm. What do I need to do?​

Temporal-in-Helm has been removed in Retool 4.0. Retool no longer ships a Temporal cluster as part of the Helm chart. You must migrate to an external Temporal provider before or during your upgrade.

Retool supports two options:

• Temporal Cloud (recommended): a fully managed Temporal service. Requires outbound network access to Temporal Cloud egress endpoints on ports 443 and 7233.
• Self-hosted Temporal: an externally managed Temporal cluster you operate. Retool does not provide support for the Temporal cluster itself.

After upgrading to Retool 4.0, an admin user must complete Temporal setup from within Retool: click the Workflows nav item and follow the in-product setup steps. A valid license key is required.

If you have Temporal-in-Helm data (workflow history) you want to preserve, contact your Retool account team before upgrading.

Permissions database migration in self-hosted Retool 4.0​

Self-hosted Retool 4.0 includes an automatic database migration that prepares your instance for upcoming improvements to how Retool handles organization permissions. This migration runs in the background during deployment and does not affect any functionality.

What happens when you upgrade​

When you deploy Retool 4.0 stable, the migration runs automatically in the background. In most cases, no action is required.

If the migration fails—even for a single space within your instance—all organization admins will see a notification banner across all settings pages to indicate that the database is in an inconsistent state. This notification includes a link for an admin to trigger the migration again.

The database integrity check can take approximately three hours from upgrade completion. If the check fails, the notification banner is displayed. For larger instances, this check can take up to 15 hours.

If the migration fails​

Should the migration fail, no existing functionality is impacted. In most cases, an admin can trigger the migration again. The option to trigger a migration again is disabled if it is already in progress so it cannot be triggered multiple times.

If re-running does not resolve the issue, contact our support team as soon as possible.

Self-hosted admins now see an Update available banner on the Retool home page when a newer release or patch update is available for their instance.

The banner shows the available version and links directly to the relevant release notes. Admins can dismiss each notification individually — dismissals are remembered per version.

Two notification tiers appear based on what's available:

• New release — shown when a new minor or major release is available.
• New patch — shown when a patch update is available for the current release.

On airgapped instances, no outbound version check is made and the banner does not appear.

The Settings navigation is reorganized into clearer, task-based groups so you can find what you need more quickly.

Settings are now grouped under the following sections: Management, Monitoring, Permissions, Authentication, Features, and Customization. For example, Users, Groups, Roles, and User attributes are grouped under Permissions, while Single sign-on (SSO) and IAM credentials are grouped under Authentication.

Admins can now use the Overview page in Settings to set up their Retool organization and respond to pending user requests.

The Get started section guides you through configuring the core areas of your organization, including single sign-on (SSO), resources, permissions, spaces, source control, and the Retool API.

Retool marks each step as complete once you configure it, and you can mark any step that does not apply as not relevant. The module is hidden once you complete the Get started steps.

The Overview also surfaces pending join requests and suggested users, so you can approve new members without leaving the page.

• Retool 3.334.17
• Retool 3.300.32

Update your Retool instance to apply the latest bug fixes and security patches.

Retool's new app builder now supports importing React apps from external sources, such as Replit, Lovable, and Claude Code, for further refinement and development in Retool.

To import your React app in Retool, generate a .zip file of the code, and select Import React code from the app builder. Learn more about how it works.

Apps created with the new app builder can now be protected and checked into your chosen Source Control Manager (SCM). Source Control lets organizations manage changes using remote SCM providers GitHub, GitLab, AWS CodeCommit, Bitbucket, and Azure Repos. Using this distributed approach, your users can:

• Prevent unwanted changes to apps.
• Work collaboratively and methodically through reviews.
• Edit React code from your preferred development environment.

To get started, first protect your app. Then you can create, publish, and tag new versions.

Builders on cloud instances can now use Retool's MCP server to build apps. Apps are built using React and use Retool's updated app builder. Connect the MCP server to Claude, ChatGPT, Codex, Cursor, Kiro, or another agentic coding environment, and describe the app you want to build. Retool's building agent generates the app and returns a preview link. Publish and manage the app from the app builder.

Beyond initial generation, you can also use the MCP server to:

• Continue building or iterating on an existing app.
• Monitor active builds and view past agent activity.
• Review function runs that require human approval.
• Inspect or read the files of an existing app.
• Cancel a failed or in-progress build.

App building tools require the user to be a builder, and the builder must authorize the mcp:write scope. Refer to the tools reference for the full list.

Claude Opus 4.8 is now available on Retool Cloud through Anthropic and Amazon Bedrock. It can be used with AI resource queries, with Retool Agents, and in Assist. Opus models require you to bring your own key for AI resource queries and Assist; Retool Agents can use Opus with a Retool-managed key. Support for self-hosted Retool is coming in an upcoming release.

The app builder includes:

• A Chat tab where you describe changes in natural language and an AI agent plans and executes them, with file uploads and per-thread model selection.
• A Data tab that shows the resources connected to your app and the functions that interact with them, with optional approval gates on writes.
• A Code tab that lets you view and edit every file your app uses.
• Support for organization themes, third-party npm packages, and publishing and version history.

Apps run on React 19 and a curated set of supporting libraries.

Admins can use the configuration guide to set up their organization to use the new app builder.

• Retool 3.334.16
• Retool 3.300.31

Update your Retool instance to apply the latest bug fixes and security patches.

• Retool 3.334.15
• Retool 3.334.14
• Retool 3.300.30

Update your Retool instance to apply the latest bug fixes and security patches.

Organization admins in the admin space can now view audit logs from all spaces on the same instance directly from the Audit logs page. Use the Space filter to view events from a specific child space, or select all spaces to view events from every space at once. When viewing events across spaces, each entry includes a tag indicating which space it belongs to.

Users in child spaces continue to see events from their own space only, and downloads remain scoped to the current space.

For more information, refer to View audit logs across spaces.

• Retool 3.334.13
• Retool 3.300.29

Update your Retool instance to apply the latest bug fixes and security patches.

The new Analytics page gives you visibility into workflow health and activity across your organization.

From the workflows landing page, select Analytics to access two views:

• All workflows: Aggregate run counts, failure rates, and resource consumption across every workflow in your organization. Includes a ranked list of your most-run workflows, a Top problem workflows table that surfaces workflows with high failure rates, and resource consumption data for the current month.
• Individual workflow: Drill into a single workflow to review summary stats, run and latency breakdown charts, resource consumption, and a paginated list of recent runs with per-run status and duration.

• Retool 3.334.12
• Retool 3.300.28

Update your Retool instance to apply the latest bug fixes and security patches.

• Retool 3.334.11
• Retool 3.300.27

Update your Retool instance to apply the latest bug fixes and security patches.

Admins can now configure memory limits for workflow code execution at the org level, and workflow editors can override those limits on a per-workflow basis.

• Org-level defaults: In Settings, go to the Advanced section and click Advanced settings to set a default memory limit (MB) that applies to all workflow runs in your organization.
• Workflow-level overrides: Open any workflow and go to Settings to override the org default for that workflow.

When a workflow runs a code block, the executor enforces the most specific limit available (workflow > org > server default). If a block exceeds its limit, it fails immediately with a clear error.

Customers who are not configuring limits see no behavior change — the server default of 2,500 MB memory applies. For customers whose workflows were hitting out-of-memory errors, limits can now be tuned without requiring infrastructure changes.

Gemini 3.1 Pro (Preview), Gemini 3 Flash (Preview), and Gemini 3.1 Flash-Lite (Preview) are now available in Retool through Google. They can be used with AI resource queries.

Gemini 3.1 Pro (Preview) and Gemini 3.5 Flash can now be used to build apps, through both Google and Google Vertex AI. Refer to the AI models reference to see which models support app building.

Retool now provides a native integration for ClickHouse, an open-source column-oriented database designed for real-time analytics. You can create a ClickHouse resource and use it to query analytical data with SQL—including ClickHouse-specific functions and aggregations—build dashboards on live data, and insert records from apps and automations.

• For cloud organizations, support for MongoDB Server 3.4 and earlier has already been removed.
• For self-hosted organizations, support for MongoDB Server 3.4 and earlier will be deprecated in the Q2 2026 stable release. It will be removed in the Q3 2026 stable release.

MongoDB Server 3.4 has been end of life (EOL) since January 2020. We recommend upgrading to a currently supported MongoDB release.

GPT-5.5 and GPT-5.3 Codex are now available in Retool through OpenAI. They can be used with AI resource queries and with Assist. GPT-5.5 is also available for use with Retool Agents.

Retool now provides a native integration for Azure Blob Storage, Microsoft's scalable object storage service. With the Azure Blob Storage resource, you can upload and download files, generate signed URLs for temporary secure access, and copy, delete, and organize objects across containers—all from Retool apps and automations.

Claude Opus 4.7 is now available on Retool Cloud through Anthropic and Amazon Bedrock. It can be used with AI resource queries, with Retool Agents, and in Assist. Opus models require you to bring your own key for AI resource queries and Assist; Retool Agents can use Opus with a Retool-managed key. Support for self-hosted Retool is coming in an upcoming release.

GPT-4 Turbo, GPT-4.1 Nano, and GPT-5.4 are also now available for use with Retool Agents.

You can now select the Python version used by a workflow from the Languages & Libraries tab. Click ... next to Python, select Update version, and choose between Python 3.10 and 3.14.

Python 3.14 does not include built-in libraries. When you upgrade, Retool automatically identifies any built-in libraries your workflow uses and installs them as custom libraries.

GPT Image 2 is now available through OpenAI. It can be used for image generation with AI resource queries.

Retool now supports an MCP server, which enables you to interact with your Retool organization from your chosen agentic environment.

Retool's MCP server currently supports tools that help you manage your organization and its users. For example, you can use the MCP for the following use cases:

• Write queries against resources to power data analysis.
• Bulk-invite users or manage pending invites.
• Audit the users who have access to your organization.
• Inspect organization and resource environment configurations.
• List all connected resources and see their configuration.

Refer to the tool reference for the full list.

Retool is actively adding additional tools that expand the capabilities of the MCP server to include additional Retool functionality, including app building.

What's changing​

New and existing workflows on Python 3.10 will continue to run but they will not be supported. They will not be automatically migrated to a newer version.

How to upgrade existing workflows​

Python 3.14 is rolling out to cloud instances and will be available in an upcoming self-hosted release.

1. Open the workflow and go to the Languages & Libraries tab.
2. Click ... next to Python and select Update version.
3. Choose Python 3.14 and click Apply.

When you upgrade, Retool automatically identifies built-in libraries your workflow uses and installs them as custom libraries. Python 3.14 is mostly backwards-compatible, but Retool recommends publishing a workflow release before upgrading so you can revert if needed.

See Configure Python version for full details on how to upgrade and revert to a previously published release.

Timeline​

• Retool 3.334.8
• Retool 3.300.24
• Retool 3.300.23
• Retool 3.284.29

Update your Retool instance to apply the latest bug fixes and security patches.

• Retool 3.334.7
• Retool 3.300.22

Update your Retool instance to apply the latest bug fixes and security patches.

To use this endpoint, your API token must have the workflows:write scope. The endpoint only supports deleting standard workflows—deleting agents and functions via the API is not supported.

Refer to the Retool API reference for full endpoint details, including request parameters and error responses.

Gemini 3 Pro Image and Gemini 3.1 Flash Image are now available on Retool Cloud through Google. They can be used for image generation with AI resource queries.

Retool now provides a native integration for CockroachDB, a relational database management system. You can create a CockroachDB resource to securely connect to your databases and create apps and automations that use SQL queries to perform create, read, update, and delete operations.

• Retool 3.334.6
• Retool 3.300.21
• Retool 3.284.28

Update your Retool instance to apply the latest bug fixes and security patches.

Retool now supports Google Vertex AI as a new native integration that can be used in AI resource queries.

• Retool 3.334.5
• Retool 3.300.20
• Retool 3.284.27

Update your Retool instance to apply the latest bug fixes and security patches.

App builders can now defer the initialization of modules until they're viewable to improve the initial loading time of larger apps.

When an app is initially loaded, Retool initializes all code, components, and modules. However, a common use case for modules is including them in conditionally hidden frames, and these modules don't need to be loaded when they are still hidden.

Modules now have a new option in the Inspector: [Beta] Defer evaluation until visible. When a “deferred” module is hidden (either ‘hidden’ state is true, or it is in a hidden frame, or otherwise not being rendered), Retool defers the module's initialization. When the module is shown, Retool invokes the initialization procedure that would typically happen during app startup.

This gives builders more flexibility in how components are loaded in their apps, and large apps load more quickly.

• Retool 3.334.4
• Retool 3.300.19
• Retool 3.284.26

Update your Retool instance to apply the latest bug fixes and security patches.

• Retool 3.334.3
• Retool 3.334.2
• Retool 3.300.18
• Retool 3.284.25

Update your Retool instance to apply the latest bug fixes and security patches.

• Improved quality of app generation. Assist has an improved ability to successfully set a wider set of properties across a wider set of components.
• Quicker app generation. Generating an app from scratch is approximately 20% faster.
• Better token efficiency, especially for app editing. Token use has decreased by approximately 40-50%, depending on the change type. Users will notice a decrease in the number of context window issues they encounter.
• Improved support for building forms and using repeatable components inside apps.

Retool now provides a native integration for ServiceNow, an IT service management platform for managing incidents, change requests, service catalog items, and other operational workflows. You can create a resource and write queries to interact with the ServiceNow API.

• Retool 3.334.1
• Retool 3.300.17
• Retool 3.284.24
• Retool 3.253.29

Update your Retool instance to apply the latest bug fixes and security patches.

GPT-5.4 is now available in Retool through OpenAI. It can currently be used with AI actions.

• Retool 3.300.16
• Retool 3.284.23

Update your Retool instance to apply the latest bug fixes and security patches.

Retool has two new improvements to the API:

• A new per-instance API reference is now available at {your-instance}/reference. The reference is available on all cloud instances and served locally by self-hosted deployments within its VPC—no internet connection required. The API reference reflects only the API version running on your instance and always matches what's available to you.
• The API version now tracks the Retool release version. The Retool API version now corresponds to your instance's release version. This makes it easier to track Retool API changes whenever your instance is updated.

Retool now uses a service worker in the browser to cache the application frontend so that pages load faster when you revisit them. The service worker uses a stale-while-revalidate strategy: it serves the previously cached version of a page immediately, then fetches the latest version from Retool in the background. If a newer version is available, Retool automatically refreshes the page so you see the latest changes.

The cache is version-aware and automatically invalidates after a Retool upgrade, so you always end up on the latest version of the platform without needing to clear your browser cache. A hard refresh (Cmd+Shift+R / Ctrl+Shift+R) bypasses the cache and loads the latest version directly.

The service worker is enabled by default on cloud instances and on self-hosted versions 3.334-stable and later. Admins can disable it from Settings > Beta if they need to diagnose page load issues in their organization.