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.

127 posts tagged with "Apps"

Updates related to apps.

View All Tags

Customize the Content Security Policy for apps

Admins can now customize the Content Security Policy (CSP) that Retool enforces on apps. Retool applies a strict default policy that restricts which origins an app can load scripts, fonts, images, and other resources from. You can now extend that policy org-wide to allow the additional origins your apps need, or tighten the defaults further.

For example, if custom JavaScript in an app loads a charting library from a CDN such as https://cdn.example.com, the default script-src 'self' policy blocks the script and the app fails to render it. You can now add that origin to script-src so the app can load it without loosening the policy for any other resource.

note

Custom CSP applies only to apps built in the app builder. It does not apply to classic apps.

Configure rules in Settings > App security > Content Security Policy. Changes apply to every app in your organization and are recorded in your audit logs.

For more information, refer to Customize the Content Security Policy for apps.

Restore changes from chat

While prompting from the Chat tab in the new app builder, you can now restore the app to a previous state. Each time the agent finishes making changes, it presents a summary of the changes and a Restore button. Click this button to return your app to the state it was in when the agent finished those changes.

Browser notifications when app building

Retool now supports audio and visual browser notifications for app building. If you prompt Retool to build an app and navigate away from the tab, a ping sounds and a red dot appears on the favicon of the tab when you need to return to it. Now, you can multitask and return to the app builder only when your input is required.

This notification occurs at the following key points in the building process:

  • The agent needs you to provide input or make a choice (such as selecting a resource).
  • The agent needs your approval to run a function.
  • The agent is finished building.

To turn off the notification sound, click the Model options selector in the prompting box and toggle off the Sound notifications setting.

Import apps using MCP

You can now use Retool's MCP server to import React apps directly from your agentic coding environment.

Open a React app, and ask Retool to import the app. Retool guides you through the process of selecting the appropriate resources, and sends you a link to the newly imported app in the app builder. From there, you can make tweaks to the generated app, and securely publish the app using the MCP server or from the app builder.

Protect apps in the new app builder

Apps created with the new app builder can now be protected and checked into your chosen Source Control Manager (SCM). Source Control lets organizations manage changes using remote SCM providers GitHub, GitLab, AWS CodeCommit, Bitbucket, and Azure Repos. Using this distributed approach, your users can:

  • Prevent unwanted changes to apps.
  • Work collaboratively and methodically through reviews.
  • Edit React code from your preferred development environment.

To get started, first protect your app. Then you can create, publish, and tag new versions.

Build apps via MCP

note

App building with the MCP server is available in cloud instances. It will be available in upcoming stable and edge releases.

Builders on cloud instances can now use Retool's MCP server to build apps. Apps are built using React and use Retool's updated app builder. Connect the MCP server to Claude, ChatGPT, Codex, Cursor, Kiro, or another agentic coding environment, and describe the app you want to build. Retool's building agent generates the app and returns a preview link. Publish and manage the app from the app builder.

Beyond initial generation, you can also use the MCP server to:

  • Continue building or iterating on an existing app.
  • Monitor active builds and view past agent activity.
  • Review function runs that require human approval.
  • Inspect or read the files of an existing app.
  • Cancel a failed or in-progress build.

App building tools require the user to be a builder, and the builder must authorize the mcp:write scope. Refer to the tools reference for the full list.

note

Using the MCP server to build classic apps is not supported.

Retool's new app builder

A new AI-powered app builder is now available. Build production-ready React apps using natural language in the app builder or through your favorite coding agent via MCP. Whatever or however you build, everything inherits the security standards your organization has already approved and implemented.

The app builder includes:

Apps run on React 19 and a curated set of supporting libraries.

Admins can use the configuration guide to set up their organization to use the new app builder.

note

Apps built using Retool's drag-and-drop IDE are now called classic apps. Apps refer to apps created in the new app builder. Learn more.

Defer module evaluation

App builders can now defer the initialization of modules until they're viewable to improve the initial loading time of larger apps.

note

To enable this public beta, navigate to Beta > Settings and enable [Perf] Module deferred evaluation.

When an app is initially loaded, Retool initializes all code, components, and modules. However, a common use case for modules is including them in conditionally hidden frames, and these modules don't need to be loaded when they are still hidden.

Modules now have a new option in the Inspector: [Beta] Defer evaluation until visible. When a “deferred” module is hidden (either ‘hidden’ state is true, or it is in a hidden frame, or otherwise not being rendered), Retool defers the module's initialization. When the module is shown, Retool invokes the initialization procedure that would typically happen during app startup.

This gives builders more flexibility in how components are loaded in their apps, and large apps load more quickly.