Changelog

The Fullstory integration for session replay is now generally available.

When 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.

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.

Internationalization (i18n) is now generally available for organizations on the Enterprise plan. This allows you to localize Retool app content and data.

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.

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.

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.

Role-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.

Once 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.

To enable this feature, navigate to Settings > Beta and enable Permissions v2.

OAuth 2.0 is now supported when adding an MCP server as a tool for an agent.

Self-hosted Retool 3.253.0 is now available on the Stable release channel.

Retool 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.

Preparation 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.

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.

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.

Retool removed some JDBC connectors that were inadvertently included in certain self-hosted release versions. These include:

• Actian Ingres/Vector JDBC Driver.
• Clickhouse JDBC Driver.
• IBM Data Server Driver for JDBC.
• IBM Informix JDBC Driver.
• Trino JDBC driver.

These 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.

Retool has since released patch updates for affected releases that remove these connectors.

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.