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.

READMEs can now be protected for apps that use Source Control. For existing apps that have a README, Retool will add a README.md file to your repository with your next commit. If you are protecting an app for the first time, Retool will include the README.md file automatically.

This feature is currently rolling out to cloud instances and will be available to self-hosted instances on an upcoming edge release.

As a form of feedback, you can now submit prompts from the help button. Find the help button at the bottom right of pages like the apps or resources landing page. Each prompt triggers an internal prototype generated with AI, which Retool can use to improve the product. If Retool implements the feature, you can choose to be credited with your name in the changelog.

Retool would like to thank the Conductor team, who inspired this change with their recent update.

Retool has two new improvements to the API:

  • A new per-instance API reference is now available at {your-instance}/reference. The reference is available on all cloud instances and served locally by self-hosted deployments within its VPC—no internet connection required. The API reference reflects only the API version running on your instance and always matches what's available to you.
  • The API version now tracks the Retool release version. The Retool API version now corresponds to your instance's release version. This makes it easier to track Retool API changes whenever your instance is updated.

Retool now uses a service worker in the browser to cache the application frontend so that pages load faster when you revisit them. The service worker uses a stale-while-revalidate strategy: it serves the previously cached version of a page immediately, then fetches the latest version from Retool in the background. If a newer version is available, Retool automatically refreshes the page so you see the latest changes.

The cache is version-aware and automatically invalidates after a Retool upgrade, so you always end up on the latest version of the platform without needing to clear your browser cache. A hard refresh (Cmd+Shift+R / Ctrl+Shift+R) bypasses the cache and loads the latest version directly.

The service worker is enabled by default on cloud instances and on self-hosted versions 3.334-stable and later. Admins can disable it from Settings > Beta if they need to diagnose page load issues in their organization.