Updates, changes, and improvements at Retool.
You can now connect any AI provider that adheres to the OpenAI, Anthropic, Google, or Cohere schema. This enables you to connect from a wide range of AI providers, such as Mistral, Fireworks AI, Together AI, and OpenRouter.
Organizations with increased security and compliance requirements can also configure custom AI providers if they need to route traffic through their own proxies.
Self-hosted Retool 3.75 is now available on the Stable release channel.
The Comment Thread component enables users to post comments and start discussions directly within your apps. All users who have access to an app that contains Comment Thread can use the component. Each user's comment appears with their name and avatar image.
Comment Thread with comments for the selected table row.
When using Comment Thread, you specify a unique thread ID with which to associate comments. This can be a dynamic value so that comment threads dynamically change based on user interactions. For example, setting the thread ID to {{ table1.selectedRow.id }} would associate comments to whichever row is currently selected.
Comment Thread includes event handler support, action buttons, and granular control over the refresh period. Retool automatically handles comment storage and retrieval so no data source is needed.
If you're currently using the Comment component, you can switch to using Comment Thread without losing previous conversations by using the current Evaluated key value as the thread ID.
Retool released a new version of the List View component in December 2023. The previous version has continued to be available as the Legacy List View component. You can continue to use the Legacy List View component in existing apps but we recommend you switch to using the newer List View component. The newer version of List View is much more performant, has more features, and will receive updates.
Learn more about the differences between Legacy List View and List View.
| Feature | Legacy List View | List View |
|---|---|---|
| Number of instances | Set the instances property value. | Automatically generated for each array item in data. |
| Instance values | Reference nested values using the item index (e.g., textInput1[3].value). | Nested components cannot be referenced outside of List View. For form inputs, use instanceValues instead. |
| Instance keys | Item keys. | Primary keys. |
| Auto-height | Automatically grows with content. | Requires a suitable maxHeight value. |
| Show border | Yes | Nest the List View component within a container and use it to set the border. |
| Show drop shadow | Yes | Nest the List View component within a container and use it to set the drop shadow. |
| Styles and nested styles | Yes | Nest a container within List View to apply styles and nested styles. |
Retool recommends using primary keys, a unique identifier, to track and restore instances within the List View.
List View is virtualized and only evaluates and renders items currently visible. This significantly improves performance. However, this also means that you can no longer directly reference nested items as they may not have been evaluated yet. Instead, you can reference instance values for forms and input components.
List View supports all of the same appearance settings as Legacy List View, with the following exceptions:
heightType of auto requires a suitable maxHeight value to maintain performance. The default is 100vh and you can specify a different value to use. You should consider using the container in which List View is nested to avoid unexpected scrollbars.The Stack component is a container with Flexbox-like layout controls. Instead of following the standard 12-column grid layout, Stack automatically arranges nested components horizontally or vertically. You can then control the alignment and distribution of nested components and precisely adjust component size.
The Microphone component for Retool Mobile can record audio using the built-in microphone. Recordings are Base64-encoded in WebM format, and audio playback displays a progress bar and elapsed time.
The Slider component for Retool Mobile enables users to select a number value with a UI slider.
The Slider component for Retool Mobile
Multipage apps contain pages to combine functionality and use cases. Standard Retool apps operate as single-page applications where all code and components is continually evaluated. Multipage apps are also supported by Retool Mobile where each screen functions as a separate page.
With multipage apps, Retool only evaluates the code and components of the page currently in view. The benefits of multipage apps include:
Each multipage app uses global and page scopes to separate pages. Globally scoped code, and Header and Sidebar frames, are available for use across every page, while each page has its own page-scoped code and components.
You can request access to the multipage app beta and explore the docs to learn more.
Retool is currently working on a new layout architecture, WidgetGrid, that significantly improves the performance of the canvas. Placement and arrangement of components, such as dragging to reposition, is up to 50% more responsive.
Enable or disable WidgetGrid from the status bar.
WidgetGrid is currently rolling out to cloud-hosted organizations as an opt-in beta and will be available in the next Edge release of self-hosted Retool. You can enable WidgetGrid from the status bar when viewing or editing an app. You can disable WidgetGrid at any time and provide feedback about any issues you experienced.
Browsers now load static .js files from the following locations:
/libs/custom-component-collections.${hash}.umd.js/libs/custom-components.${hash}.umd.js/libs/sandbox.${hash}.umd.jsThis change will not disrupt most self-hosted organizations. However, if you have additional infrastructure that sits between your user's browser and your Retool instance, such as a load balancer, you might need to update your infrastructure configuration.
The reason for this is because these files are requested from an iframe, and so regular browser cookies will be missing from those requests for these files. If you have a load balancer that requires additional cookies be present (such as for SSO), it may block requests to these files from an iframe.
If you need to account for this, the recommend solution is to allow-list requests to these file paths in your infrastructure so that they don't require any additional authentication to access.
Perform these tests if you want to confirm that your Retool instance is correctly serving these files: