Retool now supports performing web searches from the Chat tab of the app builder and from functions in draft or published apps. While building apps, the agent can access the internet to answer questions or provide more context. Web searches use a Tavily account that Retool manages for you.

Your apps can also use functions to perform web searches. Prompt the agent to include the search functionality that the users will need.

Web search is on by default. Admins can disable this feature by toggling off Web search in Settings > AI.

You can now use the Build with tests setting to validate that your app is functioning as expected and catch unintended changes before you publish your app to end users. Toggle this setting on from the chat settings or from the debug console.

When app testing is enabled, the agent writes or updates tests whenever it adds or changes behavior in your app. By default, the agent writes a small set of behavioral tests. After the agent makes any changes to your app, Retool runs the tests related to those changes. If any of them fail, Retool sends the failures to the agent, which continues working to fix them.

Retool now supports the use of private npm registries for apps. Enterprise organization admins can add registries in Settings > App Security, and builders can then ask the agent to install packages from them. Use private registries to:

• Download a specific package from a private registry. For example, pull a design system that you host on your own servers into your apps.
• Download all packages from a specific registry. Add a registry as the default, or route entire npm scopes (such as @acme) to it. Registries can require authentication with a bearer token or basic auth, or allow anonymous access.
• Control which packages are allowed. Build your own registry with rules about what it permits users to download. For example, enforce a minimum package age that you configure yourself.

Private registries must be npm-compatible and use HTTPS.

Retool's AI-powered app builder is now generally available. Since first releasing the app builder in May 2026, Retool has continually expanded its capabilities to include:

• The ability to build from anywhere using the MCP server or CLI. Learn more about the difference.
• Flexible prompts that enable planning changes, creating new resources, or queueing messages.
• Comprehensive support for all resources available in Retool.
• Full source control support, including protecting apps, transitioning between development environments, and multi-instance releases.
• Expanded management tools, including custom Content Security Policies, org-wide agent context, and the ability to embed apps.

Whatever or however you build, your apps inherit the security standards your organization has already approved and implemented.

To get started, admins can use the configuration guide to set up their organization to use the app builder.

Enterprise organizations can now implement multi-instance releases for apps using any supported SCM provider: AWS CodeCommit, Azure Repos, BitBucket, GitHub, and GitLab.

To enable multi-instance releases, navigate to Settings > Source control > Edit settings and turn on Enable multi-instance releases.

This feature enables you to publish different release versions across instances, making it possible to test a newer version on staging or development instances before promoting to production. Get started with multi-instance releases for apps.

Organizations on paid plans can prompt the app building agent to use resource environments in published apps. Resource environments enable you to run a function against different configurations of the same resource, such as staging and production, and were previously only available in Edit mode for apps.

Optionally, prompt the agent to add a UI element that allows app users to switch between resource environments.

In addition, you can use the _environment URL query parameter to open an app in a different environment, such as ?_environment=staging. This URL parameter works automatically and does not require prompting.

Organizations on the Business plan now have access to Retool-provided AI models for app building. These models, prefixed with Retool, have been tuned by Retool for enhanced performance and speed for app building.

The following Retool-provided models are supported:

• Retool Mini
• Retool Power

Business and Enterprise organizations can now use the Retool API to authenticate apps that are embedded in an app or website external to Retool.

Once configured, the custom authentication flow exchanges an API token for an embed URL. When a parent app authenticates a user using your preferred authentication method, the parent app makes an API request to Retool to generate an embed URL. This embed URL is a secure, single-use link on the domain of your published app. Loading it in the iframe exchanges the link for a session, sets the cookies the app needs, and then displays the app.

Standard authentication through Retool remains supported.

You can now prompt the app building agent to create REST API or PostgreSQL resources directly from the app builder.

Describe the resource that you want to create, and the agent initiates the resource creation process. You'll be asked to provide credentials or more details where applicable.

Organizations on the Team plan can now use Retool-provided AI models for app building, in addition to the full catalog of supported models. These models, prefixed with Retool, have been tuned by Retool for enhanced performance and speed for app building.

The following Retool-provided models are supported:

• Retool Mini
• Retool Power