Changelog

When creating a new REST API resource, you can now connect an OpenAPI or Swagger specification. Connecting an API specification enables:

• Autocomplete: Get endpoint and parameter suggestions when writing queries.
• Validation: Retool validates requests against the specification schema.
• Better Assist: Assist can more effectively generate queries based on the specification.
• Documentation: Endpoint descriptions from the specification appear in the query editor.

When working with resources, users can also manually create endpoints or parameters that aren't included in the specification.

Source Control configuration now supports embedded expressions in sensitive credential fields, including access tokens, passwords, private keys, and SSH keys. This enables secure credential management using configuration variables and secrets.

• On cloud and self-hosted instances, you can reference configuration variables:

  {{ environment.variables.MY_KEY_OR_TOKEN }}
  

• On self-hosted instances only, you can also reference secrets from secrets managers:

  {{ secrets.MY_SECRET.KEY }}
  

Embedded expression support is available for all Source Control git providers: GitHub, GitLab, Bitbucket, Azure Repos, and AWS CodeCommit. The UI includes field captions, autocomplete, and validation to help you use embedded expressions correctly.

Non-sensitive fields like repository names, branch names, and usernames do not yet support embedded expressions.

Newly created apps now have their Max width value set to 1200 px by default. This change improves usability and responsiveness.

Existing apps are unchanged. If you want to adjust the maximum width of your app, navigate to the Inspector and adjust the Max width setting in the Spacing section.

Starting February 23rd, Retool will roll out provider-specific AI resource integrations (e.g., OpenAI, Anthropic, and Bedrock) in place of the singular Retool AI resource. This change is part of a broader effort to make AI integrations behave more like other resources in Retool: more flexible, more governable, and easier to scale as usage grows.

These changes will first roll out to cloud instances. Self-hosted instances can expect to receive the changes in a future release. There are no pricing or packaging changes associated with this update.

No action is required to facilitate this change. All existing apps, queries, workflows, and agents will continue to work based on existing configurations.

What's changing​

Instead of a single Retool AI resource, AI providers will function like any other resource at Retool. This allows for more flexibility when using AI, such as:

• Using multiple API keys per provider (e.g., by team, resource environment, or use case) so you can better manage access and usage limits.
• The same granular permissions and governance controls, allowing admins to decide who can create or modify specific AI resources.
• Clearer auditability and visibility into which apps and workflows are using which provider and key.
• Easier multi-provider setups, letting you mix and match models from different providers in the same workspace.

The dedicated AI Action query is also being deprecated as its functionality will be available in AI resource queries.

Retool now supports controls for configuring your app theme while prompting Assist.

• Free and Team plan useres can choose between light or dark mode and select an accent color.
• Business and Enterprise plans support organization-level theming. Alternatively, users can select a theme preset.
• All plans can configure an app theme via the prompt. Be very clear and specific about your design intent. For example, "Create a dark mode theme with blue accent colors", or "Update the theme to match the Acme brand colors and style."

Retool released a Version 3.0 of the Microsoft SQL Server integration that includes various fixes and improvements. New Microsoft SQL resources will use this version by default. Existing resources can be updated using the Connector version setting.

Beginning in the 2026 Q3 stable release, Version 1.0 and Version 2.0 of the integration will be deprecated. Retool strongly recommends that you update your resource configuration before Q3 in order to prevent any interruptions and to resolve any unforeseen issues. If necessary, Retool may automatically migrate resources to Version 3.0 in order to ensure any issues are identified and resolved prior to the removal of the old versions.

There is a known breaking change introduced in Version 2.0 that will also apply when upgrading from Version 1.0 to Version 3.0:

Beginning in Version 2.0, array inputs must be passed as a string when used in string_split in order to pass the Microsoft SQL SDK validation. For example, select * from string_split({{[1,2,3]}}, ','); must change to select * from string_split({{[1,2,3].join(',')}}, ',');.

No breaking changes are expected between Version 2.0 and Version 3.0.

For Enterprise and Business plans, Retool now allows admins to control access to Assist and its Ask and Build modes. Organization admins can use roles and permissions to create roles and edit roles with one of the following permissions:

• Use Assist with Ask and Build mode
• Use Assist with Ask mode only
• No access to Assist

By default, all users have access to Assist and both Ask and Build mode through a preconfigured role. This role is called Assist Role or Editor, based on when your organization was created. Organization admins can edit these roles, or they can create new roles with more restrictive permissions.

This change is valuable for organizations that need to limit or prevent Assist usage to specific populations of users. For example, admins might wish to restrict Assist usage to user groups who do not have access to sensitive data or PII. Alternatively, admins could restrict access to all user groups except for a pilot group testing AI tools.

Multi-instance releases are now generally available to cloud instances and self-hosted instances on version 3.330 or later, with support for both apps and workflows.

Organizations using Source Control can manage releases of protected apps and workflows across multiple deployment instances. This feature enables you to publish different release versions across instances, making it easy to test newer versions on staging or development instances before promoting to production.

Beginning in the Q3 2026 stable release, self-hosted instances using the multiplayer feature must set the LICENSE_KEY environment variable on the multiplayer service container. While this environment variable is not yet required, Retool recommends setting it now to avoid any service interruptions.

Assist now supports the ability to create and edit multipage apps. Previously, Assist could only work with one page at a time.

Assist can now:

• Plan and build a multipage app from scratch.
• Create, edit, and rename pages.
• Move queries and code between global and page scopes.
• Create globally-scoped frames and components, such as Navigation, to help users move between pages.
• Identify and correct page scope errors.

While Assist is generating, navigating between pages is disabled to prevent errors.