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.

Tags

Tags

Tags

Retool now supports manual file management of apps from the Code tab of the app builder. This enables builders to exercise finer-grained control over code files without needing to prompt the agent and consume credits.

Builders can manually add:

  • Folder: A new empty folder inside the frontend or backend directory of your app.
  • Frontend component: A new TypeScript file that represents a React component, which Retool populates with a basic structure of the component.
  • Frontend file: A new generic frontend file. Provide the full file name, including the file extension.
  • Backend function: A new TypeScript file that represents a function, which Retool populates with the basic structure of a function.
  • Backend file: A new generic backend file. Provide the full file name, including the file extension.

Builders can also delete certain files or folders, including those that define components and backend functions, or other temporary or user-written files.

Tags

You can now queue messages in Chat tab of the app builder. While the agent is working, you can send up to five messages, which will be automatically sent in a batch once the agent responds.

You can edit or remove messages from the queue before they are sent, or clear the queue of all messages.

Tags

Tags

Tags

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

Retool releases a version on the stable channel each quarter. 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.

Tags

Retool made signficant improvements to the efficiency and performance of the app building agent. Builders will notice faster agent responses and lower AI credit consumption, especially on long-running building sessions. These improvements can result in up to 50% fewer credits consumed.

Tags

Retool is deprecating the dedicated BigID resource type.

Retool will remove the resource type in Q1 2027, after two quarterly Stable releases. After removal, BigID resources will stop working. Queries in apps and workflows that still point at those resources will fail. Cloud and self-hosted organizations will not have a BigID connection option after removal.

Organizations can keep querying BigID after removal by creating an OpenAPI or REST API resource. Retool will not migrate BigID resources or their query references automatically.

  1. Create an OpenAPI resource with specification URL https://sandbox.apps.mybigid.com/BigAPI.yaml or the BigAPI.yaml URL for your BigID instance, and environment server variable set to your BigID hostname. For REST API, set the base URL to https://HOSTNAME/api/v1.
  2. Set Authentication to Custom Auth. Add an API Request step that sends POST /api/v1/refresh-access-token with your BigID user token in the Authorization header. Add a Define a variable step named SYSTEM_TOKEN with value {{ http1.body.systemToken }}. Add an Authorization header on the resource that uses {{ SYSTEM_TOKEN }}. Enable Run this custom auth workflow without prompting the user. Configure a refresh auth workflow that repeats the exchange after a non-200 response. Generate the user token in the BigID UI and exchange it as described in BigID's token authentication.
  3. Open each app, workflow, and Query Library query that uses the BigID resource. Change the query to use the new resource, then test it. For OpenAPI, select the same operation. For REST API, recreate the request as method and path, such as GET /ds-connections. If the OpenAPI query editor shows an Authorization parameter, leave it empty.

Custom authentication is not supported in public apps. If you have a large number of BigID queries and need help finding them, contact Retool Support.

Tags