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.

Version 3.0 of the Microsoft SQL integration accepts array values in query parameters. Retool converts an array to a comma-separated string before passing it to SQL Server, which matches the behavior of version 1.0.

Retool previously documented this as a breaking change and recommended converting array values with .join(',') before using them with STRING_SPLIT. The restriction was broader than documented: it applied to any query parameter set to an array value, whether or not the query used STRING_SPLIT. Version 3.0 removes the restriction entirely, so queries that pass array values no longer need to be rewritten. Queries that already use .join(',') produce the same value and continue to work without changes.

This was the only known breaking change between version 1.0 and version 3.0. You can now update an existing Microsoft SQL resource from version 1.0 or version 2.0 to version 3.0 without changing your queries. Versions 1.0 and 2.0 are deprecated and will be removed, so Retool recommends updating any resource still using them.

Query parameters set to an object are not supported and cause the query to fail. Convert an object to a string before using it in a query, for example with JSON.stringify.

Retool introduced several features to help Enterprise organizations manage AI usage.

Use the new centralized settings page, AI visibility, to view AI credit usage and BYOK AI token usage. Navigate to Settings, and select Retool managed keys or Bring your own key from the dropdown at the top of the page. You can filter AI usage by instance, model, user, and feature.

note

This page is available on Enterprise plans. Admins can access it, and other users can access it with delegated Manage billing and Manage usage analytics permissions. Available views depend on the user’s permissions.

Enterprise organizations can also use the new Get AI credit usage endpoint to measure the number of credits consumed for each AI resource that uses a Retool-managed key. You can view the number of credits consumed by resource, user, and surface area.

Learn more about credit and token monitoring.

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.

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.