Changelog

The following patch is now available on the Stable release channel:

• Retool 4.0.12

Update your Retool instance to apply the latest bug fixes and security patches.

The app builder now includes a debug console to help you inspect your app, surface issues, and resolve them with the agent. Open it from the status bar at the bottom of the app builder.

The console has three tabs:

• Errors: Function, build, and frontend errors. Hover a row to add its context to the chat or ask the agent to fix it, or click Fix all to resolve every error at once.
• Logs: Logs emitted by the app or the agent, including function, build, frontend, sandbox, agent, and git events.
• Timeline: A record of function runs with the elapsed time and the success of each, useful for diagnosing performance issues.

The agent has access to the same information available to builders in the debug console. This enables the agent to disagnose and address issues more quickly, and it can write more performant functions.

Multi-instance releases are now supported for apps built in the new app builder, in addition to classic apps and workflows. To enable multi-instance releases, navigate to Settings > Source control > Edit settings and turn on Enable multi-instance releases.

Organizations using Source Control can manage releases of protected apps, classic apps, and workflows across multiple deployment instances. 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.

Multi-instance releases work slightly differently for apps and classic apps. Learn more about the difference, or get started with multi-instance releases for apps.

On September 30, 2026, Retool will conclude the public beta period for Assist and remove Assist from the classic app builder. All cloud and self-hosted instances will no longer be able to use Assist in the product.

The drag-and-drop experience for building and maintaining classic apps is still available. For an AI-powered building experience, Retool recommends using the new app builder. Converting your classic apps to the new app builder is free for Team, Business, and Enterprise organizations.

If you have any questions, reach out to the Community Forum or your account manager.

Enterprise organizations can use access policies to define which data each group of users can read or write on a resource. Retool enforces access policies on every query that runs against the resource. A policy can grant access to whole tables, specific columns, or specific rows.

For example, you can use an access policy to restrict an EMEA group's access on a table to only the customer rows for their own region. Retool applies that restriction to every query the group runs against the resource, so it holds regardless of which app, query, or agent the request comes from.

One policy covers queries from apps, the query library, raw SQL, and agents. Workflow queries against an enforced resource are blocked, so account for any workflows using the resource before you turn enforcement on. Retool supports access policies on PostgreSQL resources.

Access policies are enabled by default on cloud instances. On self-hosted instances, navigate to Settings > Beta and toggle on the feature flag for Enforce data security using access policies. To create a policy:

1. Open a PostgreSQL resource and select the Access Enforcement tab.
2. Turn on Data access enforcement.
3. Create a policy, choose the groups and environments it covers, and define its rules.
4. Activate the policy, then click Save changes.

Turning on data access enforcement closes the resource by default in every resource environment. Access policies apply only to the resource environments you select, so grant broad access first and narrow it once your policies are in place. Refer to Configure access policies for more details.

Access policies operate by granting access, not denying access. Refer to Access policies and Data access enforcement for more information.

You can now use Plan mode for further control over the actions that the app building agent takes.

1. Click to switch from Build mode to Plan mode and tell the agent what changes you want it to make.
2. The agent creates a comprehensive plan, which is written as a Markdown file in the .plan folder. Click Review to view the file.
3. Review the plan, and switch to the Markdown tab to make any changes. You can also ask the agent to update the plan.
4. When you're ready, click Build plan.

Retool is deprecating the dedicated Vertica resource type.

Retool will remove the resource type in Q1 2027, after two quarterly Stable releases. After removal, Vertica resources will stop working. Queries in apps and workflows that still point at those resources will fail. Retool will no longer ship the Vertica JDBC driver. Cloud organizations will not have a Vertica connection option after removal.

Self-hosted organizations can keep querying Vertica after removal by creating a JDBC resource and adding a Vertica JDBC driver that you provide. Retool will not migrate Vertica resources or their query references automatically.

1. Download the Vertica JDBC driver from Vertica.
2. Add the .jar file to your self-hosted instance. Follow the JDBC configuration steps for JDBC_DIRECTORY_PATH.
3. Create a JDBC resource with Driver name com.vertica.jdbc.Driver, connection string jdbc:vertica://HOSTNAME:5433/DATABASE?user=USERNAME&password=PASSWORD&DisableCopyLocal=true, and schema query select table_name, column_name, data_type, table_schema from columns. Include DisableCopyLocal=true on the connection string.
4. Open each app and workflow query that uses the Vertica resource. Change the query to use the new JDBC resource, then test it.

JDBC resources do not support Retool-managed SSH tunnels. If your Vertica resource uses an SSH tunnel, or you have a large number of Vertica queries and need help finding them, contact Retool Support.

The following patches are now available on the Stable release channel:

• Retool 4.0.10
• Retool 3.334.28

Update your Retool instance to apply the latest bug fixes and security patches.

Gemini 3.6 Flash is now available to cloud organizations through Google. It can be used with AI resource queries when you connect Google with your own API key. Support for self-hosted Retool is coming in an upcoming release.

Retool 4.35 is now available on the Edge release channel for self-hosted organizations.