Changelog

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.

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

• Retool 4.0.9
• Retool 3.334.27

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

Organization admins can now add shared building context that applies to all apps built with the new app builder. Building context is applied as custom instructions in the system prompt when the user makes any changes via prompting in the Chat tab, similar to the way AGENTS.md files work. Building context is valuable for defining design practices, coding conventions, data usage recommendations, and other guidelines across your organization.

To add shared context, navigate to Settings > Building context. Add your instructions in Markdown format, and click Publish to apply your changes to all apps.

Building context applies to all apps in your organization. If you have Spaces enabled, it applies to all apps in your space.

Admins on the Enterprise plan can now complete each step in the Get started section of the Overview page using guided step-by-step wizards instead of navigating through separate Settings pages to complete configuration.

You can now directly configure from the Overview page:

• SSO
• Resources
• Source control
• Spaces
• Permissions

The Get started section is aimed at providing a better onboarding experience for admins of new organizations, and will help identify what configurations still need to be set up for admins or existing organizations. For example, setting up spaces walks you through choosing custom spaces or a Dev/Staging/Prod environment split, naming and configuring each space, and optionally copying over your existing SSO settings, before creating every space at once.

The Overview page also includes an Action center that contains important notifications and pending join requests, suggested users, and seat upgrade requests, so admins can act on what needs attention, as well an at-a-glance overview of your organization stats, such as total users, apps, workflows, and AI credit usage.

Retool introduced several features to help Enterprise organizations manage AI token spend when using their own API key for AI resources.

Use the new Get BYOK AI token usage endpoint to measure the number of tokens consumed for each AI resource that uses your own key. You can view the number of tokens consumed by resource, user, and surface area.

In addition, you can also view BYOK AI token usage in Settings. Navigate to the Usage Analytics page, and click the AI tab. You can filter AI usage by model, user, and feature.

Learn more about credit and token monitoring.

Self-hosted Retool instances can now connect to Gmail as a resource to read, send, and manage email using the Gmail API.

Self-hosted instances authenticate using your own Google Cloud OAuth client, so this integration is available now without waiting on Google's app-verification process for Retool's shared OAuth client.

The app builder now supports multiple chat conversations (threads) working on the same branch rather than a single thread per branch.

A thread is a single chat conversation with the agent in the Chat tab. Threads are intended to help you keep your work organized by task or theme. For example, use one thread for updating your app theme, and another thread for editing a chart on that page. Manage threads from the Chat tab.

A branch is a set of changes to your app, associated with an app preview, and with its own change history. A branch is the unit of work that you publish, and you create a new branch to begin a distinct line of work. For example, create a new branch when you want to change the resources that your app uses, or when you want to overhaul a page. Manage branches from the Change History tab in the navbar.

When using Source Control, branches in the protected app builder map to branches in your external git repository.