![](\"https://docs.retool.com/assets/images/ask_build-d6ca95f17694370eb3bfae2f24471d4d.png\")
Toggle between Ask and Build mode.
You can now delete workflows programmatically using the DELETE /api/v2/workflows/{workflowId} endpoint in the Retool REST API.
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.
", "url": "https://docs.retool.com/changelog/delete-workflow-api", "title": "Delete workflows with the Retool API", "summary": "A new DELETE endpoint lets you programmatically delete workflows using the Retool REST API.", "date_modified": "2026-04-13T12:00:00.000Z", "tags": [ "API", "Workflows" ] }, { "id": "https://docs.retool.com/changelog/cockroachdb-integration", "content_html": "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.
\nTo enable the CockroachDB integration in Retool, navigate to Beta > Settings and turn on CockroachDB connector.
Retool now supports Google Vertex AI as a new native integration that can be used in AI resource queries.
\nThis change is available to cloud instances that use the updated AI resource management.
App builders can now defer the initialization of modules until they're viewable to improve the initial loading time of larger apps.
\nTo enable this public beta, navigate to Beta > Settings and enable [Perf] Module deferred evaluation.
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.
\nModules 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.
", "url": "https://docs.retool.com/changelog/defer-module-evaluation", "title": "Defer module evaluation", "summary": "Choose to defer module evaluation until the module is viewable.", "date_modified": "2026-03-31T12:00:00.000Z", "tags": [ "Apps", "Performance" ] }, { "id": "https://docs.retool.com/changelog/assist-march-2026", "content_html": "Retool made significant updates that improve Assist's app generation capabilities:
\nThis change is currently rolling out to cloud instances and will be available to self-hosted instances in an upcoming edge release.
| ServiceNow Integration Availability | ||
|---|---|---|
| Cloud | Generally Available | |
| Self-hosted Edge 3.357 or later | Generally Available | |
| Self-hosted Stable Expected in an upcoming release. |
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.
", "url": "https://docs.retool.com/changelog/servicenow-integration", "title": "ServiceNow resource integration now available", "summary": "Retool now offers a built-in ServiceNow integration for managing incidents, change requests, and other ServiceNow tables.", "date_modified": "2026-03-17T09:00:00.000Z", "tags": [ "New", "Integrations" ] }, { "id": "https://docs.retool.com/changelog/gpt-5.4", "content_html": "GPT-5.4 is now available in Retool through OpenAI. It can currently be used with AI actions.
", "url": "https://docs.retool.com/changelog/gpt-5.4", "title": "GPT-5.4 available in Retool", "summary": "Retool now supports GPT-5.4.", "date_modified": "2026-03-11T12:00:00.000Z", "tags": [ "AI" ], "_self_hosted": "3.355.0" }, { "id": "https://docs.retool.com/changelog/app-readme-source-control", "content_html": "READMEs can now be protected for apps that use Source Control. For existing apps that have a README, Retool will add a README.md file to your repository with your next commit. If you are protecting an app for the first time, Retool will include the README.md file automatically.
This feature is currently rolling out to cloud instances and will be available to self-hosted instances on an upcoming edge release.
As a form of feedback, you can now submit prompts from the help button. Find the help button at the bottom right of pages like the apps or resources landing page. Each prompt triggers an internal prototype generated with AI, which Retool can use to improve the product. If Retool implements the feature, you can choose to be credited with your name in the changelog.
\n\n\nRetool would like to thank the Conductor team, who inspired this change with their recent update.
Retool has two new improvements to the API:
\n{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.Retool now supports hardened images, which are now available on the self-hosted stable release channel. These images are designed to improve supply-chain security, reduce the attack surface, and support modern infrastructure while remaining functionally compatible with existing deployments. Learn more about hardened images in the conceptual guide.
\nAt this time, hardened images are supported for the tryretool/backend Docker image only. Retool plans to expand support for hardened images to tryretool/code-executor-service in the future.
Use the following high-level steps to evaluate and roll out hardened images.
\nRetool strongly recommends testing hardened images on non-production instances first, for example:
\nWhen testing:
\n*-stable-hardened tags.When you're ready to use hardened images in production:
\nIf you encounter regressions, you can temporarily roll back to classic images by reverting your image tags while you work to diagnose and resolve issues.
\nOver time, hardened images will become the recommended default for production deployments, and classic images will eventually be phased out.
\nTo stay current on timelines and support windows, monitor the Stable releases and Self-hosted requirements documentation.
", "url": "https://docs.retool.com/changelog/hardened-images-stable", "title": "Hardened images available in stable channel", "summary": "Optionally use security-hardened images for stable releases.", "date_modified": "2026-03-03T12:00:00.000Z", "tags": [ "Self-hosted" ] }, { "id": "https://docs.retool.com/changelog/self-hosted-retool-3334-stable", "content_html": "Self-hosted Retool 3.334.0 is now available on the Stable release channel.
\n\nRetool releases a version on the Stable channel every 13 weeks (quarterly). A Stable release is generally four versions behind the cloud-hosted version at the time.
\nPreparation and testing of a Stable version occurs approximately four weeks prior to its release. Stable releases are rigorously tested before they are published. As the release cycle is less frequent, administrators can more easily maintain and upgrade deployments.
\nRetool supports each Stable release for six months. During this time, Retool will release patch updates that contain bug fixes or security updates. Patch updates do not contain functionality changes and can be applied more quickly than performing a full version upgrade.
\nRetool provides versioned product documentation for supported Stable releases. When browsing Retool Docs, use the version dropdown menu in the navbar to switch to a relevant version.
After six months, a Stable release is considered deprecated. You can continue using a deprecated release but it will no longer receive updates. At this time, you should upgrade to the latest Stable release.
\nLearn about the latest features, changes, and improvements in self-hosted Retool on the Stable channel. You can also compare release versions to get a complete list of all changes. A text-only version of all stable release notes is also available.
", "url": "https://docs.retool.com/changelog/self-hosted-retool-3334-stable", "title": "Self-hosted Retool 3.334 Stable", "date_modified": "2026-03-03T09:00:00.000Z", "tags": [ "Self-hosted" ] }, { "id": "https://docs.retool.com/changelog/workflows-landing-page-update", "content_html": "Retool made significant design updates to the workflows landing page to improve user experience and align more closely with the agents landing page.
\nThe workflows landing page was updated for cloud instances. It will be available in an upcoming edge release, and is expected in the Q2 stable release for self-hosted instances. To revert to the previous landing page experience, toggle off the Reskin workflow index page to render agents home page UI feature flag in Settings > Beta.
The landing page displays all workflows, and folders containing workflows, for your Retool organization. You can perform the following actions from the landing page:
\nClaude Sonnet 4.6 and Opus 4.6 are now available in Retool through Anthropic and Amazon Bedrock. Sonnet 4.6 and Opus 4.6 can both be used with AI resource queries.
", "url": "https://docs.retool.com/changelog/claude-sonnet-opus-4.6", "title": "Claude Sonnet 4.6 and Opus 4.6 available in Retool", "summary": "Retool now supports Claude Sonnet 4.6 and Opus 4.6.", "date_modified": "2026-02-19T12:00:00.000Z", "tags": [ "AI" ], "_self_hosted": "3.344.0" }, { "id": "https://docs.retool.com/changelog/rest-api-specifications", "content_html": "When creating a new REST API resource, you can now connect an OpenAPI or Swagger specification. Connecting an API specification enables:
\nWhen working with resources, users can also manually create endpoints or parameters that aren't included in the specification.
\nThis feature is currently rolling out to cloud instances, and it will be available in an upcoming edge release.
Source Control configuration now supports embedded expressions in sensitive credential fields, including access tokens, passwords, private keys, and SSH keys. This enables secure credential management using configuration variables and secrets.
\nToggle the Template variables in Source Control config feature flag in Settings > Beta to enable this feature.
\n{{ environment.variables.MY_KEY_OR_TOKEN }}
{{ secrets.MY_SECRET.KEY }}
Embedded expression support is available for all Source Control git providers: GitHub, GitLab, Bitbucket, Azure Repos, and AWS CodeCommit. The UI includes field captions, autocomplete, and validation to help you use embedded expressions correctly.
\nNon-sensitive fields like repository names, branch names, and usernames do not yet support embedded expressions.
", "url": "https://docs.retool.com/changelog/source-control-embedded-expressions", "title": "Source control credentials allow embedded expressions", "summary": "Source Control configuration now supports embedded expressions in sensitive credential fields, including access tokens, passwords, private keys, and SSH keys. This enables secure credential management using configuration variables and secrets.", "date_modified": "2026-02-11T16:00:00.000Z", "tags": [ "Source Control", "Beta", "Enterprise" ] }, { "id": "https://docs.retool.com/changelog/app-width", "content_html": "Newly created apps now have their Max width value set to 1200 px by default. This change improves usability and responsiveness.
\nExisting apps are unchanged. If you want to adjust the maximum width of your app, navigate to the Inspector and adjust the Max width setting in the Spacing section.
", "url": "https://docs.retool.com/changelog/app-width", "title": "Updated default max width for apps", "summary": "New apps will default to a max width of 1200 px.", "date_modified": "2026-02-11T12:00:00.000Z", "tags": [ "Apps" ] }, { "id": "https://docs.retool.com/changelog/ai-resource-integrations", "content_html": "Starting February 23rd, Retool will roll out provider-specific AI resource integrations (e.g., OpenAI, Anthropic, and Bedrock) in place of the singular Retool AI resource. This change is part of a broader effort to make AI integrations behave more like other resources in Retool: more flexible, more governable, and easier to scale as usage grows.
\nThese changes will first roll out to cloud instances. Self-hosted instances can expect to receive the changes in a future release. There are no pricing or packaging changes associated with this update.
\nNo action is required to facilitate this change. All existing apps, queries, workflows, and agents will continue to work based on existing configurations.
\nInstead of a single Retool AI resource, AI providers will function like any other resource at Retool. This allows for more flexibility when using AI, such as:
\nThe dedicated AI Action query is also being deprecated as its functionality will be available in AI resource queries.
", "url": "https://docs.retool.com/changelog/ai-resource-integrations", "title": "Improved AI resource management", "summary": "Provider-specific AI resources will replace the Retool AI resource.", "date_modified": "2026-02-10T12:00:00.000Z", "tags": [ "AI", "Resources" ] }, { "id": "https://docs.retool.com/changelog/assist-theming", "content_html": "Retool now supports controls for configuring your app theme while prompting Assist.
\nRetool released a Version 3.0 of the Microsoft SQL Server integration that includes various fixes and improvements. New Microsoft SQL resources will use this version by default. Existing resources can be updated using the Connector version setting.
\nBeginning in the 2026 Q3 stable release, Version 1.0 and Version 2.0 of the integration will be deprecated. Retool strongly recommends that you update your resource configuration before Q3 in order to prevent any interruptions and to resolve any unforeseen issues. If necessary, Retool may automatically migrate resources to Version 3.0 in order to ensure any issues are identified and resolved prior to the removal of the old versions.
\nThere is a known breaking change introduced in Version 2.0 that will also apply when upgrading from Version 1.0 to Version 3.0:
\nBeginning in Version 2.0, array inputs must be passed as a string when used in string_split in order to pass the Microsoft SQL SDK validation. For example, select * from string_split({{[1,2,3]}}, ','); must change to select * from string_split({{[1,2,3].join(',')}}, ',');.
No breaking changes are expected between Version 2.0 and Version 3.0.
", "url": "https://docs.retool.com/changelog/microsoft-sql", "title": "New version of Microsoft SQL Server integration, planned deprecation of Version 1 and Version 2", "summary": "A new version of the Microsoft SQL Server integration is available. Version 1 and Version 2 will be deprecated in the 2026 Q3 stable release.", "date_modified": "2026-02-03T12:00:00.000Z", "tags": [ "Resources" ], "_self_hosted": "3.334.0" }, { "id": "https://docs.retool.com/changelog/assist-rbac", "content_html": "For Enterprise and Business plans, Retool now allows admins to control access to Assist and its Ask and Build modes. Organization admins can use roles and permissions to create roles and edit roles with one of the following permissions:
\nBy default, all users have access to Assist and both Ask and Build mode through a preconfigured role. This role is called Assist Role or Editor, based on when your organization was created. Organization admins can edit these roles, or they can create new roles with more restrictive permissions.
This change is valuable for organizations that need to limit or prevent Assist usage to specific populations of users. For example, admins might wish to restrict Assist usage to user groups who do not have access to sensitive data or PII. Alternatively, admins could restrict access to all user groups except for a pilot group testing AI tools.
", "url": "https://docs.retool.com/changelog/assist-rbac", "title": "Role-based access controls for Assist", "summary": "Assist now supports role-based access controls.", "date_modified": "2026-02-03T11:00:00.000Z", "tags": [ "Apps", "Assist", "AI", "Enterprise", "Business" ], "_self_hosted": "3.334.0" }, { "id": "https://docs.retool.com/changelog/multi-instance-releases-ga", "content_html": "Multi-instance releases are now generally available to cloud instances and self-hosted instances on version 3.330 or later, with support for both apps and workflows.
\nOrganizations using Source Control can manage releases of protected apps and workflows across multiple deployment instances. This feature enables you to publish different release versions across instances, making it easy to test newer versions on staging or development instances before promoting to production.
", "url": "https://docs.retool.com/changelog/multi-instance-releases-ga", "title": "Multi-instance releases for Source Control", "summary": "Multi-instance releases are now generally available to cloud instances and self-hosted instances on version 3.330 or later, with support for both apps and workflows.", "date_modified": "2026-01-29T16:00:00.000Z", "tags": [ "Source Control", "Enterprise" ] }, { "id": "https://docs.retool.com/changelog/multiplayer-license_key", "content_html": "Beginning in the Q3 2026 stable release, self-hosted instances using the multiplayer feature must set the LICENSE_KEY environment variable on the multiplayer service container. While this environment variable is not yet required, Retool recommends setting it now to avoid any service interruptions.
You can now unpublish workflow releases from the Releases tab.
\nThis feature is also available for workflows protected with Source Control. When unpublishing a release on a protected workflow, the latest saved version on the main branch will be live to users.
\n\n", "url": "https://docs.retool.com/changelog/workflows-unpublish-ga", "title": "Unpublish a workflow release", "summary": "Unpublish a release on protected and unprotected workflows.", "date_modified": "2026-01-29T12:00:00.000Z", "tags": [ "Workflows", "Cloud", "Source Control", "Self-hosted" ] }, { "id": "https://docs.retool.com/changelog/assist-multipage", "content_html": "Assist now supports the ability to create and edit multipage apps. Previously, Assist could only work with one page at a time.
\nAssist can now:
\nWhile Assist is generating, navigating between pages is disabled to prevent errors.
\nThis change is currently rolling out to cloud instances and will be available in an upcoming edge release.
A number of security vulnerabilities in the React framework and related frameworks, like next.js, were recently disclosed. These vulnerabilities did not impact Retool.
\n\nThese vulnerabilities were related to React's server-side rendering systems which are not used by Retool. As such, there is no action for cloud- or self-hosted customers to take.
\nRetool's website was also not impacted. We confirmed with our vendor that these vulnerabilities were already mitigated before being publicly disclosed. After the patches were released they applied the patches the same day.
", "url": "https://docs.retool.com/changelog/disclosures/react-vulnerabilities-no-impact", "title": "Retool not impacted by recently disclosed React vulnerabilities", "summary": "Retool was not affected by CVE-2025-55184, CVE-2025-55183, or CVE-2025-55182.", "date_modified": "2025-12-23T17:12:40.000Z", "tags": [ "Disclosures" ] }, { "id": "https://docs.retool.com/changelog/assist-modes", "content_html": "Retool now supports two modes for prompting with Assist: Ask and Build. Use Ask as a safe, read-only way to understand and debug your app without adding or changing components or logic, and Build when you’re ready for Assist to make edits.
\nBoth modes use the same understanding of your app, your data, Retool features, and documentation.
\nToggle between Ask and Build mode.
Assist defaults to using Build mode. You can switch between modes at any time.
", "url": "https://docs.retool.com/changelog/assist-modes", "title": "Ask and Build mode with Assist", "summary": "Users can toggle between exploration and building modes in Assist.", "date_modified": "2025-12-18T12:00:00.000Z", "tags": [ "Apps", "Assist", "AI" ], "_self_hosted": "3.317" }, { "id": "https://docs.retool.com/changelog/deepseek-models", "content_html": "Retool added support for DeepSeek-V3.2 in Baseten. DeepSeek-R1 is no longer supported, and DeepSeek-V3.2 will be used instead.
", "url": "https://docs.retool.com/changelog/deepseek-models", "title": "Baseten models updated", "summary": "Retool updated the supported AI models for Baseten.", "date_modified": "2025-12-15T12:00:00.000Z", "tags": [ "AI" ] }, { "id": "https://docs.retool.com/changelog/gpt-5.2", "content_html": "OpenAI's model GPT-5.2 is now available in Retool. It can be used with AI actions and with Retool Agents.
", "url": "https://docs.retool.com/changelog/gpt-5.2", "title": "OpenAI GPT-5.2 available in Retool", "summary": "Retool now supports GPT-5.2.", "date_modified": "2025-12-15T12:00:00.000Z", "tags": [ "AI" ] }, { "id": "https://docs.retool.com/changelog/assist-thread-summarization", "content_html": "Assist can now automatically summarize long threads. The amount of information sent to the AI provider (the context window) increases as you build. Instead of sending your full message history to the AI provider with every request, Retool now regularly compacts the thread and sends the conversation summary along with any following messages. This improvement keeps the context window within the required limits, reducing the likelihood of errors and preventing interruptions when prompting with Assist.
\nThread summarization can occur either during or after app generation.
\n![](\"https://docs.retool.com/assets/images/summary-9ff5c761709d930f6fc2b3ba5505e866.png\")
Assist summarizes long threads.
The Agent-to-agent (A2A) protocol provides standardized and secure communication between external agents and agents built with Retool, so you can trigger your agent from an external agent, or embed agents in your own systems.
\nCurrently, Retool supports ingress into Retool agents from an external agent.
Retool has implemented the core set of A2A functionality, so you can:
\nTo allow external agents to communicate with Retool agents, you can enable the A2A trigger on your agent's configuration page, and copy the endpoint and API key into your A2A client. The A2A client then sends messages via common messaging formats like the HTTP+REST and JSON-RPC APIs, and Server-Sent Events (SSE) for long-running streaming updates.
\n\n\nExplore the following pages for more information:
\nAssist can now more reliably explore large or under-documented SQL database schemas without exceeding LLM context windows. These changes enable Assist to generate higher quality SQL queries for your apps and reduce the likelihood of SQL-related errors.
\nCustomers with simple schemas now benefit from richer context retrieved through exploratory queries, while large enterprises can rely on Assist to navigate massive data lakes.
", "url": "https://docs.retool.com/changelog/assist-sql", "title": "Improvements to writing SQL with Assist", "summary": "Retool made improvements to the quality of SQL queries written with Assist.", "date_modified": "2025-12-05T12:00:00.000Z", "tags": [ "Apps", "Assist", "AI" ], "_self_hosted": "3.317" }, { "id": "https://docs.retool.com/changelog/resource-type-restrictions", "content_html": "Self-hosted organizations can now restrict the creation or usage of specific resource types using either the RESOURCE_TYPES_CREATION_DENY_LIST or RESOURCE_TYPES_DENY_LIST environment variables.
\nRESOURCE_TYPES_CREATION_DENY_LIST prevents users from creating any resources of the specified types. Any existing resources continue to function.RESOURCE_TYPES_DENY_LIST prevents users from both creating and using any resources of the specified types. Any related resource queries will then fail.Any restrictions you set can be reverted at any time.
", "url": "https://docs.retool.com/changelog/resource-type-restrictions", "title": "Resource type restrictions for self-hosted Retool", "summary": "Self-hosted organizations can prevent users from creating or using certain types of resources.", "date_modified": "2025-12-02T09:00:00.000Z", "tags": [ "Self-hosted", "Resources" ] }, { "id": "https://docs.retool.com/changelog/roles-permissions-ga", "content_html": "| Admin granularity Availability | ||
|---|---|---|
| Cloud | Generally Available | |
| Self-hosted Edge 3.300 or later | Generally Available | |
| Self-hosted Stable 3.300 or later | Generally Available |
Role-based permissions is now generally available for organizations to configure granular admin controls. Organizations can now configure granular admin permissions. You can create roles with granular permissions so groups can manage certain organization settings without full administrator access.
\nOnce you configure the necessary roles to control access, you can apply them to any number of groups. Retool will eventually transition away from using per-group permissions to role-based access controls for permissions management.
", "url": "https://docs.retool.com/changelog/roles-permissions-ga", "title": "Granular admin permissions now available", "summary": "Role-based permissions is now generally available for organizations to configure granular admin controls. Organizations can now configure granular admin permissions. You can create roles with granular permissions so groups can manage certain organization settings without full administrator access.", "date_modified": "2025-12-02T09:00:00.000Z", "tags": [ "Users and Permissions" ] }, { "id": "https://docs.retool.com/changelog/secrets-manager-multiple-configurations", "content_html": "Support for multiple Secrets Manager configurations is now available in public beta. Once enabled, self-hosted organizations can create additional configurations and retrieve secrets data from multiple locations.
\nThe multiple configurations beta is available in self-hosted Retool 3.300 and later.
", "url": "https://docs.retool.com/changelog/secrets-manager-multiple-configurations", "title": "Multiple Secrets Manager configurations beta", "summary": "Self-hosted organizations can now create multiple Secrets Manger configurations and retrieve secrets from different locations.", "date_modified": "2025-12-02T09:00:00.000Z", "tags": [ "Beta" ] }, { "id": "https://docs.retool.com/changelog/self-hosted-retool-3300-stable", "content_html": "Self-hosted Retool 3.300.0 is now available on the Stable release channel.
\n\nRetool releases a version on the Stable channel every 13 weeks (quarterly). A Stable release is generally four versions behind the cloud-hosted version at the time.
\nPreparation and testing of a Stable version occurs approximately four weeks prior to its release. Stable releases are rigorously tested before they are published. As the release cycle is less frequent, administrators can more easily maintain and upgrade deployments.
\nRetool supports each Stable release for six months. During this time, Retool will release patch updates that contain bug fixes or security updates. Patch updates do not contain functionality changes and can be applied more quickly than performing a full version upgrade.
\nRetool provides versioned product documentation for supported Stable releases. When browsing Retool Docs, use the version dropdown menu in the navbar to switch to a relevant version.
After six months, a Stable release is considered deprecated. You can continue using a deprecated release but it will no longer receive updates. At this time, you should upgrade to the latest Stable release.
\nLearn about the latest features, changes, and improvements in self-hosted Retool on the Stable channel. You can also compare release versions to get a complete list of all changes. A text-only version of all stable release notes is also available.
", "url": "https://docs.retool.com/changelog/self-hosted-retool-3300-stable", "title": "Self-hosted Retool 3.300 Stable", "date_modified": "2025-12-02T09:00:00.000Z", "tags": [ "Self-hosted" ] }, { "id": "https://docs.retool.com/changelog/workflows-unpublish", "content_html": "You can now unpublish workflow releases from the Releases tab.
\nReach out to your account manager to enable unpublish for workflows.
This feature is also available for workflows protected with Source Control. When unpublishing a release on a protected workflow, the latest saved version on the main branch will be live to users.
\n\n", "url": "https://docs.retool.com/changelog/workflows-unpublish", "title": "Unpublish a workflow release", "summary": "Unpublish a release on protected and unprotected workflows.", "date_modified": "2025-11-24T12:00:00.000Z", "tags": [ "Workflows", "Cloud", "Source Control", "Beta" ] }, { "id": "https://docs.retool.com/changelog/assist-layout-editing", "content_html": "Retool improved Assist's ability to reason about and plan layout changes for large and complex apps. This change has the following impacts:
\nRetool now supports hardened images, which are available on the self-hosted edge release channel. These images are designed to improve supply-chain security, reduce the attack surface, and support modern infrastructure while remaining functionally compatible with existing deployments. Learn more about hardened images in the conceptual guide.
\nAt this time, hardened images are supported for the tryretool/backend Docker image only. Retool plans to expand support for hardened images to tryretool/code-executor-service in the future.
Use the following high-level steps to evaluate and roll out hardened images.
\nRetool strongly recommends testing hardened images on non-production instances first, for example:
\nWhen testing:
\n*-edge-hardened-beta tags.When you're ready to use hardened images in production:
\nIf you encounter regressions, you can temporarily roll back to classic images by reverting your image tags while you work to diagnose and resolve issues.
\nAfter sufficient testing and feedback on edge, Retool plans to transition hardened images to the stable channel. When that happens:
\nTo stay current on timelines and support windows, monitor the Stable releases and Self-hosted requirements documentation.
", "url": "https://docs.retool.com/changelog/hardened-images", "title": "Hardened images available in edge channel", "summary": "Optionally use security-hardened images.", "date_modified": "2025-11-20T12:00:00.000Z", "tags": [ "Beta", "Self-hosted" ] }, { "id": "https://docs.retool.com/changelog/workflows-readme", "content_html": "You can now create a README from the workflow IDE to help clarify important information about your workflow for collaborators. For example, if a workflow requires certain permissions on a resource, or if it's only scheduled to run once a week.
\nThis feature is also available for workflows protected with Source Control. To create a README, click the title of the workflow and add content to the Editor README field. READMEs are visible from the Edit workflow details dialog box, in workflows JSON exports, and in a markdown file from source control.
\n\n", "url": "https://docs.retool.com/changelog/workflows-readme", "title": "Create README files for workflows", "summary": "Create a README file in a workflow", "date_modified": "2025-11-18T12:00:00.000Z", "tags": [ "Workflows", "Cloud", "Self-hosted" ] }, { "id": "https://docs.retool.com/changelog/gemini-3-pro-preview", "content_html": "Google Gemini's model Gemini 3 Pro Preview is now available in Retool. It can be used with AI actions and with Retool Agents.
", "url": "https://docs.retool.com/changelog/gemini-3-pro-preview", "title": "Google Gemini 3 Pro Preview available in Retool", "summary": "Google Gemini's model Gemini 3 Pro Preview is now available in Retool. It can be used with AI actions and with Retool Agents.", "date_modified": "2025-11-17T12:00:00.000Z", "tags": [ "AI" ] }, { "id": "https://docs.retool.com/changelog/gpt-5.1", "content_html": "OpenAI's model GPT-5.1 is now available in Retool. It can be used with AI actions and with Retool Agents.
", "url": "https://docs.retool.com/changelog/gpt-5.1", "title": "OpenAI GPT-5.1 available in Retool", "summary": "OpenAI's model GPT-5.1 is now available in Retool. It can be used with AI actions and with Retool Agents.", "date_modified": "2025-11-17T12:00:00.000Z", "tags": [ "AI" ] }, { "id": "https://docs.retool.com/changelog/google-slides", "content_html": "If you self-host Retool and are using a stable release, reach out to your account manager to enable Google Slides.
Retool now supports an integration to Google Slides, which utilizes the Google Slides API and the Google Drive API. Use this integration to retrieve, create, and update documents for apps, workflows, and agents.
\nThis integration can also indirectly interact with the Google Sheets API. Charts from Google Sheets can be embedded into Google Slides.
Retool now supports Azure OpenAI for use with Assist. Admins on the Enterprise plan can configure Assist to use Azure OpenAI as the single model provider for Assist-powered interactions.
\nTo enable the use of Azure OpenAI as a single model provider, reach out to your account manager.
Retool designed Assist to use two AI providers by default: OpenAI and Anthropic. Using both providers enables Assist to optimize for speed and quality. However, some customers may need to consolidate AI services with a single provider. To accommodate these customers, Enterprise organizations can configure Assist to work with a single provider.
", "url": "https://docs.retool.com/changelog/assist-azure", "title": "Assist supports Azure OpenAI", "summary": "Assist supports Azure OpenAI as a single model provider.", "date_modified": "2025-11-06T14:00:00.000Z", "tags": [ "Apps", "Assist", "AI", "Enterprise" ], "_self_hosted": "3.303" }, { "id": "https://docs.retool.com/changelog/claude-sonnet-3.5-deprecated", "content_html": "Retool no longer supports Claude Sonnet 3.5. Claude Sonnet 4.5 will be used instead.
", "url": "https://docs.retool.com/changelog/claude-sonnet-3.5-deprecated", "title": "Deprecated: Claude Sonnet 3.5", "summary": "Retool no longer supports Claude Sonnet 3.5.", "date_modified": "2025-11-03T12:00:00.000Z", "tags": [ "AI" ], "_self_hosted": "3.300.0" }, { "id": "https://docs.retool.com/changelog/integrations-ga", "content_html": "The following integrations were previously in public beta and are now generally available:
\n", "url": "https://docs.retool.com/changelog/integrations-ga", "title": "General availability of Kafka, SQS, SNS, Tavily", "summary": "Tavily Web Search and all streaming integrations are now generally available.", "date_modified": "2025-11-03T12:00:00.000Z", "tags": [], "_self_hosted": "3.300.0" }, { "id": "https://docs.retool.com/changelog/gpt-3.5-turbo-instruct-deprecated", "content_html": "Retool no longer supports GPT 3.5 Turbo. GPT-4o-mini will be used instead.
", "url": "https://docs.retool.com/changelog/gpt-3.5-turbo-instruct-deprecated", "title": "Deprecated: GPT 3.5 Turbo", "summary": "Retool no longer supports GPT 3.5 Turbo.", "date_modified": "2025-10-30T12:00:00.000Z", "tags": [ "AI" ], "_self_hosted": "3.300.0" }, { "id": "https://docs.retool.com/changelog/assist-bedrock", "content_html": "Retool now supports Amazon Bedrock for use with Assist. Admins on the Enterprise plan can configure Assist to use Amazon Bedrock as the single model provider for Assist-powered interactions.
\nTo enable the use of Amazon Bedrock as a single model provider, reach out to your account manager.
Retool designed Assist to use two AI providers by default: OpenAI and Anthropic. Using both providers enables Assist to optimize for speed and quality. However, some customers may need to consolidate AI services with a single provider. To accommodate these customers, Enterprise organizations can configure Assist to work with a single provider.
", "url": "https://docs.retool.com/changelog/assist-bedrock", "title": "Assist supports Amazon Bedrock", "summary": "Assist supports Amazon Bedrock as a single model provider.", "date_modified": "2025-10-24T14:00:00.000Z", "tags": [ "Apps", "Assist", "AI", "Enterprise" ], "_self_hosted": "3.295" }, { "id": "https://docs.retool.com/changelog/assist-oct-24", "content_html": "Retool released some updates and improvements to the Assist experience:
\nThis change is available on cloud instances and self-hosted instances on version 3.284.0 and later.
To enable Source Control for Agents in version 3.284.0 or 3.284.1, reach out to your account manager.
In version 3.284.2, Source Control for Agents is available by default, and admins can disable it in Settings > Beta by toggling the AI Agents Source Control feature flag.
You can protect an agent with Source Control from the dropdown next to the agent name, or from the dropdown on the All agents page.
\n\n\nSource Control for agents operates similarly to how it does for apps, but with some key differences.
\nSelf-hosted Retool 3.284 is now available on the Stable release channel. Retool encourages prompt upgrades to each Stable version once it is released to ensure that your deployment stays secure and up-to-date.
\nThis release is off-cycle, and it is intended to bring Assist to self-hosted organizations that prefer to use the Stable channel. The next Stable release will occur at the end of Q4 2025, and Stable releases will continue quarterly thereafter.
Retool supports each Stable release for six months. During this time, Retool will release patch updates that contain bug fixes or security updates. Patch updates do not contain functionality changes and can be applied more quickly than performing a full version upgrade.
\nAfter six months, a Stable release is considered deprecated. You can continue using a deprecated release but it will no longer receive updates. At this time, you should upgrade to the latest Stable release.
\nRetool provides versioned product documentation for supported Stable releases. When browsing Retool Docs, use the version dropdown menu in the navbar to switch to a relevant version.
Learn about the latest features, changes, and improvements in self-hosted Retool on the Stable channel. You can also compare release versions to get a complete list of all changes. A text-only version of all stable release notes is also available.
", "url": "https://docs.retool.com/changelog/self-hosted-retool-3284-stable", "title": "Self-hosted Retool 3.284 Stable", "summary": "Self-hosted Retool 3.284 is now available on the Stable release channel. Retool encourages prompt upgrades to each Stable version once it is released to ensure that your deployment stays secure and up-to-date.", "date_modified": "2025-10-21T10:00:00.000Z", "tags": [ "Self-hosted" ] }, { "id": "https://docs.retool.com/changelog/claude-haiku-4.5", "content_html": "Claude Haiku 4.5 is now available in Retool. It can be used with AI actions and with Retool Agents.
", "url": "https://docs.retool.com/changelog/claude-haiku-4.5", "title": "Claude Haiku 4.5 available in Retool", "summary": "Retool now supports Claude Haiku 4.5.", "date_modified": "2025-10-20T12:00:00.000Z", "tags": [ "AI" ] }, { "id": "https://docs.retool.com/changelog/protect-workflow-triggers", "content_html": "Enterprise customers can now use Source Control to protect workflow triggers. This prevents changes to a workflow's triggers without review. When you protect a workflow for the first time, triggers are now automatically included.
\nTo enable protected workflow triggers for self-hosted Retool on the stable channel, reach out to your Account Manager to enable the Allow users to edit triggers on branches feature flag.
For workflows that are already protected, you now have the option to protect triggers using a new PR.
\n\n\nOnce protected, triggers are versioned and published alongside each release. Information about your triggers is stored in the startTrigger.yml file in your Source Control repository.
Users can now modify the order of pages in multipage apps. In the Pages tab in the left panel of the app IDE, users can sort pages relative to each other using drag-and-drop.
\nChanges to the page order are immediately reflected in the page menu (and in header and sidebar frames if present). The retoolContext.pages Javascript variable also provides the list of pages in order.
This change is currently live on cloud and will be available in an upcoming edge release.
Enterprise customers can now use the Get IP Allowlist by Region endpoint to programmatically retrieve Retool's IP addresses. If you make use of inbound firewall rules, include the following IP addresses in its allowlist so that Retool can access your resources.
", "url": "https://docs.retool.com/changelog/ip-endpoint", "title": "Retool API endpoint to retrieve IP address allowlist", "summary": "Use a Retool API endpoint to retrieve Retool's IP addresses.", "date_modified": "2025-10-09T12:00:00.000Z", "tags": [ "Enterprise" ] }, { "id": "https://docs.retool.com/changelog/kimi-k2-instruct", "content_html": "An open source AI model available through Baseten, Kimi K2 Instruct is now available in Retool. It can be used with AI actions and with Retool Agents.
", "url": "https://docs.retool.com/changelog/kimi-k2-instruct", "title": "Kimi K2 Instruct available in Retool", "summary": "Retool now supports Kimi K2 Instruct.", "date_modified": "2025-10-09T12:00:00.000Z", "tags": [ "AI" ], "_self_hosted": "3.286" }, { "id": "https://docs.retool.com/changelog/llama-4-deprecated", "content_html": "Retool no longer supports the Llama 4 Maverick or Llama 4 Scout AI models in Retool AI. The Kimi K2 Instruct model will be used instead.
", "url": "https://docs.retool.com/changelog/llama-4-deprecated", "title": "Deprecated: Llama 4 models", "summary": "Retool no longer supports Llama 4 Maverick.", "date_modified": "2025-10-09T12:00:00.000Z", "tags": [ "AI", "Deprecation" ], "_self_hosted": "3.286.0" }, { "id": "https://docs.retool.com/changelog/assist", "content_html": "Retool is excited to announce Assist, your AI-powered partner for app development. Prompt Assist with natural language directly from the app IDE to generate apps, make changes to existing apps, and ask questions about Retool.
\nAssist can:
\nRetool has released several improvements to the README experience for web apps:
\nPreviously, app READMEs were found by clicking the title of the app. If your app has an existing README, you can now find it in the Pages tab.
", "url": "https://docs.retool.com/changelog/readme", "title": "README improvements for apps", "summary": "The README is now included in the **Pages** list of the app IDE and can be generated automatically with AI.", "date_modified": "2025-10-07T08:30:00.000Z", "tags": [ "Apps", "AI" ] }, { "id": "https://docs.retool.com/changelog/invoke-agent-block", "content_html": "To enable Result (sync) for Agents in self-hosted Retool version 3.284.0 or 3.284.1, reach out to your account manager.
In version 3.284.2, Result (sync) for Agents is available by default, and admins can disable it in Settings > Beta by toggling the Agent blocks in workflows sync mode feature flag.
You can now see the output of an agent run with the Result (sync) return type when using the Invoke Agent block in workflows.
\nagentRunId, agentId, and status only. It does not include the output of the agent.Claude Sonnet 4.5 is now available in Retool. It can be used with AI actions and with Retool Agents.
", "url": "https://docs.retool.com/changelog/claude-sonnet-4.5", "title": "Claude Sonnet 4.5 available in Retool", "summary": "Retool now supports Claude Sonnet 4.5.", "date_modified": "2025-10-01T12:00:00.000Z", "tags": [ "AI" ], "_self_hosted": "3.282.0" }, { "id": "https://docs.retool.com/changelog/gemini-1.5-deprecated", "content_html": "Retool no longer supports Gemini 1.5 Pro. Gemini 2.0 Flash will be used instead.
", "url": "https://docs.retool.com/changelog/gemini-1.5-deprecated", "title": "Deprecated: Gemini 1.5 Pro", "summary": "Retool no longer supports Gemini 1.5 Pro.", "date_modified": "2025-10-01T12:00:00.000Z", "tags": [ "AI" ], "_self_hosted": "3.283.0" }, { "id": "https://docs.retool.com/changelog/cloud-breakage-form", "content_html": "Cloud customers on all plans can now submit breakage reports from inside the product to report regressions, breakages, and potential incidents on the Retool platform.
\n\n\nThe breakage form is available by clicking Report a breakage from the following locations:
\nAfter you submit a breakage report, you will receive a confirmation email with a ticket number.
", "url": "https://docs.retool.com/changelog/cloud-breakage-form", "title": "Send cloud breakage reports to Retool", "summary": "Cloud customers can now submit breakage reports to notify Retool about issues.", "date_modified": "2025-09-25T12:00:00.000Z", "tags": [ "New" ] }, { "id": "https://docs.retool.com/changelog/fullstory-ga", "content_html": "The Fullstory integration for session replay is now generally available.
\nWhen enabled, data about user interactions with apps are reported directly to Fullstory for you to review in detail. You can then analyze app analytics, evaluate impact, and review interactions with session replay. This integration is useful for monitoring user activity across different apps, and using advanced analytical tools like heatmaps and funnels to identify usage patterns, debug errors, and improve the overall user experience.
", "url": "https://docs.retool.com/changelog/fullstory-ga", "title": "General availability of Fullstory integration", "summary": "Capture user app behavior for use with Fullstory.", "date_modified": "2025-09-23T12:00:00.000Z", "tags": [ "Apps", "Observability", "Enterprise" ] }, { "id": "https://docs.retool.com/changelog/performance-monitoring", "content_html": "Enterprise customers can send page load and query traces to Datadog and Sentry using Retool's performance monitoring integration, now in public beta. Customers can respond proactively to regressions and troubleshoot more quickly by creating dashboards and alerts to monitor the performance of their apps and use the spans themselves to help pinpoint where to take action if their apps are degraded.
", "url": "https://docs.retool.com/changelog/performance-monitoring", "title": "Performance monitoring available in public beta", "summary": "Use Retool's performance monitoring integration to send page load and query traces to Datadog or Sentry.", "date_modified": "2025-09-23T12:00:00.000Z", "tags": [ "Apps", "Beta", "Enterprise" ] }, { "id": "https://docs.retool.com/changelog/i18n", "content_html": "Internationalization (i18n) is now generally available for organizations on the Enterprise plan. This allows you to localize Retool app content and data.
", "url": "https://docs.retool.com/changelog/i18n", "title": "General availability of internationalization", "summary": "Internationalization is now generally available", "date_modified": "2025-09-18T10:30:00.000Z", "tags": [ "Enterprise", "Apps", "Beta" ] }, { "id": "https://docs.retool.com/changelog/public-link-availability", "content_html": "Free and Team plan users can now create public links to share apps externally. Anyone with a public link can access the app, so this option should only be used for apps that don’t require authentication or contain sensitive data. Public links were previously limited to the Business and Enterprise plans.
\nIf your instance is self-hosted, reach out to your account manager or the support team and request access to public links.
You can now use the Copy as Markdown button on most pages of the Retool documentation to copy the contents of the page to your clipboard in Markdown format. This feature is intended to give you easy access to a version of the content that you can paste into an LLM for more accurate answers to questions about Retool.
", "url": "https://docs.retool.com/changelog/copy-as-markdown", "title": "Copy as markdown", "summary": "Easily copy pages as markdown.", "date_modified": "2025-09-16T12:00:00.000Z", "tags": [ "Docs" ] }, { "id": "https://docs.retool.com/changelog/roles-permissions", "content_html": "| Admin granularity Availability | ||
|---|---|---|
| Cloud | Generally Available | |
| Self-hosted Edge 3.300 or later | Generally Available | |
| Self-hosted Stable 3.300 or later | Generally Available |
Retool now supports managing permissions using role-based access control in public beta. You can create roles with granular permissions so groups can manage certain organization settings without full administrator access.
\nRole-based permissions offer much greater access control than Retool's existing group permissions functionality. For example, a Design team may need access to your organization's branding settings to ensure the Retool organization follows branding styles and guidelines. Rather than give the team members admin access, role-based permissions allow for granular control over what specific settings they can access.
\nOnce you configure the necessary roles to control access, you can apply them to any number of groups. Retool will eventually transition away from per-group permissions to role-based access controls as the method with which you manage permissions.
\nTo enable this feature, navigate to Settings > Beta and enable Permissions v2.
", "url": "https://docs.retool.com/changelog/roles-permissions", "title": "Role-based permissions", "summary": "Retool now supports managing permissions using role-based access control in public beta. You can create roles with granular permissions so groups can manage certain organization settings without full administrator access.", "date_modified": "2025-09-10T12:00:00.000Z", "tags": [ "Beta" ] }, { "id": "https://docs.retool.com/changelog/oauth-mcp-agents", "content_html": "OAuth 2.0 is now supported when adding an MCP server as a tool for an agent.
", "url": "https://docs.retool.com/changelog/oauth-mcp-agents", "title": "OAuth 2.0 available for MCP tools on Agents", "summary": "OAuth 2.0 is now supported when adding an MCP server as a tool for an agent.", "date_modified": "2025-09-09T16:00:00.000Z", "tags": [ "Beta", "Agents" ] }, { "id": "https://docs.retool.com/changelog/agents-stable-beta", "content_html": "Retool Agents is available on Retool's stable release 3.253.0.
\nTo enable Retool Agents in Self-hosted Retool 3.253.0 and later, toggle the AI Agents feature flag in Settings > Beta.
", "url": "https://docs.retool.com/changelog/agents-stable-beta", "title": "Retool Agents in stable channel for Self-hosted organizations", "summary": "Retool Agents is available on Retool's stable release 3.253.0.", "date_modified": "2025-09-09T12:00:00.000Z", "tags": [ "Beta", "Agents", "Self-hosted" ] }, { "id": "https://docs.retool.com/changelog/self-hosted-retool-3253-stable", "content_html": "Self-hosted Retool 3.253.0 is now available on the Stable release channel.
\n\nRetool releases a version on the Stable channel every 13 weeks (quarterly). A Stable release is generally four versions behind the cloud-hosted version at the time.
\nPreparation and testing of a Stable version occurs approximately four weeks prior to its release. Stable releases are rigorously tested before they are published. As the release cycle is less frequent, administrators can more easily maintain and upgrade deployments.
\nRetool supports each Stable release for six months. During this time, Retool will release patch updates that contain bug fixes or security updates. Patch updates do not contain functionality changes and can be applied more quickly than performing a full version upgrade.
\nRetool provides versioned product documentation for supported Stable releases. When browsing Retool Docs, use the version dropdown menu in the navbar to switch to a relevant version.
After six months, a Stable release is considered deprecated. You can continue using a deprecated release but it will no longer receive updates. At this time, you should upgrade to the latest Stable release.
\nLearn about the latest features, changes, and improvements in self-hosted Retool on the Stable channel. You can also compare release versions to get a complete list of all changes. A text-only version of all stable release notes is also available.
", "url": "https://docs.retool.com/changelog/self-hosted-retool-3253-stable", "title": "Self-hosted Retool 3.253 Stable", "date_modified": "2025-09-09T11:00:00.000Z", "tags": [ "Self-hosted" ] }, { "id": "https://docs.retool.com/changelog/jdbc-removal", "content_html": "Retool removed some JDBC connectors that were inadvertently included in certain self-hosted release versions. These include:
\nThese JDBC connectors are not supported by Retool for self-hosted deployments. If you have created a JDBC resource using these connectors, update its configuration as needed to make use of your own preferred JDBC drivers.
\nRetool has since released patch updates for affected releases that remove these connectors.
", "url": "https://docs.retool.com/changelog/jdbc-removal", "title": "Removal of unsupported JDBC connectors", "summary": "Retool removed some JDBC connectors that were inadvertently included in certain self-hosted release versions. These include:", "date_modified": "2025-09-09T09:00:00.000Z", "tags": [ "Self-hosted", "Integrations", "Resources" ] }, { "id": "https://docs.retool.com/changelog/custom-component-support-update", "content_html": "Retool updated the custom component support library to version 1.9.0, which adds a new verbose option with deploy and sync commands. When running into unknown failures, you can add the -v option to deploy and sync commands to print more detailed errors for help with debugging.
This library is automatically included as a dependency of the custom component collection template repository. Existing users can run npm update @tryretool/custom-component-support to get the latest version with these updates.
Customers with a 3.259.0-edge deployment should immediately update to 3.259.1-edge. This patch release addresses a security vulnerability that could expose environment variables during code-executor startup.
", "url": "https://docs.retool.com/changelog/vulnerability-patch-edge-3-259-1", "title": "Action Required: Update Self-hosted Retool 3.259.0-edge to 3.259.1-edge", "summary": "Customers with a 3.259.0-edge deployment should immediately update to 3.259.1-edge. This patch release addresses a security vulnerability that could expose environment variables during code-executor startup.", "date_modified": "2025-09-04T12:00:00.000Z", "tags": [ "Security", "Self-hosted" ] }, { "id": "https://docs.retool.com/changelog/databricks-lakebase-integration", "content_html": "| Databricks Lakebase Availability | ||
|---|---|---|
| Cloud | beta | |
| Self-hosted Edge 3.256 or later | beta | |
| Self-hosted Stable 3.253 or later | beta |
Retool now provides a built-in integration for Databricks Lakebase, a fully managed Databricks Postgres database built on lakehouse architecture.
", "url": "https://docs.retool.com/changelog/databricks-lakebase-integration", "title": "Databricks Lakebase integration", "summary": "Retool now provides a built-in integration for Databricks Lakebase, a fully managed Databricks Postgres database built on lakehouse architecture.", "date_modified": "2025-09-04T09:00:00.000Z", "tags": [ "Beta", "New", "Integrations" ] }, { "id": "https://docs.retool.com/changelog/draft-app-permissions", "content_html": "Organization admins can now control whether users can create draft apps on a per-group basis. If an admin disables the draft apps feature on a permission group, users within the group will not be able to create unpublished apps in their own drafts folder.
", "url": "https://docs.retool.com/changelog/draft-app-permissions", "title": "Restrict users from creating draft apps", "summary": "Organization admins can now control whether users can create draft apps on a per-group basis. If an admin disables the draft apps feature on a permission group, users within the group will not be able to create unpublished apps in their own drafts folder.", "date_modified": "2025-08-28T13:00:00.000Z", "tags": [ "Apps" ] }, { "id": "https://docs.retool.com/changelog/multi-instance-releases", "content_html": "Self-hosted organizations using Source Control to protect apps can opt into the public beta of multi-instance releases. This feature enables you to publish different release versions of apps across multiple deployment instances. This is particularly useful if you want to test a newer version of an app on a test instance first.
", "url": "https://docs.retool.com/changelog/multi-instance-releases", "title": "Multi-instance releases for Source Control", "summary": "Self-hosted organizations using Source Control to protect apps can opt into the public beta of multi-instance releases. This feature enables you to publish different release versions of apps across multiple deployment instances. This is particularly useful if you want to test a newer version of an app on a test instance first.", "date_modified": "2025-08-27T14:00:00.000Z", "tags": [ "Source Control", "Beta", "Enterprise" ] }, { "id": "https://docs.retool.com/changelog/updated-permissions-for-all-users", "content_html": "For new Business and Enterprise plan organizations, the All Users group does not have universal access permissions by default. Admin users can add permissions to the All Users group as needed.
\nThis change was made to simplify the process of creating custom groups, eliminating the need to remove permissions from the All Users group before creating more permissioned groups.
\nThis change does not impact existing organizations, or organizations upgrading from Free or Team plans.
", "url": "https://docs.retool.com/changelog/updated-permissions-for-all-users", "title": "Update to default user permissions on Business and Enterprise plans", "summary": "For new organizations, the **All Users** group has no permissions by default.", "date_modified": "2025-08-20T12:00:00.000Z", "tags": [ "Users and Permissions", "Business", "Enterprise" ], "_self_hosted": "3.259.0" }, { "id": "https://docs.retool.com/changelog/branch-merging", "content_html": "Retool added support within the IDE for merging changes from your default branch into your feature branch. This feature allows developers to keep their branches aligned with the default branch through guided, in-product flows, eliminating the need to switch to external tools like GitHub or GitLab.
\nWhen conflicts arise, Retool walks developers through a conflict resolution process entirely within the IDE, including validation checks to catch errors before completing the operation.
\nThis change also eliminates the need for catch-up commits.
\n\n", "url": "https://docs.retool.com/changelog/branch-merging", "title": "Support for branch merging with Source Control", "summary": "You can now integrate changes from your default branch from within the App IDE.", "date_modified": "2025-08-18T12:00:00.000Z", "tags": [ "Source Control", "Enterprise" ] }, { "id": "https://docs.retool.com/changelog/code-executor-required", "content_html": "Self-hosted Retool 3.251 and later contain two notable changes to the code-executor service:
\nRetool removed the preview release of Agents for self-hosted organizations since Agents is now in public beta with the 3.234.0 edge release and it will be available in 3.253 stable. This preview release was intended for deployment into a non-production environment, and was created as a mechanism to allow Self-hosted organizations the opportunity to create agents prior to their availability in an edge or stable release.
", "url": "https://docs.retool.com/changelog/self-hosted-agents", "title": "Removed Self-hosted preview of Retool Agents", "summary": "Retool removed the preview release of Agents for self-hosted organizations since Agents is now in public beta with the 3.234.0 edge release and it will be available in 3.253 stable. This preview release was intended for deployment into a non-production environment, and was created as a mechanism to allow Self-hosted organizations the opportunity to create agents prior to their availability in an edge or stable release.", "date_modified": "2025-08-06T12:00:00.000Z", "tags": [ "Beta", "Agents", "Self-hosted" ] }, { "id": "https://docs.retool.com/changelog/bitbucket-access-tokens", "content_html": "When setting up Source Control with Bitbucket, you can now use a Bitbucket access token instead of an app password. Access tokens provide a more secure authentication method than app passwords.
\nAuthentication using app passwords is still supported, but Retool recommends using access tokens instead.
", "url": "https://docs.retool.com/changelog/bitbucket-access-tokens", "title": "Support for Bitbucket access tokens", "summary": "Retool now supports Bitbucket access tokens.", "date_modified": "2025-08-06T10:00:00.000Z", "tags": [ "Source Control" ], "_self_hosted": "3.250.0" }, { "id": "https://docs.retool.com/changelog/protected-workflow-releases", "content_html": "If you use Source Control to protect a workflow, you can now create and publish releases for that workflow. This allows you to safely test and build changes without disruption. Previously, protected workflows were automatically versioned and published, and you could not publish a specific version.
\nWith this change, users must manually create a new release in order for their latest changes to be reflected in the live version of the workflow.
Once you merge a change into the main branch, navigate to the Releases tab in the left-hand menu. In this tab, you can create, manage, and publish versions of the workflow. Refer to Version and publish workflows for more information.
Retool made several UI changes to the workflow IDE and updated some terminology to improve clarity of workflow releases. Instead of deploying a workflow release, you now publish the release instead.
\nThe functionality remains the same and you continue to publish a workflow release for it to be live. This change was made to more closely align the app and workflow IDEs.
\nWhen you are ready to finalize your workflow changes, click Publish release in toolbar of the workflow IDE. This button was previously labeled Deploy.
\nCreate, publish, and revert releases from the Releases tab in the left panel. This tab was previously labeled Deploy History. You can also navigate to the Releases tab using the button in the status bar of the IDE, which also displays the currently published release version.
", "url": "https://docs.retool.com/changelog/workflow-release-language", "title": "Updates to workflow release language", "summary": "When your workflow is ready, you can publish a release.", "date_modified": "2025-07-24T12:00:00.000Z", "tags": [ "Workflows" ] }, { "id": "https://docs.retool.com/changelog/access-list", "content_html": "You can now view which users and permission groups have access to a workflow, resource, and agent. When on the listing page for one of these objects, click the ••• menu and select View access list. Use the tabs at the top of the list to show Users or Groups. The list shows the access level of each user or user group.
\n![](\"https://docs.retool.com/assets/images/access-list-5613054ee3b30ef9b495e8c712bf5066.png\")
The access list for a workflow.
Resources display permissions on a per-environment basis if they are configured.
\nAccess lists were already available for apps and app folders.
", "url": "https://docs.retool.com/changelog/access-list", "title": "Access lists for workflows, resources, and agents", "summary": "View access lists for workflows, resources, and agents.", "date_modified": "2025-07-10T12:00:00.000Z", "tags": [ "Users and Permissions" ], "_self_hosted": 3.236 }, { "id": "https://docs.retool.com/changelog/agents-edge-beta", "content_html": "Retool Agents is in public beta for cloud instances and self-hosted instances on version 3.234.0 and later.
Retool Agents is now in public beta on Self-hosted Retool 3.234.0.
\nTo enable Retool Agents in Self-hosted Retool 3.234.0 and later, the AGENTS_ENABLED environment variable must be set to true.
Modules now support typed data inputs. This change makes your modules more reliable by catching mismatched data types early.
\nPreviously, modules offered only a Data input for passing in property values. Now, you can choose from the following options when configuring a module input:
\nChoose from String, Number, Boolean, or Enum for type validation on your module input. Selecting a Type enforces stricter validation rules and displays a warning if the input type does not match what you selected. You can also define additional characteristics about the input, such as options for Enum, and default values for all types.
\nChanging the type of the module input does not alter the actual value passed into the module—invalid values are still passed through as-is. The validation only affects how the input fields behave and display warnings.
If you set the Type to Any, Retool performs no validation on the module input.
", "url": "https://docs.retool.com/changelog/module-input-types", "title": "Data input typing for modules", "summary": "New data type validation improves the inputs for modules.", "date_modified": "2025-07-03T12:00:00.000Z", "tags": [ "Apps" ], "_self_hosted": "3.240.0" }, { "id": "https://docs.retool.com/changelog/disclosures/cve-2025-49017", "content_html": "Certain versions of self-hosted deployments of Retool are vulnerable to cross-site request forgery (CSRF/XSRF) attacks via manipulated Retool Apps. HTML forms embedded in Retool Apps by properly permissioned users can, when interacted with by other users, be used to change that users' email address and take over their account.
\nThis issue has been fixed in the following Retool versions:
\nSee the complete list of affected and fixed versions below.
\nWe have no indications of this vulnerability being known publicly before this disclosure, nor any attacks or attempted attacks using the vulnerability. This vulnerability was reported to us privately first.
\nWe will communicate further updates here, should such become necessary.
\n| Disclosure | Details |
|---|---|
| Vulnerability Type | CWE-352: Cross-Site Request Forgery |
| Vendor of Product | Retool |
| Fixed Version | Edge: 3.212.0+; Stable: 3.148.14+, 3.196.4+ |
| Affected Product Code Base | Edge: 3.123.0 to 3.207.0; Stable: 3.148.0 to 3.148.13, 3.196.0 to 3.196.3-stable |
| Affected Component | Self-hosted Retool organizations |
| Attack Type | Remote |
| Impact | Escalation of Privileges |
| CVSS 3.x Base Score | 4.8 |
| CVSS 3.x Vector | CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:H/A:N/E:P/RL:O/RC:C |
| CVSS 4.x Base Score | 4.3 |
| CVSS 4.x Vector | CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:A/VC:L/VI:L/VA:N/SC:L/SI:H/SA:N |
| Reference | https://docs.retool.com/releases |
| Discoverer | Robinhood Red Team and Doyensec |
Customers who run self-hosted deployments of vulnerable Retool versions are affected.\nTo mount an attack using this vulnerability an attacker needs to have (a user account with) permission to create or edit a Retool App, embed a malicious HTML form, and get a victim user to interact with it.
\nWe have no indications of this vulnerability being known publicly before we fixed it, nor any attacks or attempted attacks using the vulnerability.
\nThe only available fix is to upgrade the Retool deployment to a fixed version. No other customer-controllable mitigations are available.
\nAuthenticated users under some circumstances (as described above) are able to take over other users' accounts if such users have interacted with a manipulated Retool App. Other account changing actions can be taken, but are generally less severe.
\nSuccessful attacks will result in the email address of taken over accounts to be changed. Besides confirming that no user account in a Retool deployment has an unexpected email address, customers can also check for
\nSelf-hosted Retool only.
\n| Release branch | Release versions |
|---|---|
| Edge | 3.123.0 to 3.207.0 |
| 3.196-stable | 3.196.0 to 3.196.3 |
| 3.148-stable | 3.148.0 to 3.148.13 |
Self-hosted Retool only.
\n| Branch | Versions |
|---|---|
| Edge | 3.212.0+ |
| 3.196-stable | 3.196.4+ |
| 3.148-stable | 3.148.14+ |
| Stable | >=3.227 |
Retool Cloud was vulnerable to an unauthenticated account takeover via the \"Passwordless Login\" feature. This could have been used to take over Retool user accounts in organizations using this feature. We successfully patched our cloud deployment for all customers on June 17th, 2025, at 2:26 PM PDT with no further action being required by customers. All potentially affected customers have been notified as of July 2nd, 2025.
\nThere are no indications of this vulnerability being publicly known nor any attempts to exploit it before being patched. Thanks to Rens van der Linden from QUAYOUNG for responsibly and privately disclosing the vulnerability to us.
\nWe will communicate further updates here, should such become necessary.
\nOrganizations with passwordless login enabled and MFA enforcement disabled, or with individual accounts that did not have MFA activated, were vulnerable. Enforcing MFA on the organization level prevented this vulnerability from being exploitable, as did enabling MFA for individual accounts.
\nWe were able to narrow down further which customers this was possible for and notified all customers that were potentially affected. Specifically, organizations with at least one user who successfully logged in using the passwordless login feature, and whose account at the time of such login did not have MFA enabled.
\nWe have no indications of this vulnerability being known publicly before we fixed it, nor any attacks or attempted attacks using the vulnerability.
\nA patch has already been deployed to Retool's Cloud environment. No action is required from you at this time, but we recommend enforcing MFA in your Retool organization for an extra layer of security.
\nPrior to our fix, this vulnerability enabled unauthenticated users to take over accounts in your organization through the passwordless login feature.
\nRetool audit logs will contain events for successful passwordless logins, which will always be emitted for any successful attack with this vulnerability. An unexpected successful passwordless login event after April 22, 2024 can indicate a compromise.
\nAdditionally, malicious logins may be identified by correlating email notifications for logins from new IP addresses. Attempted attacks would be indicated by unexpected passwordless login request emails from Retool. Matching the timing of the emails to login event timestamps in Retool Cloud and checking with your users who received the email can be used to determine if the login is unexpected. Utilizing your email provider's search or vault functionality to bulk search for these IOCs is advised.
", "url": "https://docs.retool.com/changelog/2025/07/02/disclosures/cloud-", "title": "July 2nd, 2025 Cloud vulnerability disclosure", "summary": "July 2nd, 2025 disclosure of a vulnerability in Retool Cloud.", "date_modified": "2025-07-02T00:00:00.000Z", "tags": [ "Disclosures" ] }, { "id": "https://docs.retool.com/changelog/per-page-permissions", "content_html": "Organizations on the Business or Enterprise plan can now restrict users from accessing specific app pages with per-page permissions. When configuring a permission group, you can now also specify permissions for each page.
\nPer-page permissions are generally available to cloud instances and in for self-hosted instances on version 3.219.0 and later.
Retool has rolled out unique identifiers (UUID) for app pages. If you use Source Control, Retool recommends that you create a new branch with no changes and push it to Source Control. If you use cloud or a self-hosted instance on version 3.191-edge or later, Retool automatically creates a migration commit to add UUIDs to each page. Once you merge this commit, you can successfully configure per-page permissions on your protected app.
\nIf you are working on more than one branch before the UUID addition in version 3.191-edge, Retool runs the migration on each of those branches, and the branches will end up with different UUIDs. Make sure add UUIDs only once, do not override the UUIDs on the main branch after adding them. Doing so results in the inability to set per-page permissions, because the IDs initially set on main are the ones that Retool will use.
Retool added two new configuration settings that enable you to customize the layout of modules:
\nWhen you configure these settings inside the module editor, the settings apply as the default values only to new module instances. Existing module instances are unchanged. You can also override these settings for a single module instance by changing them in the Inspector of the app that contains the module.
", "url": "https://docs.retool.com/changelog/module-layout", "title": "Module layout updates", "summary": "New configuration options improve the layout of modules.", "date_modified": "2025-06-16T12:00:00.000Z", "tags": [ "Apps" ] }, { "id": "https://docs.retool.com/changelog/self-hosted-agents-preview", "content_html": "A preview release of Retool Agents is currently available to self-hosted organizations for deployment into a non-production environment. This preview release is intended to allow customers to preview and create proof-of-concepts that show how agents may work in their environment.
\nAs Retool is continuously working to develop and improve Retool Agents to meet the high standards required for production environments, this preview release is not intended for production use and this build should not be deployed in an existing Retool installation or deployment. Retool recommends that self-hosted organizations create a new deployment in a private network alongside resources to which you intend to connect. Retool reserves the right to make changes to the agents preview without notification.
", "url": "https://docs.retool.com/changelog/self-hosted-agents-preview", "title": "Self-hosted preview of Retool Agents", "summary": "A preview release of Retool Agents is currently available to self-hosted organizations for deployment into a non-production environment. This preview release is intended to allow customers to preview and create proof-of-concepts that show how agents may work in their environment.", "date_modified": "2025-06-11T12:00:00.000Z", "tags": [ "Beta", "Agents", "Self-hosted" ] }, { "id": "https://docs.retool.com/changelog/agents", "content_html": "Retool Agents makes it simple for builders to automate work using large-language models (LLMs) by creating agents. Agents are systems that can complete or delegate tasks based on LLM reasoning.
\nAgents call tools—for example, workflows, functions, or other agents—to gather information and complete or delegate actions. When invoked, an agent:
\nYou can invoke an agent using any of the following trigger methods:
\nYou can then test, deploy, evaluate, and monitor your agent directly from Retool.
\nRetool Agents is not currently available to Self-hosted Retool organizations.
Retool recently discovered a bug in certain versions of self-hosted Retool that affects SAML logins. This issue can occur after upgrading from an earlier version of self-hosted Retool to one of following affected versions:
| Channel | Affected versions |
|---|---|
| Stable | 3.148.12-stable |
| Stable | 3.114.24-stable |
Retool has released 3.148.13 and 3.114.24 on the Stable channel which resolves the issue.
If you have a deployment that currently runs an earlier version of self-hosted Retool, do not upgrade to an affected version.
Retool recently made changes that make it easier to review changes in source control. Retool now separates system-generated updates related to version upgrades into their own migration commit, so your pull requests are cleaner and easier to understand.
\nThis feature is generally available to cloud instances and self-hosted instances on version 3.203.0-edge or later, and will be generally available in an upcoming stable release. Self-hosted Retool organizations can reach out to support to enable this feature.
\nInstead of bundling migration changes with user changes, they now appear in a dedicated commit.
\n![](\"https://docs.retool.com/assets/images/migration_commits-affe1b57e77a4e846b5b6bc7d04caa17.png\")
No setup needed—this happens automatically when you make commits.
\nThis migration commit is required to ensure compatibility with the latest Retool features. Please do not revert or modify it.
Retool now supports an integration to the Tavily Search API. Use this integration to perform either general or news-specific web searches. You can choose to provide your own Tavily API key if you do not want to be subject to Retool's rate limits (100 calls per 24 hours) on Tavily.
", "url": "https://docs.retool.com/changelog/tavily", "title": "Tavily integration", "summary": "New integration with Tavily", "date_modified": "2025-05-21T12:00:00.000Z", "tags": [ "Integrations", "New", "Beta" ] }, { "id": "https://docs.retool.com/changelog/disclosures/cve-2025-47949", "content_html": "A vulnerability in an open-source library, samlify, which Retool uses for SAML login implementation, allowed for account takeovers through forged SAML identity provider (IdP) assertions. In the worst case, an external threat actor could forge arbitrary assertions for a SAML IdP, potentially leading to full account takeovers within an organization. An attacker would need a signed XML document by the identity provider. Version 2.10.0 fixes the issue. This exploit requires no user interaction and an attacker could gain unauthorized access to an organization with escalated privileges.
\n| Field | Value |
|---|---|
| Vulnerability Type | Improper Verification of Cryptographic Signature |
| Package | samlify |
| Affected Component | Retool organizations using SAML SSO |
| Attack Type | Remote |
| Impact | Account Takeover |
| Reference | https://nvd.nist.gov/vuln/detail/CVE-2025-47949 |
| Discoverer | Alexander Tan (ahacker1) |
| Branch | Versions |
|---|---|
| Edge | 3.207.0-edge |
| Stable | 3.196.2-stable |
| Stable | 3.148.13-stable |
| Stable | 3.114.25-stable |
| Release branch | Release versions |
|---|---|
| Edge | 3.111.0 to 3.203.0 |
| 3.196-stable | 3.196.0 to 3.196.1 |
| 3.148-stable | 3.148.0 to 3.148.11 |
| 3.114-stable | 3.114.0 to 3.114.23 |
| < 3.111.0 |
An improved version of the File Input component for Mobile is currently available to cloud instances and self-hosted instances on version 3.168.0 or later.
\nThis includes:
\nvalue property in the component state.