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.

Retool is deprecating versions 1.0 and 2.0 of the Microsoft SQL integration. Organizations with Microsoft SQL resources still using these versions must update their resource configuration to use version 3.0.

This deprecation will first take effect on cloud instances on August 24, 2026. It will then take effect in the next edge and stable releases that follow.

Version 3.0 has been available since February 2, 2026 for cloud instances and the 3.334 stable release. If you haven't intentionally created a resource on an older integration version, your resource is likely already on version 3.0 and requires no changes.

To upgrade an existing resource, open its settings from the Resources page, change Connector version to Version 3.0, and save your changes.

Versions 1.0 and 2.0 will be removed entirely from cloud instances in Q4 2026, followed by the subsequent edge and stable releases. After that, apps, workflows, and queries that depend on Microsoft SQL resources still using version 1.0 or 2.0 will stop working.

When prompting in the Chat tab of the app builder, the agent asks clarifying questions to better understand your intent and create your desired outcome. The agent can ask multiple-choice or open-ended questions.

You can now build apps with more AI models: Claude Sonnet 5, the GPT-5.6 models (Sol, Terra, and Luna), and Claude Fable 5. Choose a model for each thread in the app builder's Chat tab. Admins can set the organization's default app building provider and model in the AI settings.

Claude Sonnet 5 can be used on paid plans with a Retool-managed key or your own key. The GPT-5.6 models and Claude Fable 5 require you to bring your own key, which is available on the Enterprise plan.

You can now upload files to be used as assets in your app through the Chat tab in the app builder. Previously, uploaded files could only be used as context for the agent.

Common use cases for uploaded files as assets include:

  • Embedding PDFs.
  • Adding a company logo to the app header.
  • Presenting images within the app.
note

This change applies only to apps built using the new app builder, not to classic apps.