Changelog

The following integrations were previously in public beta and are now generally available:

• Amazon SNS
• Amazon SQS
• Apache Kafka
• Tavily Web Search

Retool no longer supports GPT 3.5 Turbo. GPT-4o-mini will be used instead.

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.

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.

Retool released some updates and improvements to the Assist experience:

• You can now prompt Assist to write a README for your app. When you're editing an existing app, Assist can also use information from existing READMEs to learn about the app context and improve the quality of changes.
• Assist automatically names apps. When you use Assist to create a new app from a blank canvas, Assist provides a descriptive name.

These changes are live on Retool Cloud. Refer to the edge release notes for information about what features are available to self-hosted organizations.

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.

Source Control for agents operates similarly to how it does for apps, but with some key differences.

• Agents cannot be moved or renamed. Protected agents and the folders in which they're located cannot be renamed or moved. You must unprotect agents before making name or location changes. Protected agents must have a unique name.
• Agent triggers cannot be protected. You can edit the trigger of a protected agent without creating a commit.
• Evals and Datasets are incompatible. You cannot access evals and datasets from a protected agent.

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.

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.

Claude Haiku 4.5 is now available in Retool. It can be used with AI actions and with Retool Agents.

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.

For workflows that are already protected, you now have the option to protect triggers using a new PR.

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

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

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.