Skip to main content

Changelog

Updates, changes, and improvements at Retool.

Refer to the stable and edge release notes for detailed information about self-hosted releases.

121 posts tagged with "Apps"

Updates related to apps.

View All Tags

Expanded source control managers for multi-instance releases

Enterprise organizations can now implement multi-instance releases for apps using any supported SCM provider: AWS CodeCommit, Azure Repos, BitBucket, GitHub, and GitLab.

To enable multi-instance releases, navigate to Settings > Source control > Edit settings and turn on Enable multi-instance releases.

This feature enables you to publish different release versions across instances, making it possible to test a newer version on staging or development instances before promoting to production. Get started with multi-instance releases for apps.

Build resource environment switching for published apps

Organizations on paid plans can prompt the app building agent to use resource environments in published apps. Resource environments enable you to run a function against different configurations of the same resource, such as staging and production, and were previously only available in Edit mode for apps.

note

Published apps do not include an environment toggle by default.

Optionally, prompt the agent to add a UI element that allows app users to switch between resource environments.

When the user is not in the Finance Admin group, use the staging resource environment.
I want to use this app across resource environments. Add a dropdown in the top right corner.

In addition, you can use the _environment URL query parameter to open an app in a different environment, such as ?_environment=staging. This URL parameter works automatically and does not require prompting.

Retool-provided AI models on the Business plan

Organizations on the Business plan now have access to Retool-provided AI models for app building. These models, prefixed with Retool, have been tuned by Retool for enhanced performance and speed for app building.

The following Retool-provided models are supported:

  • Retool Mini
  • Retool Power

Custom authentication for embedded apps

Business and Enterprise organizations can now use the Retool API to authenticate apps that are embedded in an app or website external to Retool.

Once configured, the custom authentication flow exchanges an API token for an embed URL. When a parent app authenticates a user using your preferred authentication method, the parent app makes an API request to Retool to generate an embed URL. This embed URL is a secure, single-use link on the domain of your published app. Loading it in the iframe exchanges the link for a session, sets the cookies the app needs, and then displays the app.

Standard authentication through Retool remains supported.

note

This flow is available for apps published on a cloud instance that use the standard Retool domain (example.retool.com). It is not available to self-hosted instances or organizations that use a custom domain.

Retool-provided AI models on the Team plan

Organizations on the Team plan can now use Retool-provided AI models for app building, in addition to the full catalog of supported models. These models, prefixed with Retool, have been tuned by Retool for enhanced performance and speed for app building.

The following Retool-provided models are supported:

  • Retool Mini
  • Retool Power

Changes to available AI models on the Free plan

Organizations on the Free plan now use Retool-provided AI models for app building. These models, prefixed with Retool, have been tuned by Retool for enhanced performance and speed for app building. Access to models from other providers is now only available on paid plans.

Builders using these models will notice comparable quality and faster speeds when compared with other models previously available on the Free plan.

The following Retool-provided models are supported:

  • Retool Mini
  • Retool Power

Use external MCPs in app builder

Retool now supports using external MCPs as resources in the app builder. The app building agent creates function calls to utilize tools from your connected MCP servers, which can be used while building or at app runtime. For example:

Use the @Genie OneMCP resource in a chat component so that my app users can ask natural language questions about data
Use @Linear MCP and make changes described on ticket TOOL-1203

Users of the published app can only trigger MCP tools for which they have permission.

note

This functionality enables you to use MCP servers from other companies or services in your app. Retool also provides an MCP server with which you can manage your organization and build apps.

Retool CLI

The Retool CLI is now available in public beta. It enables you to build, manage, and publish Retool-native React apps from the command line and with the help of your chosen code development agent harness, like Claude Code or Codex.

With this tool, you can write and validate app code directly on your machine. You can use the CLI independently or pair it with a local development agent. Follow the installation instructions to get started, learn how the CLI works, or compare the CLI to the MCP.

note

Retool supports an existing CLI that is used exclusively for classic apps. This CLI is now deprecated. It will be removed from cloud instances on March 1, 2027, and from stable instances in the Q2 2027 stable release.

Embed apps in iframes

You can now embed apps in other apps, in classic apps, and in apps or websites outside Retool using an iframe. To enable app embedding, an organization admin adds Content Security Policy directive rules that name the pages that are allowed to frame your app.

Refer to the Embed apps guide to learn how.