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.

If the organization has not set a preferred resource for AI app building, the app building agent will use a Retool-provided model.

The following Retool-provided models are supported:

• Retool Mini
• Retool Power

Organizations on the Free plan now use 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. Access to models from other providers is now only available on paid plans.

Builders using these models will notice comparable quality and faster speeds when compared with other models previously available on the Free plan.

The following Retool-provided models are supported:

• Retool Mini
• Retool Power

Retool now supports using external MCPs as resources in the app builder. The app building agent creates function calls to utilize tools from your connected MCP servers, which can be used while building or at app runtime. For example:

Users of the published app can only trigger MCP tools for which they have permission.

The Retool CLI is now available in public beta. It enables you to build, manage, and publish Retool-native React apps from the command line and with the help of your chosen code development agent harness, like Claude Code or Codex.

With this tool, you can write and validate app code directly on your machine. You can use the CLI independently or pair it with a local development agent. Follow the installation instructions to get started, learn how the CLI works, or compare the CLI to the MCP.

You can now embed apps in other apps, in classic apps, and in apps or websites outside Retool using an iframe. To enable app embedding, an organization admin adds Content Security Policy directive rules that name the pages that are allowed to frame your app.

Refer to the Embed apps guide to learn how.

Retool now supports manual file management of apps from the Code tab of the app builder. This enables builders to exercise finer-grained control over code files without needing to prompt the agent and consume credits.

Builders can manually add:

• Folder: A new empty folder inside the frontend or backend directory of your app.
• Frontend component: A new TypeScript file that represents a React component, which Retool populates with a basic structure of the component.
• Frontend file: A new generic frontend file. Provide the full file name, including the file extension.
• Backend function: A new TypeScript file that represents a function, which Retool populates with the basic structure of a function.
• Backend file: A new generic backend file. Provide the full file name, including the file extension.

Builders can also delete certain files or folders, including those that define components and backend functions, or other temporary or user-written files.

You can now queue messages in Chat tab of the app builder. While the agent is working, you can send up to five messages, which will be automatically sent in a batch once the agent responds.

You can edit or remove messages from the queue before they are sent, or clear the queue of all messages.

Retool introduced finer controls on branches in the app builder. You can now rename branches from the Change History panel by hovering over a branch name and clicking the icon.

You can also copy the branch name, which enables builders using Source Control to transition between development in the app builder and development locally. Learn more about switching development environments.

Retool made signficant improvements to the efficiency and performance of the app building agent. Builders will notice faster agent responses and lower AI credit consumption, especially on long-running building sessions. These improvements can result in up to 50% fewer credits consumed.