Changelog

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.

Retool now supports hardened images, which are now available on the self-hosted stable release channel. These images are designed to improve supply-chain security, reduce the attack surface, and support modern infrastructure while remaining functionally compatible with existing deployments. Learn more about hardened images in the conceptual guide.

Plan your migration​

Use the following high-level steps to evaluate and roll out hardened images.

1. Review requirements and environment​

• Confirm that your environment meets the Self-hosted Retool requirements, including network and egress configuration.
• Identify any current reliance on shell access, system tools, or custom image modifications.
• Review your update process in Upgrade deployments and your overall deployment model in the Self-hosted quickstart.

2. Test hardened images in non-production​

Retool strongly recommends testing hardened images on non-production instances first, for example:

• A development or staging instance in a separate Virtual Private Cloud (VPC) or cluster.
• A temporary test environment built using the Docker or Kubernetes deployment guides.

When testing:

• Update your manifests or Docker Compose files to use the appropriate *-stable-hardened tags.
• Verify your critical apps, workflows, and database connections behave as expected.
• Check container health, logs, and telemetry using Container logs and Collect self-hosted telemetry data.

3. Roll out to production instances​

When you're ready to use hardened images in production:

• Follow your usual deployment and rollout process. For example, use the near-zero downtime strategy in Scale your self-hosted deployment infrastructure.
• Upgrade instances sequentially (development → staging → production) and validate each step.
• Communicate with your users about maintenance windows and any expected changes.

If you encounter regressions, you can temporarily roll back to classic images by reverting your image tags while you work to diagnose and resolve issues.

Stable channel timeline​

Over time, hardened images will become the recommended default for production deployments, and classic images will eventually be phased out.

To stay current on timelines and support windows, monitor the Stable releases and Self-hosted requirements documentation.

Self-hosted Retool 3.334.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.

Retool made significant design updates to the workflows landing page to improve user experience and align more closely with the agents landing page.

The landing page displays all workflows, and folders containing workflows, for your Retool organization. You can perform the following actions from the landing page:

• Sort workflows by Name, Last Updated date, or Created date.
• Search for workflows.
• Toggle between Grid view or Table view.
• Refresh the workflows list.
• Import a workflow from JSON.
• Create a new Folder.
• Create a new Workflow.
• Create a workflow From Template.

Claude Sonnet 4.6 and Opus 4.6 are now available in Retool through Anthropic and Amazon Bedrock. Sonnet 4.6 and Opus 4.6 can both be used with AI resource queries. Opus 4.6 requires you to bring your own key for AI resource queries.

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.

Toggle the Template variables in Source Control config feature flag in Settings > Beta to enable this feature.

• 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 users 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."