Updates, changes, and improvements at Retool.
Refer to the stable and edge release notes for detailed information about self-hosted releases.
The Settings navigation is reorganized into clearer, task-based groups so you can find what you need more quickly.
Settings are now grouped under the following sections: Management, Monitoring, Permissions, Authentication, Features, and Customization. For example, Users, Groups, Roles, and User attributes are grouped under Permissions, while Single sign-on (SSO) and IAM credentials are grouped under Authentication.
Settings navigation update.
Admins can now use the Overview page in Settings to set up their Retool organization and respond to pending user requests.
The Get started section guides you through configuring the core areas of your organization, including single sign-on (SSO), resources, permissions, spaces, source control, and the Retool API.
Retool marks each step as complete once you configure it, and you can mark any step that does not apply as not relevant. The module is hidden once you complete the Get started steps.
The Overview also surfaces pending join requests and suggested users, so you can approve new members without leaving the page.
Retool 4.1 is now available on the Edge release channel for self-hosted organizations.
The following patches are now available on the Stable release channel:
Update your Retool instance to apply the latest bug fixes and security patches.
Retool's new app builder now supports importing React apps from external sources, such as Replit, Lovable, and Claude Code, for further refinement and development in Retool.
To import your React app in Retool, generate a .zip file of the code, and select Import React code from the app builder. Learn more about how it works.
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:
To get started, first protect your app. Then you can create, publish, and tag new versions.
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:
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.
Using the MCP server to build classic apps is not supported.
Claude Opus 4.8 is now available on Retool Cloud through Anthropic and Amazon Bedrock. It can be used with AI resource queries, with Retool Agents, and in Assist. Support for self-hosted Retool is coming in an upcoming release.
A new AI-powered app builder is now available to cloud instances. 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 updated app builder is available in cloud instances. It will be available in upcoming stable and edge releases.
The app builder includes:
Apps run on React 19 and a curated set of supporting libraries.
Apps built using Retool's drag-and-drop IDE are now called classic apps. Apps refer to apps created in the new app builder.
Retool 3.396 is now available on the Edge release channel for self-hosted organizations.